Nothing Special   »   [go: up one dir, main page]

Manual MLT 1 MLT 2 Cat 200 Foundation Fieldbus Communication Software 3rd Ed Rosemount en 69940

Download as pdf or txt
Download as pdf or txt
You are on page 1of 98

Instruction Manual

ETC01184
10/2003

Instruction Manual
FoundationTM Fieldbus
Communication Option for
MLT 1, MLT 2 and CAT 200

3rd Edition 10/2003

www.EmersonProcess.com
Foundation Fieldbus for MLT 1, MLT 2 & CAT 200 Instruction Manual
ETC01184
10/2003
ESSENTIAL INSTRUCTIONS
READ THIS PAGE BEFORE PROCEEDING!

Emerson Process Management (Rosemount Analytical) designs, manufactures and tests


its products to meet many national and international standards. Because these instruments
are sophisticated technical products, you MUST properly install, use, and maintain
them to ensure they continue to operate within their normal specifications. The following
instructions MUST be adhered to and integrated into your safety program when installing,
using and maintaining Emerson Process Management (Rosemount Analytical) products.
Failure to follow the proper instructions may cause any one of the following situations to
occur: Loss of life; personal injury; property damage; damage to this instrument; and warranty
invalidation.

• Read all instructions prior to installing, operating, and servicing the product.

• If you do not understand any of the instructions, contact your Emerson Process
Management (Rosemount Analytical) representative for clarification.

• Follow all warnings, cautions, and instructions marked on and supplied with the product.

• Inform and educate your personnel in the proper installation, operation, and
maintenance of the product.

• Install your equipment as specified in the Installation Instructions of the appropriate


Instruction Manual and per applicable local and national codes. Connect all products
to the proper electrical and pressure sources.

• To ensure proper performance, use qualified personnel to install, operate, update, program,
and maintain the product.

• When replacement parts are required, ensure that qualified people use replacement parts
specified by Emerson Process Management (Rosemount Analytical). Unauthorized parts
and procedures can affect the product’s performance, place the safe operation of your
process at risk, and VOID YOUR WARRANTY. Look-alike substitutions may result in fire,
electrical hazards, or improper operation.

• Ensure that all equipment doors are closed and protective covers are in place, except
when maintenance is being performed by qualified persons, to prevent electrical
shock and personal injury.

The information contained in this document is subject to change without notice. Misprints
reserved.

1st Edition 06/2003 2nd Edition 10/2003


3rd Edition 10/2003
©
2003 by Emerson Process Management

Emerson Process Management


GmbH & Co. OHG
Industriestrasse 1
D-63594 Hasselroth
Germany
T +49 (0) 6055 884-0
F +49 (0) 6055 884-209
Internet: www.EmersonProcess.com
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus

PREFACE

The purpose of this manual is to provide information concerning the


technology, components and functions of FOUNDATIONTM Fieldbus in
combination with a MLT or CAT 200 analyzer.
Some sections may describe equipment not used in your configuration.
The user should become thoroughly familiar with the operation of this
module before operating it. Read this instruction manual completely.

Definitions

The following definitions apply to WARNINGS, CAUTIONS and NOTES found


throughout this publication.

Highlights an operation or Highlights an operation or


maintenance procedure, maintenance procedure,
practice, condition, practice, condition,
statement, etc. If not strictly statement, etc. If not strictly
observed, could result in observed, could result in
injury, death, or long-term damage to or destruction of
health hazards of personnel. equipment, or loss of
effectiveness.

NOTE
Highlights an essential operating
procedure, condition or statement.

P-1
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003

IMPORTANT
SAFETY INSTRUCTIONS

INTENDED USE STATEMENT


The equipment covered by or referred to within this manual is inteded for use as an
industrial process measurement device only. It is not intended for use in medical,
diagnostic, or life support applications, and no independent agency certifications or
approvals are to be implied as covering such applications.

SAFETY SUMMARY
If this equipment is used in a manner not specified in the related instructions, protective
systems may be impaired.

AUTHORIZED PERSONNEL
To avoid loss of life, personal injury and damage to this equipment and on-site property,
do not operate or service this instrument before reading and understanding all related
instruction manuals and receiving appropriate training. Save these instructions.

EXPLOSION HAZARD
In principle FOUNDATION TM Fieldbus signals as described in this manual are
NOT INTRINSICALLY SAFE
according to national and international standards for explosion protection for
equipment to be used in hazardous areas, except stated on the equipment’s
nameplate label!
Do not connect NON INTRINSICALLY SAFE circuits to INTRINSICALLY SAFE ciruits!
Connecting NON INTRINSICALLY SAFE circuits to INTRINSICALLY SAFE ciruits
voids the safety of the whole equipment and could result in injury, death, or long-
term health hazards of personnel and/or damage to or destruction of equipment!

P-2
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus

TABLE OF CONTENTS

PREFACE P-1
Definitions .......................................................................................................................... P-1
Safety Instructions .............................................................................................................. P-2
SECTION 1
FOUNDATIONTM Fieldbus Technology 1-1
1-1 Overview .................................................................................................................... 1-1
1-2 Introduction ............................................................................................................... 1-1
1-2-1 Function Blocks ................................................................................................... 1-2
1-2-2 Device Descriptions ............................................................................................. 1-3
1-3 Instrument Specific Function Blocks ...................................................................... 1-4
1-3-1 Resource Blocks .................................................................................................. 1-4
1-3-2 Transducer Blocks ............................................................................................... 1-4
1-3-3 Alerts ..................................................................................................................... 1-4
1-4 Network Communication ......................................................................................... 1-5
1-4-1 Link Active Scheduler (LAS) ................................................................................ 1-5
1-4-2 Device Addressing ............................................................................................... 1-6
1-4-3 Scheduled Transfers ............................................................................................ 1-6
1-4-4 Unscheduled Transfers ....................................................................................... 1-8
1-4-5 Function Block Scheduling ................................................................................. 1-9
1-5 References .............................................................................................................. 1-10
1-5-1 Fieldbus Foundation .......................................................................................... 1-10
1-6 Implemented Function Blocks ............................................................................... 1-11
SECTION 2
Transducer Block 2-1
2-1 List of Transducer Block Parameters ..................................................................... 2-2
2-2 Transducer Block Parameter Descriptions ............................................................ 2-5
2-3 Transducer Block Parameter Attribute Definitions ................................................ 2-7
2-4 Transducer Block Enumerations ............................................................................ 2-9
2-4-1 Gas Control State ................................................................................................. 2-9
2-4-2 Calibration States ................................................................................................. 2-9
2-4-3 Calibration Step Control .................................................................................... 2-10
2-4-4 Measurement Options ........................................................................................ 2-11
2-4-5 Calibration Options ............................................................................................ 2-11
2-4-6 Sensor Options ................................................................................................... 2-12
2-4-7 Analyzer Options ................................................................................................ 2-12
2-4-8 Access Mode Control ......................................................................................... 2-13

T-1
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
Table of Contents

2-4-9 Detailed Status.................................................................................................... 2-13


2-4-9-1 Detailed Maintenance ..................................................................................... 2-13
2-4-9-2 Detailed Failure ............................................................................................... 2-14
2-4-9-3 Detailed Status ............................................................................................... 2-15
2-4-10 Function Call Control ......................................................................................... 2-16
2-5 Transducer Block Channel Assignments ............................................................. 2-17
2-5-1 I/O Channel Assignments for AI-Blocks ............................................................ 2-17
2-5-2 I/O Channel Assignment for A0-Blocks ............................................................. 2-17
2-6 Simulation of TBlk States ....................................................................................... 2-18
2-7 Supported Transducer Block Errors ..................................................................... 2-18
2-7-1 Out of Service ..................................................................................................... 2-18
2-7-2 Block Configuration Error ................................................................................. 2-18
2-7-3 Input Failure/ Process Variable has BAD Status .............................................. 2-18
2-7-4 Device needs Maintenance Now ....................................................................... 2-18
2-7-5 Simulate Active ................................................................................................... 2-18
2-7-6 Other Error .......................................................................................................... 2-18
SECTION 3
Resource Block 3-1
3-1 Mapping of the PlantWeb Alerts .............................................................................. 3-1
3-2 PWA_SIMULATE ....................................................................................................... 3-3
SECTION 4
Analog Input (AI) Function Block 4-1
4-1 Simulation ................................................................................................................. 4-3
4-2 Filtering ...................................................................................................................... 4-4
4-3 Signal Conversion .................................................................................................... 4-4
4-4 Block Errors .............................................................................................................. 4-6
4-5 Modes ........................................................................................................................ 4-6
4-6 Alarm Detection ........................................................................................................ 4-7
4-7 Status Handling ........................................................................................................ 4-8
4-8 Advanced Features .................................................................................................. 4-8
4-9 Application Information ............................................................................................ 4-9
4-9-1 Application Example 1
Temperature Transmitter ...................................................................................... 4-9
4-9-2 Application Example 2
Pressure Transmitter used to Measure Level in Open Tank ........................... 4-10
4-9-3 Application Example 3
Differential Pressure Transmitter used to Measure Flow ................................ 4-11
4-10 Troubleshooting ..................................................................................................... 4-12

T-2
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
Table of Contents

SECTION 5
Analog Output (AO) Function Block 5-1
5-1 Setting the Output ..................................................................................................... 5-2
5-2 Setpoint Selection and Limiting .............................................................................. 5-3
5-3 Conversion and Status Calculation ........................................................................ 5-3
5-4 Simulation ................................................................................................................. 5-4
5-5 Action on Fault Detection......................................................................................... 5-4
5-6 Block Errors .............................................................................................................. 5-5
5-7 Modes ........................................................................................................................ 5-5
5-8 Status Handling ........................................................................................................ 5-5
SECTION 6
Input Selector (ISEL) Function Block 6-1
6-1 Block Errors .............................................................................................................. 6-3
6-2 Modes ........................................................................................................................ 6-4
6-3 Alarm Detection ........................................................................................................ 6-4
6-4 Block Execution........................................................................................................ 6-4
6-5 Status Handling ........................................................................................................ 6-5
6-6 Application Information ............................................................................................ 6-5
6-7 Troubleshooting ....................................................................................................... 6-7
SECTION 7
Arithmetic (ARTHM) Function Block 7-1
7-1 Block Errors .............................................................................................................. 7-4
7-2 Modes ........................................................................................................................ 7-4
7-3 Alarm Detection ........................................................................................................ 7-5
7-4 Block Execution........................................................................................................ 7-5
7-5 Status Handling ........................................................................................................ 7-6
7-6 Application Information ............................................................................................ 7-6
SECTION 8
Proportional / Integral / Derivative (PID) Function Block 8-1
8-1 Setpoint Selection and Limiting .............................................................................. 8-4
8-2 Filtering ...................................................................................................................... 8-5
8-3 Feedforward Calculation .......................................................................................... 8-5
8-4 Tracking ..................................................................................................................... 8-5
8-5 Output Selection and Limiting ................................................................................. 8-6
8-6 Bumpless Transfer and Setpoint Tracking ............................................................. 8-6
8-7 PID Equation Structures .......................................................................................... 8-6
8-8 Reverse and Direct Action ....................................................................................... 8-7

T-3
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
Table of Contents

8-9 Reset Limiting ........................................................................................................... 8-7


8-10 Block Errors .............................................................................................................. 8-7
8-11 Modes ........................................................................................................................ 8-8
8-12 Alarm Detection ........................................................................................................ 8-8
8-13 Status Handling ........................................................................................................ 8-9
8-14 Closed Loop Control ................................................................................................ 8-9
8-15 Application Information .......................................................................................... 8-10
8-15-1 Application Example 1
Basic PID Block for Steam Heater Control ....................................................... 8-11
8-15-2 Application Example 2
Feedforward Control .......................................................................................... 8-12
8-15-3 Application Example 3
Cascade Control with Master and Slave Loops ............................................... 8-13
8-15-4 Application Example 4
Cascade Control with Override ......................................................................... 8-14
8-16 Troubleshooting ..................................................................................................... 8-15
APPENDIX
Operation with EMERSON™ Process Management DeltaV™ A-1
A-1 About DeltaV Software with AMS inside ................................................................ A-1
A-2 Install the Analyzer onto DeltaVTM......................................................................... A-1

T-4
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
SECTION 1
FOUNDATION TM
Fieldbus Technology

1-1 Overview
FOUNDATIONTM Fieldbus is an all digital, serial, devices on one set of wires.
two-way communication system that • Increased selection of suppliers
interconnects field equipment such as sensors, due to interoperability.
actuators, and controllers. Fieldbus is a Local • Reduced loading on control room
Area Network (LAN) for instruments used in equipment with the distribution of
both process and manufacturing automation some control and input/output
with built-in capacity to distribute the control functions to field devices.
application across the network. It is the ability • Speed options for process control
to distribute control among intelligent field and manufacturing applications.
devices on the plant floor and digitally
communicate that information at high speed NOTE: The following descriptions and
that makes FOUNDATIONTM Fieldbus an enabling definitions are not intended as a training guide
technology. for Foundation Fieldbus technology but are
Emerson offers a full range of products from presented as an overview for those not familiar
field devices to the DeltaV scalable control with Fieldbus and to define device specific
system to allow an easy transition to Fieldbus attributes for the Fieldbus system engineer.
technology. Anyone attempting to implement Fieldbus
The Fieldbus retains the features of the communications and control with this analyzer
4-20 mA analog system, including must be well versed in Fieldbus technology and
standardized physical interface to the wire, bus protocol and must be competent in
powered devices on a single wire, and intrinsic programming using available tools such as
safety options, and enables additional DeltaV. See „References“ below for additional
capabilities such as: sources for Fieldbus technology and
• Increased capabilities due to full methodology.
digital communications.
• Reduced wiring and wire
terminations due to multiple

1-2 Introduction
A Fieldbus system is a distributed system a collection of physical devices interconnected
composed of field devices and control and by a Fieldbus network. One of the ways that
monitoring equipment integrated into the the physical devices are used is to perform their
physical environment of a plant or factory. portion of the total system operation by
Fieldbus devices work together to provide I/O implementing one or more function blocks.
and control for automated processes and
operations. The Fieldbus Foundation provides
a framework for describing these systems as

1-1
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
1-2-1 Function Blocks

1-2-1 Function Blocks


Function blocks within the Fieldbus device per- classes, such as input, output, control, and
form the various functions required for process calculation blocks. Each of these classes also
control. Because each system is different, the has a small set of parameters established for
mix and configuration of functions are different. it. They have also published definitions for
Therefore, the Fieldbus F OUNDATION has transducer blocks commonly used with
designed a range of function blocks, each standard function blocks. Examples include
addressing a different need. temperature, pressure, level, and flow
Function blocks perform process control transducer blocks.
functions, such as analog input (AI) and analog The FOUNDATION specifications and definitions
output (AO) functions as well as proportional- allow vendors to add their own parameters by
integral-derivative (PID) functions. The importing and sub-classing specified classes.
standard function blocks provide a common This approach permits extending function block
structure for defining function block inputs, definitions as new requirements are discovered
outputs, control parameters, events, alarms, and as technology advances.
and modes, and combining them into a process Fig. 1-1 illustrates the internal structure of a
that can be implemented within a single device function block. When execution begins, input
or over the Fieldbus network. This simplifies parameter values from other blocks are
the identification of characteristics that are snapped-in by the block. The input snap
common to function blocks. process ensures that these values do not
The Fieldbus FOUNDATION has established the change during the block execution. New values
function blocks by defining a small set of received for these parameters do not affect the
parameters used in all function blocks called snapped values and will not be used by the
universal parameters. The FOUNDATION has also function block during the current execution.
defined a standard set of function block

Input Events Execution Control Output Events

Input Parameter
Input Processing Output Output

Status Status

Fig. 1-1
Function Block Internal Structure

1-2
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
1-2-2 Device Descriptions

Once the inputs are snapped, the algorithm A block is a tagged logical processing unit. The
operates on them, generating outputs as it tag is the name of the block. System
progresses. Algorithm executions are management services locate a block by its tag.
controlled through the setting of contained Thus the service personnel need only know the
parameters. Contained parameters are tag of the block to access or change the
internal to function blocks and do not appear appropriate block parameters.
as normal input and output parameters. Function blocks are also capable of performing
However, they may be accessed and modified short-term data collection and storage for
remotely, as specified by the function block. reviewing their behavior.
Input events may affect the operation of the
algorithm. An execution control function
regulates the receipt of input events and the
generation of output events during execution
of the algorithm. Upon completion of the
algorithm, the data internal to the block is saved
for use in the next execution, and the output data
is snapped, releasing it for use by other function
blocks.

1-2-2 Device Descriptions


Device Descriptions are specified tool from the external medium. The use of an open
definitions that are associated with the function language in the device description permits
blocks. Device descriptions provide for the interoperability of function blocks within
definition and description of the function blocks devices from various vendors. Additionally,
and their parameters. human interface devices, such as operator
To promote consistency of definition and consoles and computers, do not have to be
understanding, descriptive information, such as programmed specifically for each type of
data type and length, is maintained in the device device on the bus. Instead their displays and
description. Device Descriptions are written interactions with devices are driven from the
using an open language called the Device device descriptions.
Description Language (DDL). Parameter Device descriptions may also include a set of
transfers between function blocks can be easily processing routines called methods. Methods
verified because all parameters are described provide a procedure for accessing and
using the same language. Once written, the manipulating parameters within a device.
device description can be stored on an external
medium, such as a CD-ROM or diskette.
Users can then read the device description

1-3
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
1-3 Instrument Specific Function Blocks

1-3 Instrument Specific Function Blocks


In addition to function blocks, Fieldbus devices
contain two other block types to support the
function blocks. These are the resource block
and the transducer block. The resource block
contains the hardware specific characteristics
associated with a device. Transducer blocks
couple the function blocks to local input/output
functions.

1-3-1 Resource Blocks


Resource blocks contain the hardware specific of the physical device, as defined by the
characteristics associated with a device; they manufacturer. As a result of this activity, the
have no input or output parameters. The algorithm may cause the generation of events.
algorithm within a resource block monitors and There is only one resource block defined for a
controls the general operation of the physical device. For example, when the mode of a
device hardware. The execution of this resource block is „out of service,“ it impacts all
algorithm is dependent on the characteristics of the other blocks.

1-3-2 Transducer Blocks


Transducer blocks connect function blocks to writes to the actuator without burdening the
local input/output functions. They read sensor function blocks that use the data. The transducer
hardware and write to effector (actuator) block also isolates the function block from the
hardware. This permits the transducer block to vendor specific characteristics of the physical
execute as frequently as necessary to obtain I/O.
good data from sensors and ensure proper

1-3-3 Alerts
When an alert occurs, execution control sends Two types of alerts are defined for the block,
an event notification and waits a specified events and alarms. Events are used to report
period of time for an acknowledgment to be a status change when a block leaves a
received. This occurs even if the condition that particular state, such as when a parameter
caused the alert no longer exists. If the crosses a threshold. Alarms not only report a
acknowledgment is not received within the pre- status change when a block leaves a particular
specified time-out period, the event notification state, but also report when it returns back to
is retransmitted. This assures that alert that state.
messages are not lost.

1-4
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
1-4 Network Communication

1-4 Network Communication


Fig. 1-2 illustrates a simple Fieldbus network
consisting of a single segment (link).

Fieldbus Link
LAS
(Link Active Scheduler)

Link Master

Fig. 1-2
Single Link Fieldbus Network Basic Devices and/or LinkMaster Devices

1-4-1 Link Active Scheduler (LAS)


All links have one and only one Link Active capable of becoming the LAS are called link
Scheduler (LAS). The LAS operates as the bus master devices. All other devices are referred
arbiter for the link. The LAS does the following: to as basic devices. When a segment first
• recognizes and adds new devices to the starts up, or upon failure of the existing LAS,
link. the link master devices on the segment bid to
• removes non-responsive devices from the become the LAS. The link master that wins the
link. bid begins operating as the LAS immediately
• distributes Data Link (DL) and Link upon completion of the bidding process. Link
Scheduling (LS) time on the link. Data Link masters that do not become the LAS act as
Time is a network-wide time periodically basic devices. However, the link masters can
distributed by the LAS to synchronize all act as LAS backups by monitoring the link for
device clocks on the bus. Link Scheduling failure of the LAS and then bidding to become
time is a link-specific time represented as the LAS when a LAS failure is detected.
an offset from Data Link Time. It is used Only one device can communicate at a time.
to indicate when the LAS on each link Permission to communicate on the bus is
begins and repeats its schedule. It is used controlled by a centralized token passed
by system management to synchronize between devices by the LAS. Only the device
function block execution with the data with the token can communicate. The LAS
transfers scheduled by the LAS. maintains a list of all devices that need access
• polls devices for process loop data at to the bus. This list is called the „Live List.“
scheduled transmission times. Two types of tokens are used by the LAS. A
• distributes a priority-driven token to time-critical token, compel data (CD), is sent
devices between scheduled by the LAS according to a schedule. A non-
transmissions. time critical token, pass token (PT), is sent by
Any device on the link may become the LAS, the LAS to each device in ascending numerical
as long as it is capable. The devices that are order according to address.

1-5
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
1-4-2 Device Addressing

1-4-2 Device Addressing


Fieldbus uses addresses between 0 and 255. programmed address. Each of the other
Addresses 0 through 15 are reserved for group devices will be given one of four temporary
addressing and for use by the data link layer. addresses between 248 and 251. If a
For all Emerson Fieldbus devices addresses temporary address is not available, the device
20 through 35 are available to the device. If will be unavailable until a temporary address
there are two or more devices with the same becomes available.
address, the first device to start will use its

1-4-3 Scheduled Transfers


Information is transferred between devices
over the Fieldbus using three different types of
reporting.

• Publisher/Subscriber: This type of receives the Compel data. The buffer


reporting is used to transfer critical contains only one copy of the data. New
process loop data, such as the process data completely overwrites previous data.
variable. The data producers (publishers) Updates to published data are transferred
post the data in a buffer that is transmitted simultaneously to all subscribers in a single
to the subscriber (S), when the publisher broadcast. Transfers of this type can be
scheduled on a precisely periodic basis.

• Report Distribution: This type of queued. They are delivered to the


reporting is used to broadcast and receivers in the order transmitted, although
multicast event and trend reports. The there may be gaps due to corrupted
destination address may be predefined so transfers. These transfers are unscheduled
that all reports are sent to the same and occur in between scheduled transfers
address, or it may be provided separately at a given priority.
with each report. Transfers of this type are

• Client/Server: This type of reporting is transmission, according to their priority,


used for request/response exchanges without overwriting previous messages.
between pairs of devices. Like Report Dis- However, unlike Report Distribution, these
tribution reporting, the transfers are transfers are flow controlled and employ a
queued, unscheduled, and prioritized. retransmission procedure to recover from
Queued means the messages are sent corrupted transfers.
and received in the order submitted for

1-6
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
1-4-3 Scheduled Transfers

Fig. 1-3 diagrams the method of scheduled that need to be cyclically transmitted. When it
data transfer. Scheduled data transfers are is time for a device to publish data, the LAS
typically used for the regular cyclic transfer of issues a Compel Data (CD) message to the
process loop data between devices on the device. Upon receipt of the CD, the device
Fieldbus. Scheduled transfers use publisher/ broadcasts or „publishes“ the data to all
subscriber type of reporting for data transfer. devices on the Fieldbus. Any device that is
The Link Active Scheduler maintains a list of configured to receive the data is called a
transmit times for all publishers in all devices „subscriber.“

LAS

Schedule
X
DT(A)
Y
Z

A B C A D A
CD(X,A)
P S P S P S

Device X Device Y Device Z

LAS = Link Active Scheduler


P = Publisher
S = Subscriber
CD = Compel Data
DT = Data Transfer Packet
Fig. 1-3
Scheduled Data Transfer

1-7
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
1-4-4 Inscheduled Transfers

1-4-4 Unscheduled Transfers


Figure 1-4 diagrams an unscheduled transfer. between transmissions of scheduled data. The
Unscheduled transfers are used for things like LAS grants permission to a device to use the
user-initiated changes, including set point Fieldbus by issuing a pass token (PT)
changes, mode changes, tuning changes, and message to the device. When the device
upload/download. Unscheduled transfers use receives the PT, it is allowed to send messages
either report distribution or client/server type until it has finished or until the „maximum token
of reporting for transferring data. hold time“ has expired, whichever is the shorter
All of the devices on the Fieldbus are given a time. The message may be sent to a single
chance to send unscheduled messages destination or to multiple destinations.

LAS
PT(Z)

Schedule
X DT(M)
Y
Z

A B C A D A
M M

P S P S P S

Device X Device Y Device Z

LAS = Link Active Scheduler


P = Publisher
S = Subscriber
PT = Pass Token
M = Message
Fig. 1-4
Unscheduled Data Transfer

1-8
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
1-4-5 Function Block Scheduling

1-4-5 Function Block Scheduling


Figure 1-5 shows an example of a link the Function Block Schedule. The Function
schedule. A single iteration of the link-wide Block Schedule indicates when the function
schedule is called the macrocycle. When the blocks for the device are to be executed. The
system is configured and the function blocks scheduled execution time for each function
are linked, a master link-wide schedule is block is represented as an offset from the
created for the LAS. Each device maintains beginning of the macrocycle start time.
its portion of the link-wide schedule, known as

Macrocycle Start Time Sequence Repeats

Offset from macrocycle Start


time = 0 for AI Execution
Device 1 AI AI

Offset from macrocycle Start


time = 20 for AI Communication
Scheduled
Communication

Unscheduled
Communication

Offset from macrocycle Start


time = 30 for PID Execution

Device 2 PID AO PID AO

Offset from macrocycle Start


time = 50 for AO Execution

Macrocycle

Fig. 1-5
Example of Link Schedule
(Showing scheduled and unscheduled communication)

To support synchronization of schedules, Function Block schedules on a link and for the
periodically Link Scheduling (LS) time is LAS link-wide schedule. This permits function
distributed. The beginning of the macrocycle block executions and their corresponding data
represents a common starting time for all transfers to be synchronized in time.

1-9
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
1-5 References

1-5 References
The following Fieldbus FOUNDATION documents Fieldbus, and are referenced wherever
should be used to gain an understanding of appropriate in the document:
Document Number Document Title
FF-890 Fieldbus Foundation™ Fieldbus Specification —
Function Block Application Process – Part 1
FF-891 Fieldbus Foundation™ Fieldbus Specification —
Function Block Application Process – Part 2
FF-902 Fieldbus Foundation™ Fieldbus Specification —
Transducer Block Application Process – Part 1
FF-903 Fieldbus Foundation™ Fieldbus Specification —
Transducer Block Application Process – Part 2
Tab. 1-1
Fieldbus Foundation Documents

1-5-1 Fieldbus Foundation


The Fieldbus Foundation is the leading
organization dedicated to a single internatio-
nal, interoperable Fieldbus standard. Rather, it is an „open,“ interoperable Fieldbus
Established in September 1994 by a merger that is based on the International Standards
of World FIP North America and the Inter- Organization’s Open System Interconnect (OSI/
operable Systems Project (ISP), the foundation ISO) seven-layer communications model. The
is a not-for-profit corporation that consists of FOUNDATION specification is compatible with
nearly 120 of the world’s leading suppliers and the officially sanctioned SP50 standards project
end users of process control and manufacturing of The International Society for Measurement
automation products. Working together, these and Control (ISA) and the International
companies have provided unparalleled support Electrotechnical Committee (IEC).
for a worldwide Fieldbus protocol, and have
made major contributions to the IEC/ISA Contact information:
Fieldbus standards development.
Important differences exist between the 9005 Mountain Ridge Drive
Fieldbus Foundation and other Fieldbus initia- Bowie Buldg - Suite 190
tives. The foundation’s technology - Austin, TX 78759-5316, USA
FOUNDATION Fieldbus - is unique insomuch
as it is designed to support mission-critical
Tel: +1.512.794.8890
applications where the proper transfer and
handling of data is essential. Unlike proprietary Fax: +1.512.794.8893
network protocols, FOUNDATION Fieldbus is Email: info@fieldbus.org
neither owned by any individual company, or Internet: www.fieldbus.org
controlled by a single nation or regulatory body.

1-10
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
1-6 Implemented Function Blocks

1-6 Implemented Function Blocks


For the MLT we have implemented the
following function blocks :
Intended Use or
Transducer Block Channel Assignments
Resource Block (RB)
TransducerBlock (TB)
Analog-Input Block 1 (AI1) PRIM ARY_VARIABLE_1 (see Table 7? 1)
Analog-Input Block 2 (AI2) PRIM ARY_VARIABLE_2 (see Table 7? 1)
Analog-Input Block 3 (AI3) SENSOR_FLOW_1 (see Table 7? 1)
Analog-Input Block 4 (AI4) SENSOR_FLOW_2 (see Table 7? 1)
Analog-Input Block 5 (AI5) SENSOR_PRESSURE_1(read) (see Table 7? 1)
Analog-Output Block1 (AO1) SENSOR_PRESSURE_1(w rite) (seeTable 7? 2)
Analog-Output Block2 (AO2) SENSOR_PRESSURE_2(w rite) (seeTable 7? 2)
Arithmetic Block (ARTHM ) 4th order polynomial for any AI-block
PID Block (PID) proportional/integral/derivative control of any AI-block
Input Selector Block (ISEL) selector of any AI-block

Tab. 1-2
Implemented Function Blocks

1-11
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003

1-12
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus

SECTION 2
Transducer Block

The Transducer Block part was designed to The transmitter specific detailed status and its
provide the information necessary to interface relationship to standard Fieldbus block alarms
the MLT to the Fieldbus. The data structures and errors are shown in a table in the Detailed
should be used for transferring Fieldbus Status section of the document. The I/O channel
information between the MLT’s Object assignments and their status values are shown
Dictionary and other hosts and devices on in the Channel Assignments section.
Fieldbus. Finally the default values for parameters are
Three tables are used to describe the MLT defined. These are the parameters which will
parameters. The List of Parameters table be loaded into the Fieldbus Interface Board’s
defines the relative index value used to database before any communication to the
reference the parameter in the MLT Transducer transducer itself is performed.
Block Object Dictionary and the mnemonic Dynamic parameter default values are
used to reference the parameter, as well as the specified to aid in configuring static simulations
View(s )in which the parameter is contained. of the transducer block. For example, when
The Parameter Descriptions table gives a brief creating a placeholder for this device in a host
description of the behavior of each of the application’s database.
parameters. The Parameter Attributes table
describes the key attributes of each of the
parameters.

2-1
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
2-1 List of Transducer Block Parameters

2-1 List of Transducer Block Parameters


This section defines parameter access for a Parameter access is described in FF-890.
basic sensor.
Relative Param eter Mnem onic VIEW_1 VIEW_2 VIEW_3 VIEW_3 VIEW_4 VIEW_4 VIEW_4 VIEW_4
Index 1st 2nd 1st 2nd 3rd 4th
1 ST_REV 2 2 2 2 2
2 TAG_DESC
3 STRATEGY 2
4 ALERT_KEY 1
5 MODE_BLK 4 4
6 BLOCK_ERR 2 2
7 UPDATE_EVT
8 BLOCK_ALM
9 TRANSDUCER_DIRECTORY
10 TRANSDUCER_TYPE 2 2 2 2
11 XD_ERROR 1 1
12 COLLECTION_DIRECTORY
13 PRIMARY_VALUE_TYPE_1 2
14 PRIMARY_VALUE_1 5 5
15 PRIMARY_VALUE_RANGE_1 11
16 CAL_POINT_HI_1 4
17 CAL_POINT_LO_1 4
18 CAL_MIN_SPAN_1 4
19 CAL_UNIT_1 2
20 CAL_GAS_TIME_1 2
21 CAL_ZERO_TOLERANCE_1 4
22 CAL_SPAN_TOLERANCE_1 4
23 CAL_SLOPE_1 4
24 CAL_CONSTANT_1 4
25 CAL_ZERO_INTERVAL_1 2
26 CAL_ZERO_DATE_1 7
27 CAL_SPAN_INTERVAL_1 2
28 CAL_SPAN_DATE_1 7
29 CAL_ ZERO_SPAN_INTERVAL_1 2
30 CAL_ ZERO_SPAN_DATE_1 7
31 SPAN_CAL_DATE_1 7
32 ZERO_CAL_DATE_1 7
33 SENSOR_TYPE_1 2
34 SENSOR_RANGE_1 11
35 SENSOR_ID_1 30
36 SENSOR_FILTER_VALUE_1 4
37 SENSOR_RAW_CONCENTRATION_1 4
38 SENSOR_AVG_CYCLES_1 2
39 SENSOR_AVG_METHOD_1 1
40 SENSOR_NOISE_REFVAL_1 4

Tab. 2-1
Transducer Block Parameters

2-2
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
2-1 List of Transducer Block Parameters

Relative Param eter Mnem onic VIEW_1 VIEW_2 VIEW_3 VIEW_3 VIEW_4 VIEW_4 VIEW_4 VIEW_4
Index 1st 2nd 1st 2nd 3rd 4th
41 SENSOR_NOISE_LEVEL_1 4
42 SENSOR_NOISE_TUNE_1 4
43 SENSOR_ZTEMPERATURE_1 4
44 SENSOR_STEMPERATURE_1 4
45 SENSOR_TEMP_OFFSET_1 4
46 SENSOR_CROSS_INTF_OFFSET_1 4
47 SENSOR_TEMP_FACTOR_1 4
48 SENSOR_PRESSURE_1 5 5
49 SENSOR_PRESSURE_FACTOR_1 4
50 SENSOR_FLOW_1 5 5
51 SENSOR_OPTS_1 4
52 PRIMARY_VALUE_TYPE_2 2
53 PRIMARY_VALUE_2 5 5
54 PRIMARY_VALUE_RANGE_2 11
55 CAL_POINT_HI_2 4
56 CAL_POINT_LO_2 4
57 CAL_MIN_SPAN_2 4
58 CAL_UNIT_2 2
59 CAL_GAS_TIME_2 2
60 CAL_ZERO_TOLERANCE_2 4
61 CAL_SPAN_TOLERANCE_2 4
62 CAL_SLOPE_2 4
63 CAL_CONSTANT_2 4
64 CAL_ZERO_INTERVAL_2 2
65 CAL_ZERO_DATE_2 7
66 CAL_SPAN_INTERVAL_2 2
67 CAL_SPAN_DATE_2 7
68 CAL_ ZERO_SPAN_INTERVAL_2 2
69 CAL_ ZERO_SPAN_DATE_2 7
70 SPAN_CAL_DATE_2 7
71 ZERO_CAL_DATE_2 7
72 SENSOR_TYPE_2 2
73 SENSOR_RANGE_2 11
74 SENSOR_ID_2 30
75 SENSOR_FILTER_VALUE_2 4
76 SENSOR_RAW_CONCENTRATION_2 4
77 SENSOR_AVG_CYCLES_2 2
78 SENSOR_AVG_METHOD_2 1
79 SENSOR_NOISE_REFVAL_2 4
80 SENSOR_NOISE_LEVEL_2 4

Tab. 2-1 (cont’d)


Transducer Block Parameters

2-3
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
2-1 List of Transducer Block Parameters

Relative Param eter Mnem onic VIEW_1 VIEW_2 VIEW_3 VIEW_3 VIEW_4 VIEW_4 VIEW_4 VIEW_4
Index 1st 2nd 1st 2nd 3rd 4th
81 SENSOR_NOISE_TUNE_2 4
82 SENSOR_ZTEMPERATURE_2 4
83 SENSOR_STEMPERATURE_2 4
84 SENSOR_TEMP_OFFSET_2 4
85 SENSOR_CROSS_INTF_OFFSET_2 4
86 SENSOR_TEMP_FACTOR_2 4
87 SENSOR_PRESSURE_2 5 5
88 SENSOR_PRESSURE_FACTOR_2 4
89 SENSOR_FLOW_2 5 5
90 SENSOR_OPTS_2 4
91 ANALYZER_OPTS 1
92 MEASUREMENT_OPTS 2
93 GAS_CTRL_STATE 2 2
94 CAL_STATE 2 2
95 CAL_STEP 1
96 CAL_OPTS 1
97 FUNCTION_CALL 1
98 DETAILED_FAILURE 4
99 DETAILED_MAINTENANCE 4
100 DETAILED_STATUS 4
101 SIM_DETAILED_FAILURE 4
102 SIM_DETAILED_MAINTENANCE 4
103 SIM_DETAILED_STATUS 4
104 DEVICE_TIME 7
105 MODULE_SN 20
106 MANUFACTURING_DATE 30
107 ANALYZER_HW_VERSION 30
108 ANALYZER_SW_VERSION 30
109 ACCESS_MODE 1
110 STATS_ATTEMPTS 4
111 STATS_TIMEOUTS 4
Totals 45 24 86 116 72 110 83 83

Tab. 2-1 (cont’d)


Transducer Block Parameters

2-4
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
2-2 Transducer Block Parameter Descriptions

2-2 Transducer Block Parameter Descriptions


This table gives a description of all parameters Fieldbus specifications that the description can
in the above table, or gives the location in the be found.
Param eter Mnem onic Description
ACCESS_MODE This parameter controls access to the transducer block parameters. See Table 6-8.
ALERT_KEY See FF-891 section 5.3.
ANALYZER_HW_VERSION The type of the analyzer hardw are including boot image version string
ANALYZER_OPTS The installed analyzer options
ANALYZER_SW_VERSION The version number of the analyzer softw are
BLOCK_ALM See FF-891 section 5.3.
BLOCK_ERR See FF-891 section 5.3.
CAL_CONSTANT_n The zero correction offset (calculated by zero calibration).
CAL_GAS_TIME Purge delay time (in secs) for calibration gas supply
CAL_MIN_SPAN_n See FF-903 section 3.3.
CAL_OPTS The calibration options. See Table 6-5.
CAL_POINT_HI_n See FF-903 section 3.3
CAL_POINT_LO_n See FF-903 section 3.3
CAL_SLOPE_n This parameter represents the span correction factor (calculated by span calibration).
CAL_SPAN_DATE_n The date/time the next automatic span calibration w ill be started.
CAL_SPAN_INTERVAL_n The time interval (in hours) for automatic span calibrations (0 = OFF).
CAL_SPAN_TOLERANCE_n The allowed deviation tolerance (% of CAL_POINT_HI_n) for a span calibration.
CAL_STATE This parameter represents the present state a calibration cycle is in.
CAL_STEP This parameter is used to control zero and/or span calibrations. See Table 6-3 for the definition of states.
CAL_UNIT_n See FF-903 section 3.3.
CAL_ZERO_DATE_n The date/time the next automatic zero calibration w ill be started.
CAL_ZERO_INTERVAL_n The time interval (in hours) for automatic zero calibrations (0 = OFF).
CAL_ZERO_SPAN_DATE_n The date/time the next automatic zero & span calibrations w ill be started.
CAL_ZERO_SPAN_INTERVAL_n The time interval (in hours) for automatic zero & span calibrations (0 = OFF).
CAL_ZERO_TOLERANCE_n The allowed deviation tolerance (% of CAL_POINT_HI_n) for a zero calibration.
COLLECTION_DIRECTORY See FF-891 section 5.3.
DETAILED_FAILURE This is a bit-enumerated value used to communicate the failures of the device. SeeTable 6-9.
DETAILED_MAINTENANCE This is a bit-enumerated value used to communicate the maintenance requests of the device. SeeTable 6-10.
DETAILED_STATUS This is a bit-enumerated value used to communicate the status of the device. See Table 6-11 - Detailed
DEVICE_TIME This is the analyzer's internal real time clock. It is used to automatically start time/date controlled procedures.
To synchronize it w ith the FF-central date/time w e should w rite to in certain time intervals.
FUNCTION_CALL This parameter is used to call certain device procedures. SeeTable 6-12 for the definition of the states.
GAS_CTRL_STATE The state of controlling the gas valves as w ell as gas pumps.
MANUFACTURING_DATE The analyzer's manufacturing date string
MEASUREMENT_OPTS The different kind of options for the measurement.
MODE_BLK See FF-891 section 5.3.
MODULE_SN The analyzer's serial number
PRIMARY_VALUE_n See FF-903 section 3.3.
PRIMARY_VALUE_RANGE_n See FF-903 section 3.3.
PRIMARY_VALUE_TYPE_n See FF-903 section 3.3 and 4.1.
SENSOR_AVG_CYCLES_n The number of preaveraging cycles for digital signal filtering.
SENSOR_AVG_METHOD_n The preaveraging method for digital signal filtering (arithmetic or sliding).
SENSOR_CROSS_INTF_OFFSET_n The zero correction of cross interference compensation.
SENSOR_FILTER_VALUE_n The t90 response time (in secs) for gas change.

Tab. 2-2
Transducer Block Parameter Descriptions

2-5
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
2-1 List of Transducer Block Parameters

Param eter Mnem onic Description


SENSOR_FLOW_n The current gas flow (in l/min) of a measurement sensor. If the optional flow sensor is installed this is a
dynamic variable. If the sensor is not installed w e do not use for further evaluations.
SENSOR_ID_n String w hich contents the measurement sensor's identifier as w ell as the measured gas type.
SENSOR_NOISE_LEVEL_n This is the percentage level of the reference value the dynamic noise filtering becomes active.
SENSOR_NOISE_REFVAL_n This parameter is a reference value (in ppm) for the dynamic noise filter.
SENSOR_NOISE_TUNE_n Tuning factor how extremely the dynamic noise filter reduces dynamic noises.
SENSOR_OPTS_n The installed sensor specific options.
SENSOR_PRESSURE_n The current pressure (in hPa) of a measurement sensor:
If internal pressure sensor is installed this is a readonly dynamic variable.
If no pressure sensor is installed w e can input the current pressure value.
If w e use remote pressure w e have to input via AO block. There w e have to select appropriate assignment
by the CHANNEL-parameter.
SENSOR_PRESSURE_FACTOR_n This parameter represents the span correction of pressure compensation.
SENSOR_RANGE_n See FF-903 section 3.3.
SENSOR_RAW_CONCENTRATION_n This parameter represents the raw value of A/D-Conversion of measurement channel.
SENSOR_STEMPERATURE_n This parameter is the temperature (in °C) used for compensation of span corrections.
SENSOR_TEMP_FACTOR_n This parameter represents the span correction of temperature compensation
SENSOR_TEMP_OFFSET_n This parameter represents the zero correction of temperature compensation.
SENSOR_TYPE_n See FF-903 section 3.3 and 4.3.
SENSOR_ZTEMPERATURE_n This parameter is the temperature (in °C) used for compensation of zero corrections.
SIM_DETAILED_FAILURE This is a bit-enumerated value used to simulate the failures of the device. SeeTable 6-9.
SIM_DETAILED_MAINTENANCE This is a bit-enumerated value used to simulate the maintenance requests of the device. SeeTable 6-10.
SIM_DETAILED_STATUS This is a bit-enumerated value used to simulate the stati of the device. SeeTable 6-11.
SPAN_CAL_DATE_n The date the last span calibration w as performed.
ST_REV See FF-891 section 5.3.
STATS_ATTEMPTS Total number of messages sent to the transducer a/d board.
STATS_FAILURES Total number of failed a/d board message attempts.
STATS_TIMEOUTS Total number of timed out a/d board message attempts.
STRATEGY See FF-891 section 5.3.
TAG_DESC See FF-891 section 5.3.
TRANSDUCER_DIRECTORY See FF-903 section 3.3.
TRANSDUCER_TYPE See FF-903 sections 3.3.
UPDATE_EVT See FF-891 section 5.3.
XD_ERROR SeeTable 6-9, Table 6-10, Table 6-11and FF-903 section 3.3.
ZERO_CAL_DATE_n The date the last zero calibration w as performed.

Tab. 2-2 (cont’d)


Transducer Block Parameter Descriptions

2-6
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
2-3 Transducer Block Parameter Attribute Definitions

2-3 Transducer Block Parameter Attribute Definitions


The parameters not described in FF-891 or FF- as the one in FF-891, except that the columns
903 are described in the following table. This for Use/Model and Direction have been
table also includes some parameters defined omitted because all parameters are contained.
in FF-891 or FF-903, but are redefined for this Refer to FF-891, section 5 – Block Parame-
application. This table has the same definitions ters, for an explanation of this table.
Obj Data Type / Initial Range
Param eter Mnem onic Store Size Valid Range Units Mode Other
Type Structure Value Check
ACCESS_MODE S Unsigned8 S 1 See Table 6-8 0 Enumerated Yes
ANALYZER_HW_VERSION S Octet String S 30 none Read Only
ANALYZER_OPTS S Unsigned8 S 1 See Table 6-7 Bit String Read Only
ANALYZER_SW_VERSION S Octet String S 30 none Read Only
CAL_CONSTANT_n S Floating Point D 4 none Read Only
CAL_GAS_TIME S Unsigned16 S 2 2 - 1000 2 Sec O/S Note 5-2 Yes
CAL_OPTS S Unsigned8 S 1 See Table 6-5 0 Bit String O/S Note 5-2 Yes
CAL_POINT_HI_n S Floating Point S 4 100 CAL_UNIT O/S Note 5-2
CAL_POINT_LO_n S Floating Point S 4 0 CAL_UNIT O/S Note 5-2
CAL_SLOPE_n S Floating Point D 4 0 Read Only
CAL_SPAN_DATE_n S Date-(11) D 7 0 O/S Note 5-4 Yes
CAL_SPAN_INTERVAL_n S Unsigned16 S 2 0-999 0 Hours O/S Note 5-4 Yes
CAL_SPAN_TOLERANCE_n S Floating Point S 4 0 - 100 10 % O/S Note 5-2 Yes
CAL_STATE S Unsigned16 D 2 See Table 6-2 0 Bit String Read Only
CAL_STEP S Unsigned8 D 1 See Table 6-3 0 Enumerated Note 5-2 Yes
CAL_UNIT_n S Unsigned16 S 2 ppm, % % Enumerated O/S Note 5-2
(see FF-903
sect. 4.10 Units Codes)
CAL_ZERO_DATE_n S Date-(11) D 7 0 O/S Note 5-4 Yes
CAL_ZERO_INTERVAL_n S Unsigned16 S 2 0-999 0 Hours O/S Note 5-4 Yes
CAL_ZERO_SPAN_DATE_n S Date-(11) D 7 0 O/S Note 5-4 Yes
CAL_ZERO_SPAN_INTERVAL_n S Unsigned16 S 2 0-999 0 Hours O/S Note 5-4 Yes
CAL_ZERO_TOLERANCE_n S Floating Point S 4 0 - 100 10 % O/S Note 5-2 Yes
COLLECTION_DIRECTORY A Array of Unsigned32 N Var FF-903 section 3.3 None Read Only
DETAILED_FAILURE S Unsigned32 D 4 See Table 6-9 0 Bit String Read Only
DETAILED_MAINTENANCE S Unsigned32 D 4 See Table 6-10 0 Bit String Read Only
DETAILED_STATUS S Unsigned32 D 4 See Table 6-11 0 Bit String Read Only
DEVICE_TIME S Date-(11) D 7 0 Yes
FUNCTION_CALL S Unsigned8 D 1 See Table 6-12 0 Enumerated O/S Note 5-2 Yes
GAS_CTRL_STATE S Unsigned16 D 2 See Table 6-1 0 Bit String Note 5-2 Yes
MANUFACTURING_DATE S Octet String S 30 0 none Read Only
MEASUREMENT_OPTS S Unsigned16 S 2 See Table 6-4 0 Bit String O/S Note 5-2 Yes
MODULE_SN S Octet String S 20 0 none Read Only
PRIMARY_VALUE_n R DS-65 D 5 0 PVR Read Only

Tab. 2-3
Transducer Block Parameter Attribute Definitions

2-7
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
2-3 Transducer Block Parameter Attribute Definitions

Obj Data Type / Initial Range


Parameter Mnemonic Store Size Valid Range Units Mode Other
Type Structure Value Check
PRIMARY_VALUE_RANGE_n R DS-68 S 11 0-100% PVR O/S Note 5-2
See section 4.1 in FF- 65535
PRIMARY_VALUE_TYPE_n S Unsigned16 S 2 Enumerated Read Only
903 (other)
SENSOR_AVG_CYCLES_n S Unsigned16 S 2 1 none Read Only
0: arithmetic
SENSOR_AVG_METHOD_n S Unsigned8 S 1 0 Enumerated Read Only
1: sliding
SENSOR_CROSS_INTF_OFFSET_n S Floating Point D 4 none Read Only
SENSOR_FILTER_VALUE_n S Floating Point S 4 0.01-1000 2 Sec O/S Note 5-2 Yes
SENSOR_FLOW_n S DS-65 D 5 0 l/min Read Only
SENSOR_ID_n S Octet String S 30 NULL none Read Only
SENSOR_NOISE_LEVEL_n S Floating Point S 4 0 – 100 0 % Read Only
SENSOR_NOISE_REFVAL_n S Floating Point S 4 0 – 1000000 0 ppm Read Only
SENSOR_NOISE_TUNE_n S Floating Point S 4 1 – 1000 0 none Read Only
SENSOR_OPTS_n S Unsigned32 S 4 See Table 6-6 0 Bit String Read Only
SENSOR_PRESSURE_n R DS-65 D 5 0.0-2000.0 1013 hPa Note 5-1 Note 5-3
SENSOR_PRESSURE_FACTOR_n S Floating Point D 4 1 none Read Only
SENSOR_RANGE_n R DS-68 S 11 0-100 % PVR Read Only

SENSOR_RAW_CONCENTRATION_n S Floating Point D 4 0 ADC Counts Read Only

SENSOR_STEMPERATURE_n S Floating Point D 4 0 °C Read Only


SENSOR_TEMP_FACTOR_n S Floating Point D 4 1 none Read Only
SENSOR_TEMP_OFFSET_n S Floating Point D 4 0 none Read Only
See FF-903 65535
SENSOR_TYPE_n S Unsigned16 S 2 Enumerated Read Only
sect. 4.3 Sensor Types (Non-Std)
SENSOR_ZTEMPERATURE_n S Floating Point D 4 0 °C Read Only
SIM_DETAILED_FAILURE S Unsigned32 D 4 See Table 6-9 0 Bit String O/S Note 5-5
SIM_DETAILED_MAINTENANCE A Array of Unsigned8 D 4 See Table 6-10 0 Bit String O/S Note 5-5
SIM_DETAILED_STATUS S Unsigned32 D 4 See Table 6-11 0 Bit String O/S Note 5-5
SPAN_CAL_DATE_n S Date-(11) S 7 0 none Read Only
STATS_ATTEMPTS S Unsigned32 D 4 0-16777215 0 Read Only
STATS_FAILURES S Unsigned32 D 4 0-16777215 0 Read Only
STATS_TIMEOUTS S Unsigned32 D 4 0-16777215 0 Read Only
ZERO_CAL_DATE_n S Date-(11) S 7 0 none Read Only

Tab. 2-3
Transducer Block Parameter Attribute Definitions

Note 5-1: Writable only if PRES_REMOTE bit of SENSOR_OPTS_n is set, otherwise is only
Readable.
Note 5-2: This parameter is Read Only if the “local parameter access active ” bit or the "parameter
access via serial service interface active" bit is on in the DETAILED_STATUS word.
Note 5-3: Range check is only done if in SENSOR_OPTS_n the bit PRES_CORR is set.
Note 5-4: This parameter is similar to Note 5-2 and additionally Read Only if VALVES_INST of
SENSOR_OPTS_n is cleared.
Note 5-5: Writable only if Simulation-bit of DETAILED_STATUS is set otherwise Read Only.

2-8
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
2-4 Transducer Block Enumerations

2-4 Transducer Block Enumerations


2-4-1 Gas Control State
FFValue of
Bit Number Description
GAS_CTRL_
15 0x8000 Sample Gas Valve for Snsr1 opened
14 0x4000 Zero Gas Valve for Snsr1 opened
13 0x2000 Span Gas Valve for Snsr1 opened
12 0x0100 Sample Gas pump for Snsr1 running
11 0x0800 Sample Gas Valve for Snsr2 opened
10 0x0400 Zero Gas Valve for Snsr2 opened
9 0x0200 Span Gas Valve for Snsr2 opened
8 0x0100 Sample Gas pump for Snsr2 running

Tab. 2-4
Gas Control State

During a running calibration procedure of a So it is refused to change this states by


sensor (see Table 2-5) the gas control states operator during this running procedures.
are controlled by this procedure.

2-4-2 Calibration States


FF-Value of
Bit Number Description
CAL_STATE
15 0x8000 running zero calibration on Snsr1
14 0x4000 running span calibration on Snsr1
13 0x2000 purging changed gas on Snsr1
12 0x1000 running cross interference calibration of Snsr2 onto Snsr1
11 0x0800 running zero calibration on Snsr2
10 0x0400 running span calibration on Snsr2
9 0x0200 purging changed gas on Snsr2
8 0x0100 running cross interference calibration of Snsr1 onto Snsr2

Tab. 2-5
Calibration States

2-9
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
2-4 Transducer Block Enumerations

2-4-3 Calibration Step Control

Value CAL_STEP – Description


0 No Action
1 Zero Calibration Snsr1
2 Zero Calibration Snsr2
3 Zero Calibration Snsr1+2
4 Span Calibration Snsr1
5 Span Calibration Snsr2
6 Span Calibration Snsr1+2
7 Zero & Span Calibration Snsr1
8 Zero & Span Calibration Snsr2
9 Zero & Span Calibration Snsr1+2
10 Cross Interference Calibration of Snsr2 onto Snsr1
11 Cross Interference Calibration of Snsr1 onto Snsr2
12 Cancel running Calibration of Snsr1
13 Cancel running Calibration of Snsr2
14 Cancel running Calibration of Snsr1+2
15 Load factory Calibration of Snsr1
16 Load factory Calibration of Snsr2
17 Load factory Calibration of Snsr1+2

Tab. 2-6
Calibration Control Enumerations

To start a calibration procedure of a sensor is If we do not want to wait for finishing the already
only allowed if there is no procedure already running procedure we have first to cancel it
running on the same sensor (seeTable 2-5). before starting the new procedure.

2-10
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
2-4 Transducer Block Enumerations

2-4-4 Measurement Options

V alue of
Bit Num be r Pne um onic De s cription
MEAS UREMENT_O PTS
15 0x8000 XCMP_1 Cross-Compensation Enabled f or Snsr1
14 0x4000 SPLINE_1 Multiple Splines Linearization Enabled f or Snsr1
13 0x2000 POLY NOM_1 4th Order Polynomial Linearization Enabled f or Snsr1
12 0x1000 reserved
11 0x0800 reserved
10 0x0400 reserved
9 0x0200 reserved
8 0x0100 reserved
7 0x0080 XCMP_2 Cross-Compensation Enabled f or Snsr2
6 0x0040 SPLINE_2 Multiple Splines Linearization Enabled f or Snsr2
5 0x0020 POLY NOM_2 4th Order Polynomial Linearization Enabled f or Snsr2

Tab. 2-7
Measurement Options

2-4-5 Calibration Options


Value of
Bit Num ber Description
CAL_O PTS
15 0x8000 Calibration Deviation Tolerance Check Enabled for Snsr1
14 0x4000 reserved
13 0x2000 reserved
12 0x1000 reserved
11 0x0800 Calibration Deviation Tolerance Check Enabled for Snsr2

Tab. 2-8
Calibration Options

2-11
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
2-4 Transducer Block Enumerations

2-4-6 Sensor Options

Value of
Bit Num ber Pneum onic Description
SENSOR_O PTS_n
31 0x80000000 not usable
30 0x40000000 MUX1_ZTEMP Multiplexer1 input is used for temperature zero correction
29 0x20000000 MUX2_ZTEMP Multiplexer2 input is used for temperature zero correction
28 0x10000000 OTHER_ZTEMP other sensor is used for temperature zero correction
27 0x08000000 reserved
26 0x04000000 MUX1_STEMP Multiplexer1 input is used for temperature span correction
25 0x02000000 MUX2_STEMP Multiplexer2 input is used for temperature span correction
24 0x01000000 OTHER_STEMP other sensor is used for temperature span correction of sensor
23 0x00800000 PRES_SENSOR pressure sensor installed
22 0x00400000 PRES_MANMEAS manual pressure input is used for pressure measurement
21 0x00200000 PRES_SNSMEAS built-in pressure sensor is used for pressure measurement
20 0x00100000 PRES_CORR pressure measurement is used for span correction
19 0x00080000 PRES_REMOTE remote pressure measurement is used for pressure measurement
18 0x00040000 reserved
17 0x00020000 reserved
16 0x00010000 reserved
15 0x00008000 FLOW_SENSOR flow sensor installed
14 0x00004000 PUMP_INST pump installed
13 0x00002000 VALVES_INST valves installed
12 0x00001000 HEATER_INST heater installed
Tab. 2-9
Sensor Options

2-4-7 Analyzer Options


Value of
Bit Num ber Description
ANALYZER_O PTS
7 0x80 Serial Gas Flow through Analyzer Cells (otherw ise parallel)
6 0x40 Sensor2 not built-in
5 0x20 FF host is master of date/time

Tab. 2-10
Analyzer Options

2-12
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
2-4 Transducer Block Enumerations

2-4-8 Access Mode Control


Value ACCESS_MODE – Description
0 Normal
1 Fieldbus access only

Tab. 2-11
Parameter Access Mode Enumerations (ACCESS_MODE)

2-4-9 Detailed Status

2-4-9-1 Detailed Maintenance


Bit Value of Value of XD_ERROR
Description
Num ber DETAILED_MAINTENANC E (see FF-903)
31 0x80000000 not usable
30 0x40000000 Deviation too high for zero calibration of Snsr1 CALIBRATION_FAILURE
29 0x20000000 Deviation too high for span calibration of Snsr1 CALIBRATION_FAILURE
28 0x10000000 Measurement too noisy during zero calibration of Snsr1 CALIBRATION_FAILURE
27 0x08000000 Measurement too noisy during span calibration of Snsr1 CALIBRATION_FAILURE
26 0x04000000 digital input notifies maintenance request for Snsr1 IO_FAILURE
25 0x02000000 reserved NONE
24 0x01000000 reserved NONE
23 0x00800000 reserved NONE
22 0x00400000 Deviation too high for zero calibration of Snsr2 CALIBRATION_FAILURE
21 0x00200000 Deviation too high for span calibration of Snsr2 CALIBRATION_FAILURE
20 0x00100000 Measurement too noisy during zero calibration of Snsr2 CALIBRATION_FAILURE
19 0x00080000 Measurement too noisy during span calibration of Snsr2 CALIBRATION_FAILURE
18 0x00040000 digital input notifies maintenance request for Snsr2 IO_FAILURE
17 0x00020000 reserved NONE
16 0x00010000 reserved NONE
15 0x00008000 Maintenance interval for the device expired GENERAL_FAILURE
14 0x00004000 factory configuration loaded DATA_INTEGRITY_FAILURE
13 0x00002000 measurement sensors running in w rong mode and IO_FAILURE
12 0x00001000 d li
reserved d NONE
11 0x00000800 reserved NONE
10 0x00000400 reserved NONE
9 0x00000200 reserved NONE
8 0x00000100 reserved NONE

Tab. 2-12
Detailed Maintenance

2-13
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
2-4 Transducer Block Enumerations

2-4-9-2 Detailed Failure


Bit Value of Value of XD_ERROR
Description
Num ber DETAILED_FAILURE (see FF-903)
31 0x80000000 not usable
30 0x40000000 Chopper motor turning fails for Snsr1 ELECTRICAL_FAILURE
29 0x20000000 A/D converter out of range for Snsr1 ALGORITHM_ERROR
28 0x10000000 Source light failed for Snsr1 ELECTRICAL_FAILURE
27 0x08000000 Detector component failed for Snsr1 ELECTRICAL_FAILURE
26 0x04000000 Heater control failed for Snsr1 ELECTRICAL_FAILURE
25 0x02000000 Sensor of temperature correction failed for Snsr1 IO_FAILURE
24 0x01000000 Pressure measurement for pressure correction failed for Snsr1 IO_FAILURE
23 0x00800000 digital input notifies failure for Snsr1 IO_FAILURE
22 0x00400000 interfering measurement onto Snsr1 failed IO_FAILURE
21 0x00200000 over temperature shut dow n for Snsr1 GENERAL_FAILURE
20 0x00100000 reserved NONE
19 0x00080000 reserved NONE
18 0x00040000 reserved NONE
17 0x00020000 reserved NONE
16 0x00010000 reserved NONE
15 0x00008000 reserved NONE
14 0x00004000 Chopper motor turning fails for Snsr2 ELECTRICAL_FAILURE
13 0x00002000 A/D converter out of range for Snsr2 ALGORITHM_ERROR
12 0x00001000 Source light failed for Snsr2 ELECTRICAL_FAILURE
11 0x00000800 Detector component failed for Snsr2 ELECTRICAL_FAILURE
10 0x00000400 Heater control failed for Snsr2 ELECTRICAL_FAILURE
9 0x00000200 Sensor of temperature correction failed for Snsr2 IO_FAILURE
8 0x00000100 Pressure measurement for pressure correction failed for Snsr2 IO_FAILURE
7 0x00000080 digital input notifies failure for Snsr2 IO_FAILURE
6 0x00000040 interfering measurement onto Snsr2 failed IO_FAILURE
5 0x00000020 over temperature shut dow n for Snsr2 GENERAL_FAILURE
4 0x00000010 reserved NONE
3 0x00000008 Communication to sensor electronics failed. ELECTRICAL_FAILURE
2 0x00000004 No communication to transducer device ELECTRICAL_FAILURE

Tab. 2-13
Detailed Failure

2-14
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
2-4 Transducer Block Enumerations

2-4-9-3 Detailed Status


Bit FF-Value of Value of XD_ERROR
Description
Num ber DETAILED_STATUS (see FF-903)
31 0x80000000 not usable
30 0x40000000 Raw signal for Snsr1 is a simulated one CONFIGURATION_ERROR
29 0x20000000 No valid sample gas measurement running for Snsr1 NONE
28 0x10000000 Any calibration in progress for Snsr1 NONE
27 0x08000000 Snsr1 is still in w arming up phase NONE
26 0x04000000 Snsr1 is in a defined state of measurement interruption NONE
25 0x02000000 Snsr1 is in standby-mode NONE
24 0x01000000 Any of secondary measurements for Snsr1 in simulation mode CONFIGURATION_ERROR
23 0x00800000 digital input notifies an 'out of service' mode for Snsr1 NONE
22 0x00400000 linearization procedure of Snsr1 produces an underflow ALGORITHM_ERROR
21 0x00200000 linearization procedure of Snsr1 produces an overflow ALGORITHM_ERROR
20 0x00100000 installed sample gas pump of Snsr1 not running NONE
19 0x00080000 reserved NONE
18 0x00040000 reserved NONE
17 0x00020000 reserved NONE
16 0x00010000 reserved NONE
15 0x00008000 Snsr2 not built in NONE
14 0x00004000 Raw signal for Snsr2 is a simulated one CONFIGURATION_ERROR
13 0x00002000 No valid sample gas measurement running for Snsr2 NONE
12 0x00001000 Any calibration in progress for Snsr2 NONE
11 0x00000800 Snsr2 is still in w arming up phase NONE
10 0x00000400 Snsr2 is in a defined state of measurement interruption NONE
9 0x00000200 Snsr2 is in standby-mode NONE
8 0x00000100 Any of secondary measurements for Snsr2 in simulation mode CONFIGURATION_ERROR
7 0x00000080 digital input notifies an 'out of service' mode for Snsr2 NONE
6 0x00000040 linearization procedure of Snsr2 produces an underflow ALGORITHM_ERROR
5 0x00000020 linearization procedure of Snsr2 produces an overflow ALGORITHM_ERROR
4 0x00000010 installed sample gas pump of Snsr2 not running NONE
3 0x00000008 local parameter access active NONE
2 0x00000004 parameter access via local serial service interface active NONE
1 0x00000002 Status simulation active NONE

Tab. 2-14
DetailedStatus

2-15
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
2-4 Transducer Block Enumerations

2-4-10 Function Call Control


Value FUNCTION_CALL – Description
0 No Action
1 Acknow ledge and clear Failures Snsr1
2 Acknow ledge and clear Maintenance Requests Snsr1
3 Acknow ledge and clear Function Controls Snsr1
4 Acknow ledge and clear Failures Snsr2
5 Acknow ledge and clear Maintenance Requests Snsr2
6 Acknow ledge and clear Function Controls Snsr2
7 Set FF Host as master of date/time
8 Set sensor device's clock as master of date/time
9 Load transducer's factory configuration

Tab. 2-15
Function Call Enumerations (FUNCTION_CALL)

2-16
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
2-5 Transducer Block Channel Assignments

2-5 Transducer Block Channel Assignments


2-5-1 I/O Channel Assignments for AI-Blocks

Transducer Block XD_SCALE


Process Variable
Channel Value UNITS
1 PRIMARY_VALUE_1 %, ppm
2 PRIMARY_VALUE_2 %, ppm
3 SENSOR_FLOW_1 l/min
4 SENSOR_FLOW_2 l/min
5 SENSOR_PRESSURE_1(read) hPa
6 SENSOR_PRESSURE_2(read) hPa

Tab. 2-16
I/O Channel Assignments for AI-Blocks

2-5-2 I/O Channel Assignment for A0-Blocks

Transducer Block XD_SCALE


Process Variable
Channel Value UNITS
7 SENSOR_PRESSURE_1(w rite) hPa
8 SENSOR_PRESSURE_2(w rite) hPa

Tab. 2-17
I/O Channel Assignments for AI-Blocks

The assignment of SENSOR_PRESSURE_n is only possible if the device has not


enabled the PRES_SNSMEAS-bit of SENSOR_OPTS_n (seeTable 2-9)

2-17
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
2-6 Simulation of TBlk States

2-6 Simulation of TBlk States


The TBlk parameters which are evaluated for Having this bit activated the values of
the PWAs (=PlantWeb Alerts) D E T A I L E D _ F A I L U R E ,
(DETAILED_FAILURE, DETAILED_STATUS DETAILED_MAINTENANCE,
and DETAILED_MAINTENANCE) can be DETAILED_STATUS equal the values of
simulated. SIM_DETAILED_FAILURE,
For the simulation use the SIM_DETAILED_MAINTENANCE and
parameters SIM_DETAILED_FAILURE, SIM_DETAILED_STATUS.
SIM_DETAILED_MAINTENANCE and That means the user has the opportunity to
SIM_DETAILED_STATUS. simulate the TBlk-states by writing to the
For activating the simulation mode of these use SIM_DETAILED_XXXX-parameter bits. By
the bit „Status simulation active“ in this means he has the opportunity to check the
SIM_DETAILED_STATUS . correct mapping onto the PWA’s
XXXX_ACTIVE-parameters of the RBlk.

2-7 Supported Transducer Block Errors

2-7-1 Out of Service


Set whenever the transducer block actual mode
is OOS

2-7-2 Block Configuration Error


Set whenever there is a communication error
between the round board and the a/d board.

2-7-3 Input Failure/ Process Variable has BAD Status


Set whenever PRIMARY_VARIABLE_1 or
PRIMARY_VARIABLE_2 has BAD status.

2-7-4 Device needs Maintenance Now


Set whenever DETAILED_FAILURE is unequal ‘0’.
2-7-5 Simulate Active
Set whenever „Status simulation active“-bit of
DETAILED_STATUS is set.

2-7-6 Other Error


Set whenever XD_ERROR is non-zero.

2-18
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus

SECTION 3
Resource Block

3-1 Mapping of the PlantWeb Alerts

What this Alert is What is the effect on


Advisory Alert R block Tblock Relevant Param eters Health Bit
Detecting? the instrument?
PlantWeb Alerts The alerts are simulated RB.BLOCK_ERR DETAILED_STATUS RB.SIMULATE_STATE
Simulate Active and might not come from 3 Simulate Active 30 Status simulation active
live detection 90 2
PWA_SIMULATE
Inactive Measurement Local operator or The affected PV quality DETAILED_STATUS DETAILED_STATUS
Mode technician sw itched status w ill go to BAD 5 Sensor 1 is in a defined state of measurement pause 2 No valid sample gas
device into inactive state. 21 Sensor 2 is in a defined state of measurement pause measurement..Snsr1 90 3
6 Sensor 1 is in standby-mode 18 No valid sample gas
22 Sensor 2 is in standby-mode measurement..Snsr2
Inactive Gas Pump There is installed a sample The affected PV quality DETAILED_STATUS SENSOR_OPTS_1:PUMP_INST
gas pump but it is not status w ill go to BAD 11 Installed sample gas pump of sensor 1 not running SENSOR_OPTS_1:FLOW_SENSOR
sw itched on. 27 Installed sample gas pump of sensor 2 not running SENSOR_FLOW_1:value
SENSOR_FLOW_1:status
SENSOR_OPTS_2:PUMP_INST 90 4
SENSOR_OPTS_2:FLOW_SENSOR
SENSOR_FLOW_2:value
SENSOR_FLOW_2:status

Maintenance Interval Maintenance period No impact DETAILED_MAINTENANCE


90 5
Expired defined by user is due 16 maintenance interval expired
Diagnostic Condition Local operator or No impact DETAILED_STATUS
Active technician sw itched 1 raw signal simulated for sens1
device into 7 2nd measurement simulated for sens1
simulation/diagnostic state. 17 raw signal simulated for sens2 90 8
23 2nd measurement simulated for sens2
8 digital input notifies 'out of service' mode for sensor 1
24 digital input notifies 'out of service' mode for sensor 2

Tab. 3-1
MLT PWA Mapping - Advice

What this Alert is What is the effect


Maintenance Alert Rblock Tblock Relevant Param eters Health Bit
Detecting? on the instrum ent?
Calibration Error During the Analyzer continues to RB.BLOCK_ERR DETAILED_MAINTENANCE CAL_OPTS:0
calibration, the operate, but affected 0 Other 1 deviation of zero cal Sens1 CAL_OPTS:4
deviation or noise PV quality status w ill 2 deviation of span cal Sens1
exceeded go to UNCERTAIN. 3 noise during zero cal Sens1
acceptable ranges. 4 noise during span cal Sens1 70 1
9 deviation of zero cal Sens2
10 deviation of span cal Sens2
11 noise during zero cal Sens2
12 noise during span cal Sens2
External Maintenance A digital input Analyzer continues to DETAILED_MAINTENANCE
Request signals a operate, but affected 5 digital input notify for Snsr1
maintenance PV quality status w ill 13 digital input notify for Snsr2 70 2
request from an go to UNCERTAIN.
external facility.
Configuration Error Analyzer Analyzer continues to DETAILED_MAINTENANCE
configuration does operate, but affected 17 failed battery caused factory config
not match definition PV quality status w ill 18 w rong mode of sensors 70 4
or configuration has go to UNCERTAIN.
been lost
Linearizer out of range The raw signal Analyzer continues to DETAILED_STATUS PRIMARY_VALUE_1: value
readings are out of operate, but affected 9 linearization proc. of sensor 1 produces an underflow SENSOR_RAW_CONCENTRATION_1
linearizer's defined PV quality status w ill 10 linearization proc. of sensor 1 produces an overflow PRIMARY_VALUE_2: value 40 16
range. go to UNCERTAIN. 25 linearization proc. of sensor 2 produces an underflow SENSOR_RAW_CONCENTRATION_2
26 linearization proc. of sensor 2 produces an overflow

Tab. 3-2
MLT PWA Mapping - Maintenance

3-1
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
3-1 Mapping of the PlantWeb Alerts

What this Alert is What is the effect on


Failure Alert Rblock Tblock Relevant Param eters Health Bit
Detecting? the instrum ent?
External Failure Signal A digital input signals The af fected PV quality DETAILED_FAILURE
a f ailure from an status w ill go to BAD 9 digital input notifies failure f or Snsr1
10 9
external facility. 25 digital input notifies failure f or Snsr2

Temperature Sensor This detects an out The af fected PV quality DETAILED_FAILURE SENSOR_ZTEMPERATURE_1
Malfunction of range status w ill go to BAD 6 Sensor of temp. corr. failed for sensor 1 SENSOR_STEMPERATURE_1
10 11
temperature sensor. 22 Sensor of temp. corr. failed for sensor 2 SENSOR_ZTEMPERATURE_2
SENSOR_STEMPERATURE_2
Pressure The sensor w hich is The af fected PV quality DETAILED_FAILURE SENSOR_PRESSURE_1:value
Compensation used for pressure status w ill go to BAD 7 Pressure measurement for pressure SENSOR_PRESSURE_1:status
Malfunction compensation correction failed for Snsr1 SENSOR_PRESSURE_2:value
10 12
calculations is out of 23 Pressure measurement for pressure SENSOR_PRESSURE_2:status
order. correction failed for Snsr2 SENSOR_OPTS_1: PRES_REMOTE
SENSOR_OPTS_2: PRES_REMOTE
Interf ering Gas It notif ies a failure in The af fected PV quality DETAILED_FAILURE PRIMARY_VALUE_2:value
Compensation Failure interfering gas status w ill go to BAD 8 interfering meas. onto Snsr1 f ailed PRIMARY_VALUE_2:status
10 13
measurements. 24 interfering meas. onto Snsr2 f ailed PRIMARY_VALUE_1:value
PRIMARY_VALUE_1:status
Temperature out of This detects an out The af fected PV quality DETAILED_FAILURE SENSOR_ZTEMPERATURE_1
Range of range status w ill go to BAD 5 Heater control failed for Snsr1 SENSOR_STEMPERATURE_1
temperature inside 21 Heater control failed for Snsr2 SENSOR_ZTEMPERATURE_2
10 14
the device. 10 over temperature shut dow n for Snsr1 SENSOR_STEMPERATURE_2
26 over temperature shut dow n for Snsr2 SENSOR_OPTS_1: HEATER_INST
SENSOR_OPTS_2: HEATER_INST
Sensor Engine Various faults w ill output w ill not be valid DETAILED_FAILURE
Hardw are Failure cause the analysis or analyzer w ill not 1 Chopper motor failure Snsr1
to be bad includig operate 17 Chopper motor failure Snsr2
failure in chopper 2 A/D converter out of range for Snsr1
motor, light source 18 A/D converter out of range for Snsr2
10 16
or the detector 3 Source light failed for Snsr1
component 19 Source light failed for Snsr2
4 Detector component failed for Snsr1
20 Detector component failed for Snsr2
28 Sensor Communication failed
Output Board NV The non-volatile RB.BLOCK_ERR
Memory Failure parameter storage 0 Other
on the CPU board 11 Lost NV Data
10 22
has become
unreliable RB.DETAILED_STATUS
4 NV Integrity error
Sensor Board This occurs w hen Data w ill be unusable, RB.BLOCK_ERR DETAILED_FAILURE
Electronics Failure the electronics of bad quality alarm w ill 0 Other 29 No communication to transducer device
the sensor can not be sent to the operator 13 Device Needs
reliably send data to and the analyzer w ill be Maintenance Now
the Fieldbus Output taken out of service. 15 Out of service 10 23
Electronics Board.
RB.DETAILED_STATUS
1 Sensor transducer error

Output Board This occurs w hen Data w ill be unusable, RB.BLOCK_ERR


Electronics Failure the electronics can a bad quality alarm w ill 0 Other
not reliably collect be sent to the operator 9 Memory Failure
data from the and the analyzer w ill be 13 Device Needs
sensors taken out of service. Maintenance Now
15 Out of service
10 24
RB.DETAILED_STATUS
2 Manufacturing block
integrity error
5 Register test failure
6 ROM integrity error

Tab. 3-3
MLT PWA Mapping - Failed

3-2
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
3-2 PWA_Simulate

3-2 PWA_SIMULATE
Having PWA_SIMULATE == ON allows There are some bits of DETAILED_STATUS
simulating the RBlk-parameters of the RBlk (not TBlk!) which are mapped to
FAILED_ACTIVE, MAINT_ACTIVE and FAILED_ACTIVE („Electronics Failure“ and
ADVISE_ACTIVE. „NV memory failure“).
„Allow simulating“ means that these parameters We also allow simulating them in this state.
get write permission and the host’s written value Hereby is used a wired-OR logic of these
is the only one which is used for parameter’s DETAILED_STATUS bits and of the
read back value. The data which come via appropriate FAILED_ACTIVE bits.
1451-protocol from the MLT itself is not used
in this case (also no wired-OR).

3-3
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003

3-4
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus

SECTION 4
Analog Input (AI) Function Block

OUT = The block output value and status


OUT_D = Discrete output that signals a selected alarm condition
Fig. 4-1
Analog input function block

The Analog Input (AI) function block processes In Automatic mode, the block’s output
field device measurements and makes them parameter (OUT) reflects the process variable
available to other function blocks. The output (PV) value and status. In Manual mode, OUT
value from the AI block is in engineering units may be set manually. The Manual mode is
and contains a status indicating the quality of reflected on the output status. A discrete output
the measurement. The measuring device may (OUT_D) is provided to indicate whether a
have several measurements or derived values selected alarm condition is active. Alarm
available in different channels. Use the channel detection is based on the OUT value and user
number to define the variable that the AI block specified alarm limits. Figure 3-2 on page 3–3
processes. illustrates the internal components of the AI
The AI block supports alarming, signal scaling, function block while table 3-1 lists the AI block
signal filtering, signal status calculation, mode parameters and their units of measure,
control, and simulation. descriptions and index numbers.
Index
Param eter Units Description
Num ber
ACK_OPTION 23 None Used to set auto acknow ledgment of alarms.
ALARM_HYS 24 Percent The amount the alarm value must return w ithin the alarm limit before the associated active
alarm condition clears.
ALARM_SEL 38 None Used to select the process alarm conditions that w ill cause the OUT_D parameter to be
set.
ALARM_SUM 22 None The summary alarm is used for all process alarms in the block. The cause of the alert is
entered in the subcode field. The first alert to become active w ill set the Active status in
the Status parameter. As soon as the Unreported status is cleared by the alert reporting
task, another block alert may be reported w ithout clearing the Active status, if the
subcode has changed.
ALERT_KEY 4 None The identification number of the plant unit. This information may be used in the host for
sorting alarms, etc.
BLOCK_ALM 21 None The block alarm is used for all configuration, hardw are, connection failure or system
problems in the block. The cause of the alert is entered in the subcode field. The first alert
to become active w ill set the Active status in the Status parameter. As soon as the
Unreported status is cleared by the alert reporting task, another block alert may be
reported w ithout clearing the Active status, if the subcode has changed.

Tab. 4-1
Definitions of Analog Input Function Block System Parameters

4-1
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
4 Analog Input (AI) Function Block

Index
Param eter Units Description
Num ber
BLOCK_ERR 6 None This parameter reflects the error status associated w ith the hardw are or softw are
components associated w ith a block. It is a bit string, so that multiple errors may be
show n.
CHANNEL 15 None The CHANNEL value is used to select the measurement value. Refer to the appropriate
device manual for information about the specific channels available in each device. The
CHANNEL parameter must be configured before configuring the XD_SCALE parameter.
FIELD_VAL 19 Percent The value and status from the transducer block or from the simulated input w hen
simulation is enabled.
GRANT_DENY 12 None Options for controlling access of host computers and local control panels to operating,
tuning, and alarm parameters of the block. Not used by device.
HI_ALM 34 None The HI alarm data, w hich includes a value of the alarm, a timestamp of occurrence and
the state of the alarm.
HI_HI_ALM 33 None The HI HI alarm data, w hich includes a value of the alarm, a timestamp of occurrence and
the state of the alarm.
HI_HI_LIM 26 EU of The setting for the alarm limit used to detect the HI HI alarm condition.
PV_SCALE
HI_HI_PRI 25 None The priority of the HI HI alarm.
HI_LIM 28 EU of The setting for the alarm limit used to detect the HI alarm condition.
PV_SCALE
HI_PRI 27 None The priority of the HI alarm.
IO_OPTS 13 None Allow s the selection of input/output options used to alter the PV. Low cutoff enabled is
the only selectable option.
L_TYPE 16 None Linearization type. Determines w hether the field value is used directly (Direct), is
converted linearly (Indirect), or is converted w ith the square root (Indirect Square Root).

LO_ALM 35 None The LO alarm data, w hich includes a value of the alarm, a timestamp of occurrence and
the state of the alarm.
LO_LIM 30 EU of The setting for the alarm limit used to detect the LO alarm condition.
PV_SCALE
LO_LO_ALM 36 None The LO LO alarm data, w hich includes a value of the alarm, a timestamp of occurrence
and the state of the alarm.
LO_LO_LIM 32 EU of The setting for the alarm limit used to detect the LO LO alarm condition.
PV_SCALE
LO_LO_PRI 31 None The priority of the LO LO alarm.
LO_PRI 29 None The priority of the LO alarm.
LOW_CUT 17 % If percentage value of transducer input fails below this, PV = 0.
MODE_BLK 5 None The actual, target, permitted, and normal modes of the block.
Target: The mode to “go to”
Actual: The mode the “block is currently in”
Permitted: Allow ed modes that target may take on
Normal: Most common mode for target
OUT 8 EU of The block output value and status.
OUT_SCALE
OUT_D 37 None Discrete output to indicate a selected alarm condition.
OUT_SCALE 11 None The high and low scale values, engineering units code, and number of digits to the right
of the decimal point associated w ith OUT.
PV 7 EU of The process variable used in block execution.
XD_SCALE
PV_FTIME 18 Seconds The time constant of the first-order PV filter. It is the time required for a 63% change in
the IN value.
SIMULATE 9 None A group of data that contains the current transducer value and status, the simulated
transducer value and status, and the enable/disable bit.
STRATEGY 3 None The strategy field can be used to identify grouping of blocks. This data is not checked or
processed by the block.
ST_REV 1 None The revision level of the static data associated w ith the function block. The revision value
w ill be incremented each time a static parameter value in the block is changed.

Tab. 4-1 (cont’d)


Definitions of Analog Input Function Block System Parameters

4-2
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
4-1 Simulation

Index
Param eter Units Description
Num ber
TAG_DESC 2 None The user description of the intended application of the block.
UPDATE_EVT 20 None This alert is generated by any change to the static data.
VAR_INDEX 39 % of OUT The average absolute error betw een the PV and its previous mean value over that
Range evaluation time defined by VAR_SCAN.
VAR_SCAN 40 Seconds The time over w hich the VAR_INDEX is evaluated.
XD_SCALE 10 None The high and low scale values, engineering units code, and number of digits to the right
of the decimal point associated w ith the channel input value. The XD_SCALE units code
must match the units code of the measurement channel in the transducer block. If the
units do not match, the block w ill not transition to MAN or AUTO.

Tab. 4-1 (cont’d)


Definitions of Analog Input Function Block System Parameters

4-1 Simulation
To support testing, either change the mode of All Fieldbus instruments have a
the block to manual and adjust the output value, simulation jumper. As a safety
or enable simulation through the configuration measure, the jumper has to be
tool and manually enter a value for the reset every time there is a power
measurement value and its status. In both interruption. This measure is to
cases, the ENABLE jumper on the field device prevent devices that went
must first be set. through simulation in the
With simulation enabled, the actual staging process from being
measurement value has no impact on the OUT installed with simulation
value or the status. enabled.
Analog
Measurement

ALARM_TYPE
Access HI_HI_LIM
Analog HI_LIM
Meas. LO_LO_LIM Alarm
LO_LIM Detection OUT_D
ALARM_HYS
CHANNEL
LOW_CUT

Cutoff Filter OUT


Convert PV Status
Sq Root Calc.

SIMULATE
OUT = The block output value and status
L_TYPE
PV_FTIME MODE OUT_D= Discrete output that signals a
selected alarm condition
FIELD_VAL
IO_OPTS
STATUS_OPTS
OUT_SCALE
XD_SCALE

Fig. 4-2
Analog Input Function Block Schematic

4-3
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
4-2 Filtering

OUT (mode in man)

OUT (mode in auto)

PV

63% of Change

FIELD_VAL

Time (seconds)

PV_FTIME

Fig. 4-3
Analog Input Function Block Timing Diagram

4-2 Filtering
The filtering feature changes the response time The filter time constant (in seconds) can be
of the device to smooth variations in output adjusted using the PV_FTIME parameter. Set
readings caused by rapid changes in input. the filter time constant to zero to disable the
filter feature.

4-3 Signal Conversion


Set the signal conversion type with the View the converted signal (in percent of
Linearization Type (L_TYPE) parameter. XD_SCALE) through the FIELD_VAL
parameter.

100 x (Channel Value - EU * @0% )


FIELD_VAL =
(EU * @100% − EU * @ 0% ) *XD_SCALE values

4-4
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
4-3 Signal Conversion

Choose from direct, indirect, or indirect square


root signal conversion with the L_TYPE
parameter.
• Direct
Direct signal conversion allows the signal input value (or the simulated value when
to pass through the accessed channel simulation is enabled).
PV = Channel Value

• Indirect
Indirect signal conversion converts the simulation is enabled) from its specified
signal linearly to the accessed channel range (XD_SCALE) to the range and units
input value (or the simulated value when of the PV and OUT parameters
(OUT_SCALE).
 FIELD _ VAL 
PV =   x (EU * * @100% − EU * * @ 0% ) + EI * * @ 0%
 100 
*OUT_SCALE values

• Indirect Square Root


Indirect Square Root signal conversion
takes the square root of the value
computed with the indirect signal
conversion and scales it to the range and
units of the PV and OUT parameters.

 FIELD _ VAL 
PV =   x (EU * *@100% − EU * *@ 0% ) + eu * *@ 0%
 100 
*OUT_SCALE values

When the converted input value is below the


limit specified by the LOW_CUT parameter,
and the Low Cutoff I/O option (IO_OPTS) is Low Cutoff is the only I/O option
enabled (True), a value of zero is used for the supported by the AI block. It is
converted value (PV). This option is useful to possible to set the I/O option in
eliminate false readings when the differential Manual or Out of Service mode
pressure measurement is close to zero, and it only.
may also be useful with zero-based
measurement devices such as flow meters.

4-5
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
4-4 Block Errors

4-4 Block Errors


Table 32 lists conditions reported in the
BLOCK_ERR parameter. Conditions in italics
are inactive for the AI block and are here listed
for reference only.
Condition Condition Name and Description
Number
0 Other
1 Block Configuration Error: the selected channel carries a measurement that is incompatible w ith the
engineering units selected in XD_SCALE, the L_TYPE parameter is not configured, or CHANNEL = zero.
2 Link Configuration Error
3 Sim ulate Active: Simulation is enabled and the block is using a simulated value in its execution.
4 Local Override
5 Device Fault State Set
6 Device Needs Maintenance Soon
7 Input Failure/Process Variable has Bad Status: The hardw are is bad, or a bad status is being simulated.
8 Output Failure: The output is bad based primarily upon a bad input.
9 Memory Failure
10 Lost Static Data
11 Lost NV Data
12 Readback Check Failed
13 Device Needs Maintenance Now
14 Power Up
15 Out of Service: The actual mode is out of service.

Tab. 4-2
Block Error Conditions

4-5 Modes
The AI Function Block supports three modes
of operation as defined by the MODE_BLK
parameter:
• Manual (Man) The block output (OUT) • Out of Service (O/S) The block is not
may be set manually processed. FIELD_VAL and PV are not
• Automatic (Auto) OUT reflects the ana- updated and the OUT status is set to Bad:
log input measurement or the simulated Out of Service. The BLOCK_ERR
value when simulation is enabled. parameter shows Out of Service. In this
mode, changes can be made to all
configurable parameters. The target mode
of a block may be restricted to one or more
of the supported modes.

4-6
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
4-6 Alarm Detection

4-6 Alarm Detection


A block alarm will be generated whenever the In order to avoid alarm chattering when the va-
BLOCK_ERR has an error bit set. The types riable is oscillating around the alarm limit, an
of block error for the AI block are defined above. alarm hysteresis in percent of the PV span can
Process Alarm detection is based on the OUT be set using the ALARM_HYS parameter. The
value. The alarm limits of the following standard priority of each alarm is set in the following
alarms can be configured: parameters:
• High (HI_LIM) • HI_PRI
• High high (HI_HI_LIM) • HI_HI_PRI
• Low (LO_LIM) • LO_PRI
• Low low (LO_LO_LIM) • LO_LO_PRI

Alarms are grouped into five levels of priority:


Priority Priority Description Number
0 The priority of an alarm condition changes to 0 after the condition
that caused the alarm is corrected.
1 An alarm condition w ith a priority of 1 is recognized by the
system, but is not reported to the operator.
2 An alarm condition w ith a priority of 2 is reported to the operator,
but does not require operator attention (such as diagnostics and
system alerts).
03. Jul Alarm conditions of priority 3 to 7 are advisory alarms of
increasing priority.
Aug 15 Alarm conditions of priority 8 to 15 are critical alarms of increasing
priority.

Tab. 4-3
Alarm Priorities

4-7
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
4-7 Status Handling

4-7 Status Handling


Normally, the status of the PV reflects the status In the STATUS_OPTS parameter, select from
of the measurement value, the operating the following options to control the status
condition of the I/O card, and any active alarm handling:
condition. In Auto mode, OUT reflects the value • BAD if Limited – sets the OUT status
and status quality of the PV. In Man mode, the quality to Bad when the value is higher or
OUT status constant limit is set to indicate that lower than the sensor limits.
the value is a constant and the OUT status is • Uncertain if Limited – sets the OUT
Good. status quality to Uncertain when the value
The Uncertain - EU range violation status is is higher or lower than the sensor limits.
always set, and the PV status is set high- or • Uncertain if in Manual mode – The
low-limited if the sensor limits for conversion status of the Output is set to Uncertain
are exceeded. when the mode is set to Manual.

The instrument must be in Manual


or Out of Service mode to set the
status option.
The AI block only supports the
BAD if Limited option. Unsupported
options are not grayed out; they
appear on the screen in the same
manner as supported options.

4-8 Advanced Features


The AI function block provided with Emerson
Fieldbus devices provides added capability
through the addition of the following
parameters:
• ALARM_TYPE – Allows one or more of • VAR_SCAN – Time period in seconds
the process alarm conditions detected by over which the variability index
the AI function block to be used in setting (VAR_INDEX) is computed.
its OUT_D parameter. • VAR_INDEX – Process variability index
• OUT_D – Discrete output of the AI function measured as the integral of average ab-
block based on the detection of process solute error between PV and its mean
alarm condition(s). This parameter may be value over the previous evaluation period.
linked to other function blocks that require This index is calculated as a percent of
a discrete input based on the detected OUT span and is updated at the end of
alarm condition. the time period defined by VAR_SCAN.

4-8
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
4-9 Applicatin Information

4-9 Application Information


The configuration of the AI function block and
its associated output channels depends on the
specific application. A typical configuration for
the AI block involves the following parameters:
• CHANNEL If the device supports more • SCALING XD_SCALE provides the
than one measurement, verify that the range and units of the measurement and
selected channel contains the appropriate OUT_SCALE provides the range and
measurement or derived value. engineering units of the output.
• L_TYPE
Select Direct when the measurement is
already in the engineering units that are
desired for the block output.
Select Indirect when it is desired to
convert the measured variable into
another, for example, pressure into level
or flow into energy.
Select Indirect Square Root when the
block I/O parameter value represents a
flow measurement made using differenti-
al pressure, and when square root
extraction is not performed by the
transducer.

4-9-1 Application Example 1


Temperature Transmitter
Situation Solution
A temperature transmitter with a range of The table below lists the appropriate
–200 to 450 °C. configuration settings, and the figure illustrates
the correct function block configuration.
Temperature
Measurement

Param eter Configured


Values OUT_D
L_TYPE Direct OUT To Another
AI Function Block
XD_SCALE Not Used Function Block

OUT_SCALE Not Used

4-9
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
4-9 Application Information

4-9-2 Application Example 2


Pressure Transmitter used to Measure Level in Open Tank

Situation #1
The level of an open tank is to be measured
using a pressure tap at the bottom of the tank. Full Tank
The level measurement will be used to control
the level of liquid in the tank.
The maximum level at the tank is 16 ft. The li- 16 ft 7.0 psi measured at
quid in the tank has a density that makes the the transmitter

level correspond to a pressure of 7.0 psi at the


pressure tap (see diagram below).

Fig. 4-5
Situation #1 Diagram

Solution to Situation #1
The table below lists the appropriate
configuration settings, and the figure illustrates
the correct function block configuration.

Analog
Measurement

AI OUT_D
Param eter Configured Function
OUT
Block
Values
L_TYPE Indirect BKCAL_IN BKCAL_OUT

XD_SCALE 0 to 7 psi PID AO


Function Function
OUT_SCALE 0 to 16 ft Block OUT CAS_IN Block
CAS_IN

Fig. 4-6
Function Block Diagram for a Pressure Transmitter
used in Level Measurement

4-10
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
4-9 Application Information

Situation #2
The transmitter in situation #2 is installed below 16 ft
the tank in a position where the liquid column
is in the impulse line, when the tank is empty,
is equivalent to 2.0 psi.
Empty Tank

Param eter Configured


Values
L_TYPE Indirect
XD_SCALE 2 to 9 psi 0 ft
2.0 psi measured at
OUT_SCALE 0 to 16 ft the transmitter

Fig. 4-7
Stuation #2 Diagram

4-9-3 Application Example 3


Differential Pressure Transmitter used to Measure Flow
Situation Solution
The liquid flow in a line is to be measured using The table below lists the appropriate
the differential pressure across an orifice plate configuration settings, and the figure illustrates
in the line, and the flow measurement will be the correct function block configuration.
used in a flow control loop. Based on the orifice
specification sheet, the differential pressure Param eter Configured
transmitter was calibrated for 0 to 20 in H2 0 Values
for a flow of 0 to 800 gal/min, and the transducer L_TYPE Indirect Square Root
was not configured to take the square root of XD_SCALE 0 to 20 in
the differential pressure. OUT_SCALE 0 to 800 gal/min

Analog BKCAL_IN BKCAL_OUT


Measurement

AI OUT_D PID AO
Function Function Function
Block OUT IN Block Block

Fig. 4-8
Function Block Diagram for Differential Pressure Transmitter in Flow Measurement

4-11
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003

4-10 Troubleshooting

4-10 Troubleshooting

Sym ptom Possible Causes Corrective Action

Mode w ill not 1. Target mode not set. 1. Set target mode to something other than OOS.
leave OOS
2. Configuration error 2. BLOCK_ERR will show the configuration error bit set. The following are parameters that must be set
before the block is allowed out of OOS:
a. CHANNEL must be set to a valid value and cannot be left at initial value of 0.
b. XD_SCALE.UNITS_INDX must match the units in the transducer block channel value.
c. L_TYPE must be set to Direct, Indirect, or Indirect Square Root and cannot be lef t at initial value of 0.
3. Resource block 3. The actual mode of the Resource block is OOS. See Resource Block Diagnostics for corrective action.
4. Schedule 4. Block is not scheduled and therefore cannot execute to go to Target Mode. Schedule the block to execute.
Process and/or 1. Features 1. FEATURES_SEL does not have Alerts enabled. Enable the Alerts bit.
2. Notification 2. LIM_NOTIFY is not high enough. Set equal to MAX_NOTIFY.
3. Status Options 3. STATUS_OPTS has Propagate Fault Forw ard bit set. This should be cleared to cause an alarm to occur.
Value of output 1. Linearization Type 1. L_TYPE must be set to Direct, Indirect, or Indirect Square Root and cannot be left at initial value of 0.
2. Scaling 2. Scaling parameters are set incorrectly:
a. XD_SCALE.EU0 and EU100 should match that of the transducer block channel value.
b. OUT_SCALE.EU0 and EU100 are not set properly.
Cannot set 1. Scaling 1. Limit values are outside the OUT_SCALE.EU0 and OUT_SCALE.EU100 values. Change OUT_SCALE or set
HI_LIMIT, values w ithin range.
HI_HI_LIMIT,
LO_LIMIT, or
. LO_LO_LIMIT
Values

Tab. 4-4
Troubleshooting AI Block

4-12
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus

SECTION 5
Analog Output (AO) Function Block

BKCAL_OUT
CAS_IN
AO OUT

CAS_IN = The remote point value from another function block.


BKCAL_OUT = The value and status required by the BKCAL_IN input of another block
to prevent reset windup and to provide bumpless transfer to closed loop control.
OUT = The block output and status.
Fig. 5-1
Analog output function block

The Analog Output (AO) function block assigns The block supports mode control, signal status
an output value to a field device through a calculation, and simulation. Figure 5-2
specified I/O channel. illustrates the internal components of the AO
function block, and Table 5-1 lists the definitions
of the system parameters.
Param eters Units Description
BKCAL_OUT EU of PV_SCALE The value and status required by the BKCAL_IN input of another block to
prevent reset w indup and to provide bumpless transfer to closed loop
control.
BLOCK_ERR None The summary of active error conditions associated w ith the block. The
block errors for the Analog Output block are Sim ulate Active, Input
Failure/Process Variable has Bad Status, Output Failure, Read
back Failed, and Out of Service.
CAS_IN EU of PV_SCALE The remote setpoint value from another function block.
IO_OPTS None Allow s you to select how the I/O signals are processed. The supported
I/O options for the AO function block are SP_PV Track in Man,
Increase to Close, and Use PV for BKCAL_OUT.
CHANNEL None Defines the output that drives the field device.
MODE None Enumerated attribute used to request and show the source of the
setpoint and/or output used by the block.
OUT EU of XD_SCALE The primary value and status calculated by the block in Auto mode. OUT
may be set manually in Man mode.
PV EU of PV_SCALE The process variable used in block execution. This value is converted
from READBACK to show the actuator position in the same units as the
setpoint value.
PV_SCALE None The high and low scale values, the engineering units code, and the
number of digits to the right of the decimal point associated with the PV.
READBACK EU of XD_SCALE The measured or implied actuator position associated w ith the OUT value.

SIMULATE EU of XD_SCALE Enables simulation and allow s you to enter an input value and status.
SP EU of PV_SCALE The target block output value (setpoint).
SP_HI_LIM EU of PV_SCALE The highest setpoint value allow ed.
SP_LO_LIM EU of PV_SCALE The low est setpoint value allow ed.
SP_RATE_DN EU of PV_SCALE Ramp rate for dow nw ard setpoint changes. When the ramp rate is set to
per second zero, the setpoint is used immediately.
SP_RATE_UP EU of PV_SCALE Ramp rate for upw ard setpoint changes. When the ramp rate is set to
per second zero, the setpoint is used immediately.
SP_WRK EU of PV_SCALE The w orking setpoint of the block. It is the result of setpoint rate-of-
change limiting. The value is converted to percent to obtain the block’s
OUT value.
Tab. 5-1
Analog Output Function Block System Parameters

5-1
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
5-1 Setting the Output

5-1 Setting the Output


To set the output for the AO block, you must This provides bumpless transfer on mode
first set the mode to define the manner in which changes and windup protection in the upstream
the block determines its setpoint. In Manual block. The OUT attribute or an analog
mode the value of the output attribute (OUT) readback value, such as valve position, is
must be set manually by the user, and is shown by the process value (PV) attribute in
independent of the setpoint. In Automatic mode, engineering units.
OUT is set automatically based on the value To support testing, you can enable simulation,
specified by the setpoint (SP) in engineering which allows you to manually set the channel
units and the I/O options attribute (IO_OPTS). feedback. There is no alarm detection in the
In addition, you can limit the SP value and the AO function block.
rate at which a change in the SP is passed to To select the manner of processing the SP and
OUT. the channel output value configure the setpoint
In Cascade mode, the cascade input limiting options, the tracking options, and the
connection (CAS_IN) is used to update the SP. conversion and status calculations.
The back calculation output (BKCAL_OUT) is
wired to the back calculation input (BKCAL_IN)
of the upstream block that provides CAS_IN.
RCAS_OUT
RCAS_IN BKCAL_OUT
SP_RATE_DN READ_BACK
SP_RATE_UP PV
Operator
Setpoint

SP SP Convert
HI/LO Rate and Status
Limit Limit Calculation OUT
CAS_IN

SP_WRK
SP_LO_LIM PV_SCALE
SP_HI_LIM
IO_OPTS
MODE

SIMULATE

Shed
Mode

Access Access
Analog Analog CHANNEL
Input Output

Fig. 5-2 Position Analog


Analog Output Function Block Schematic Feedback Output

5-2
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
5-2 Setpoint Selection and Limiting

OUT (Mode in CAS)

SP_RATE_DN
OUT (Mode in AUTO) SP_RATE_UP

OUT (Mode in MAN)

SP

Time
1 second 1 second

Fig. 5-3
Analog Output Function Block Timing Diagram

5-2 Setpoint Selection and Limiting


To select the source of the SP value use the manual mode, and is enabled (True) as a
MODE attribute. In Automatic (Auto) mode, the default. You can disable this option in Man or
local, manually-entered SP is used. In Cascade O/S mode only.
(Cas) mode, the SP comes from another block The SP value is limited to the range defined by
through the CAS_IN input connector. In the setpoint high limit attribute (SP_HI_LIM) and
RemoteCascade (RCas) mode, the SP comes the setpoint low limit attribute (SP_LO_LIM).
from a host computer that writes to RCAS_IN. In Auto mode, the rate at which a change in the
The range and units of the SP are defined by SP is passed to OUT is limited by the values
the PV_SCALE attribute. of the setpoint upward rate limit attribute
In Manual (Man) mode the SP automatically (SP_RATE_UP) and the setpoint downward
tracks the PV value when you select the SP- rate limit attribute (SP_RATE_DN). A limit of
PV Track in Man I/O option. The SP value is zero prevents rate limiting, even in Auto mode.
set equal to the PV value when the block is in

5-3 Conversion and Status Calculation


The working setpoint (SP_WRK) is the setpoint PV_SCALE and XD_SCALE.
value after limiting. You can choose to reverse In Auto mode, the converted SP value is stored
the conversion range, which will reverse the in the OUT attribute. In Man mode, the OUT
range of PV_SCALE to calculate the OUT attribute is set manually, and is used to set the
attribute, by selecting the Increase to Close I/ analog output defined by the CHANNEL
O option. This will invert the OUT value with parameter.
respect to the setpoint based on the You can access the actuator position

5-3
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
5-4 Simulation

associated with the output channel through the the OUT channel, you can choose to allow the
READBACK parameter (in OUT units) and in PV to be used for BKCAL_OUT by selecting
the PV attribute (in engineering units). If the the Use PV for BKCAL_OUT I/O option.
actuator does not support position feedback, NOTE: SP_PV Track in Man, Increase to
the PV and READBACK values are based on Close, and Use PV for BKCAL_OUT are the
the OUT attribute. only I/O options that the AO block supports. You
The working setpoint (SP_WRK) is the value can set I/O options in Manual or Out of Ser-
normally used for the BKCAL_OUT attribute. vice mode only.
However, for those cases where the
READBACK signal directly (linearly) reflects

5-4 Simulation
When simulation is enabled, the last value of
OUT is maintained and reflected in the field
value of the SIMULATE attribute. In this case,
the PV and READBACK values and statuses
are based on the SIMULATE value and the
status that you enter.

5-5 Action on Fault Detection


To define the state to which you wish the valve
to enter when the CAS_IN input detects a bad
status and the block is in CAS mode, configure
the following parameters:
• FSTATE_TIME: The length of time that the • FSTATE_VAL: The value to which the OUT
AO block will wait to position the OUT value value transitions after FSTATE_TIME
to the FSTATE_VAL value upon the elapses and the fault condition has not
detection of a fault condition. When the cleared. You can configure the channel to
block has a target mode of CAS, a fault hold the value at the start of the failure
condition will be detected if the CAS_IN action condition or to go to the failure action
has a BAD status or an Initiate Fault State value (FAIL_ACTION_VAL).
substatus is received from the upstream
block.

5-4
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
5-6 Block Errors

5-6 Block Errors


The following conditions are reported in the
BLOCK_ERR attribute:
• Input failure/process variable has Bad • Output failure – The output hardware is
status – The hardware is bad, the Device bad.
Signal Tag (DST) does not exist, or a BAD • Readback failed – The readback failed.
status is being simulated. • Simulate active – Simulation is enabled
• Out of service – The block is in Out of and the block is using a simulated value in
Service (O/S) mode. its execution.

5-7 Modes
The Analog Output function block supports the following modes:
• Manual (Man) – You can manually set the output to the I/O channel through the OUT attribute.
This mode is used primarily for maintenance and troubleshooting.
• Automatic (Auto) – The block output (OUT) reflects the target operating point specified by the
setpoint (SP) attribute.
• Cascade (Cas) – The SP attribute is set by another function block through a connection to
CAS_IN. The SP value is used to set the OUT attribute automatically.
• RemoteCascade (RCas) – The SP is set by a host computer by writing to the RCAS_IN
parameter. The SP value is used to set the OUT attribute automatically.
• Out of Service (O/S) – The block is not processed. The output channel is maintained at the last
value and the status of OUT is set to Bad: Out of Service. The BLOCK_ERR attribute shows
Out of Service.
• Initialization Manual (Iman) – The path to the output hardware is broken and the output will
remain at the last position.
• Local Override (LO) – The output of the block is not responding to OUT because the resource
block has been placed into LO mode or fault state action is active.
The target mode of the block may be restricted to one or more of the following modes: Man, Auto,
Cas, RCas, or O/S.

5-8 Status Handling


Output or readback fault detection are reflected can set the value and status for PV and
in the status of PV, OUT, and BKCAL_OUT. A READBACK.
limited SP condition is reflected in the When the block is in Cas mode and the
BKCAL_OUT status. When simulation is CAS_IN input goes bad, the block sheds mode
enabled through the SIMULATE attribute, you to the next permitted mode.

5-5
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003

5-6
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus

SECTION 6
Input Selector (ISEL) Function Block

IN (1-4) = Input used in the selection algorithm.


DISABLE (1-4) = Discrete input used to enable or disable the associated input channel.
OP_SELECT = Input used to override algorithm.
TRK_VAL = The value after scaling applied to OUT in Local Override mode.
SELECTED = The selected channel number.
OUT = The block output and status.
Fig. 6-1
Input Selector (ISEL) Function Block

The Input Selector (ISEL) function block can be Figure 5-2 illustrates the internal components
used to select the first good, Hot Backup, of the ISEL function block. Table 5-1 lists the
maximum, minimum, or average of as many ISEL block parameters and their descriptions,
as four input values and place it at the output. units of measure, and index numbers.
The block supports signal status propagation.
There is no process alarm detection in the In-
put Selector function block.

Param eter Index Units Description


Num ber
ALERT_KEY 4 None The identification number of the plant unit. This information may be used in
the host for sorting alarms, etc.
BLOCK_ALM 24 None The block alarm is used for all configuration, hardw are, connection failure,
or system problems in the block. The cause of the alert is entered in the
subcode field. The first alert to become active w ill set the Active status in
the Status parameter. As soon as the Unreported status is cleared by the
alert reporting task, another block alert may be reported w ithout clearing the
Active status, if the subcode has changed.
BLOCK_ERR 6 None This parameter reflects the error status associated w ith the hardw are or
softw are components associated w ith a block. It is a bit string, so that
multiple errors may be show n.
DISABLE_1 15 None A Connection from another block that disables the associated input from the
selection.
DISABLE_2 16 None A Connection from another block that disables the associated input from the
selection.

Tab. 6-1
Input Selector Function Block System Parameters

6-1
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
6 Input Selector (ISEL) Function Block

Param eter Index Units Description


Num ber
DISABLE_3 17 None A Connection from another block that disables the associated input from the
selection.
DISABLE_4 18 None A Connection from another block that disables the associated input from the
selection.
GRANT_DENY 9 None Options for controlling access of host computers and local control panels to
operating, tuning, and alarm parameters of the block. Not used by device.

IN_1 11 Determined by The connection input from another block. One of the inputs to be selected
source from.
IN_2 12 Determined by The connection input from another block. One of the inputs to be selected
source from.
IN_3 13 Determined by The connection input from another block. One of the inputs to be selected
source from.
IN_4 14 Determined by The connection input from another block. One of the inputs to be selected
source from.
MIN_GOOD 20 None The minimum number of good inputs
MODE_BLK 5 None The actual, target, permitted, and normal modes of the block.
Target: The mode to “go to”
Actual: The mode the “block is currently in”
Permitted: Allow ed modes that target may take on
Normal: Most common mode for target
OP_SELECT 22 None Overrides the algorithm to select 1 of the 4 inputs regardless of the
selection type.
OUT 7 EU of IN The block output value and status.
OUT_UNITS 8 None The engineering units of the output. Typically, all inputs have the same units
and the value is also the same.
SELECTED 21 None The selected input number (1–4).
SELECT_TYPE 19 None Specifies selection method (see Block Execution)
STATUS_OPTS 10 None Allow s selection of options for status handling and processing. The
supported status option for the PID block is Target to Manual if Bad IN.
STRATEGY 3 None The strategy field can be used to identify grouping of blocks. This data is
not checked or processed by the block.
ST_REV 1 None The revision level of the static data associated w ith the function block. The
revision value w ill be incremented each time a static parameter value in the
block is changed.
TAG_DESC 2 None The user description of the intended application of the block.
UPDATE_EVT 23 None This alert is generated by any change to the static data.

Tab. 6-1 (cont’d)


Input Selector Function Block System Parameters

6-2
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
6 Input Selector (ISEL) Function Block

IN_1
Selection AUTO
IN_2
OUT
IN_3
Algorithm
MAN
IN_4

DISABLE_1

DISABLE_2 SELECTED

DISABLE_3

DISABLE_4 SEL_TYPE

OP_SELECT MIN_GOOD

Fig. 6-2
Input Selector Function Block Schematic

6-1 Block Errors


Table 5-2 lists conditions reported in the Conditions in italics are inactive for the ISEL
BLOCK_ERR parameter. block and are listed for reference only.
Condition Condition Nam e and Description
Num ber
0 Other: The output has a quality of uncertain.
1 Block Configuration Error
2 Link Configuration Error
3 Simulate Active
4 Local Override: The actual mode is LO.
5 Device Fault State Set
6 Device Needs Maintenance Soon
7 Input Failure/Process Variable has Bad Status:
One of the inputs is Bad or not connected.
8 Output Failure: The output has the quality of Bad.
9 Mem ory Failure: A memory failure has occurred in
FLASH, RAM, or EEROM memory.
10 Lost Static Data
11 Lost NV Data
12 Readback Check Failed
13 Device Needs Maintenance Now
14 Pow er Up: The device w as just pow ered-up.
15 Out of Service: The actual mode is out of service.
Tab. 6-2
Block Error Conditions

6-3
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
6-2 Modes

6-2 Modes
The ISEL function block supports three modes • Out of Service (O/S) The block is not
of operation as defined by the MODE_BLK processed. The BLOCK_ERR parameter
parameter: shows Out of Service. In this mode,
• Manual (Man) The block output (OUT) changes caNn be made to all configurable
may be set manually. parameters. The target mode of a block
• Automatic (Auto) OUT reflects the may be restricted to one or more of the
selected value. supported modes.

6-3 Alarm Detection


A block alarm will be generated whenever the
BLOCK_ERR has an error bit set. The types
of block error for the ISEL block are defined
above.
Alarms are grouped into five levels of priority:

Priority Priority Description Num ber


0 The priority of an alarm condition changes to 0 after the condition that caused the alarm is corrected.
1 An alarm condition w ith a priority of 1 is recognized by the system, but is not reported to the operator.
2 An alarm condition w ith a priority of 2 is reported to the operator, but does not require operator attention
(such as diagnostics and system alerts).
03. Jul Alarm conditions of priority 3 to 7 are advisory alarms of increasing priority.
Aug 15 Alarm conditions of priority 8 to 15 are critical alarms of increasing priority.

Tab. 5-3
Alarm Priorities

6-4 Block Execution


The ISEL function block reads the values and • mid calculates the middle of three inputs
statuses of as many as four inputs. To specify or the average of the middle two inputs if
which of the six available methods (algorithms) four inputs are defined.
is used to select the output, configure the • 1st Good selects the first available good
selector type parameter (SEL_TYPE) as input.
follows: • Hot Backup latches on the selected input
• max selects the maximum value of the and continues to use it until it is bad.
inputs. If DISABLE_N is active, the associated input
• min selects the minimum value of the is not used in the selection algorithm.
inputs. If OP_SELECT is set to a value between 1 and
• avg calculates the average value of the 4, the selection type logic is overridden and
inputs. the output value and status is set to the value

6-4
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
6-5 Status Handling

and status of the input selected by


OP_SELECT.
SELECTED will have the number of the
selected input unless the SEL_TYPE is
average, in which case it will have the number
of inputs used to calculate its value.

6-5 Status Handling


In Auto mode, OUT reflects the value and status • Use Uncertain as Good: sets the OUT
quality of the selected input. If the number of status quality to Good when the selected
inputs with Good status is less than input status is Uncertain.
MIN_GOOD, the output status will be Bad. • Uncertain if in Manual mode: The status
In Man mode, the OUT status high and low of the Output is set to Uncertain when the
limits are set to indicate that the value is a mode is set to manual.
constant and the OUT status is always Good.
In the STATUS_OPTS parameter, the following The instrument must be in Ma-
options can be selected from to control the nual or Out of Service mode to
status handling: set the status option.

6-6 Application Information


The ISEL function block can be used to select process water chiller (see fig. 5-3) or it can use
the maximum temperature input from four inputs the block to calculate the average temperature
and send it to a PID function block to control a of the four inputs (see fig. 5-4).

IN1 = 126 °F
Input Selector
IN2 = 104 °F (ISEL) Function
Block To Another
Function Block
IN3 = 112 °F OUT = 130 °F

IN4 = 130 °F
SEL_TYPE = max

Fig. 6-3
Input Selector Function Block Application Example (SEL_TYPE = max).

6-5
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
6-6 Application Information

IN1 = 126 °F
Input Selector
IN2 = 104 °F (ISEL) Function
Block To Another
Function Block
IN3 = 112 °F OUT = 118 °F

IN4 = 130 °F
SEL_TYPE = avg

Fig. 6-4
Input Selector Function Block Application Example (SEL_TYPE = avg.).

IN1 = 126 °F
Input Selector
IN2 = 104 °F (ISEL) Function
Block

IN3 = 112 °F

IN4 = 130 °F
SEL_TYPE = Hot Backup

Fig. 6-5
Input Selector Function Block Application Example (SEL_TYPE = Hot Back-
up).

IN1 IN2 Out Selected


Tim e Value Status Value Status Value Status Value Status
T0 Good 20 Good 21 Good 20 Good 1
T1 Bad 20 Good 21 Good 21 Good 2
T2 Good 20 Good 21 Good 21 Good 2

Tab. 6-4
Input Selector Function Blocks

6-6
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
6-7 Troubleshooting

6-7 Troubleshooting

Sym ptom Possible Causes Corrective Action


Mode w ill not 1. Target mode not set. 1. Set target mode to something other than OOS.
leave OOS
2. Configuration error 2. BLOCK_ERR will show the configuration error bit set. SELECT_TYPE
must be set to a valid value and cannot be left at 0.
3. Resource block 3. The actual mode of the Resource block is OOS. See Resource Block Diagnostics
for corrective action.
4. Schedule 4. Block is not scheduled and therefore cannot execute to go to Target Mode.
Schedule the block to execute.
Status of 1. Inputs 1. All inputs have Bad status.
output is bad. 2. OP selected 2. OP_SELECT is not set to 0 (or it is linked to an input that is not 0), and it points to
an input that is Bad.
3. Min good 3. The number of Good inputs is less than MIN_GOOD.
Block alarms 1. Features 1. FEATURES_SEL does not have Alerts enabled. Enable Alerts bit..
w ill not w ork 2. Notification 2. LIM_NOTIFY is not high enough. Set equal to MAX_NOTIFY.
1. Status Options 1. STATUS_OPTS has Propagate Fault Forw ard bit set. This should be cleared to
cause an alarm to occur.

Tab. 6-5
Troubleshooting ISEL Block

6-7
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003

6-8
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus

SECTION 7
Arithmetic (ARTHM) Function Block

IN OUT
IN_LO
IN_1 ARTHM
IN_2
IN_3

The Arithmetic function block provides the ability The nine (9) arithmetic functions are Flow
to configure a range extension function for a Compensation Linear, Flow Compensation
primary input and applies the nine (9) different Square Root, Flow Compensation
arithmetic types as compensation to or Approximate, BTU Flow, Traditional Multiply
augmentation of the range extended input. All and Divide, Average, Summer, Fourth Order
operations are selected by parameter and Polynomial, and Simple HTG Compensate
input connection. Level.
This Arithmetic function block supports mode
control (Auto, Manual, Out of Service). There
is no standard alarm detection in this block.

7-1
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
7 Arithmetic (ARTHM) Function Block

Index
Parameter Units Description
Number
4 ALERT_KEY None The identification number of the plant unit. This information may be used in the
host fro sorting alarms, etc.
29 ARITH_TYPE None The set of 9 arithmetic functions applied as compensation to or augmentation
of the range extended input.
30 BAL_TIME Seconds Specifies the time for a block value to match an input, output, or calculated
value or the time for dissipation of the internal balancing bias.
31 BIAS None The bias value
21 BIAS_IN_1 None The bias value for IN_1.
23 BIAS_IN_2 None The bias value for IN_2.
25 BIAS_IN_3 None The bias value for IN_3.
36 BLOCK_ALM None This block alarm is used for all configuration, hardware, connection failure, or
system problems in the block. The cause of the alert is entered in the subcode
field.The first alert to become active will set the active status in the status
parameter. As soon as the Unreported status is cleared by the alert reporting
task, and other block alert may be reported without clearing the Active status,
if the subcode has changed.
6 BLOCK_ERR None The summary of active error conditions associated with the block. The
possible block errors are Block configuration error, Simulate active, Local
override, Input failure/process variable has Bad status, Output failure,
Readback failed, Out of service, and Other. Each function block reports none
or a subset of these error conditions.
27 COMP_HI_LIM EU of PV Determines the high limit of the compensation input.
28 COMP_LO_LIM EU of PV Determines the low limit of the compensation input.
32 GAIN None The proportional gain (multiplier) value.
22 GAIN_IN_1 None The proportional gain (multiplier) value for IN_1
24 GAIN_IN_2 None The proportional gain (multiplier) value for IN_2
26 GAIN_IN_3 None The proportional gain (multiplier) value for IN_3
12 GRANT_DENY None Options for controlling access of host computers and local control panels to
operating, tuning, and alarm parameters of the block. Not used by the device.
14 IN Determined by source or The analog input value and status. The number of inputs is an extensible
EU of PV_SCALE parameter in some function blocks.
16 IN_1 Determined by supplying The first analog input value and status.
block or source.
17 IN_2 Determined by supplying The second analog input value and status.
block or source.
18 IN_3 Determined by supplying The third analog input value and status.
block or source.
15 IN_LO None The value used for the input whenever IN is below range.
13 INPUT_OPTS None Sets the options for using IN, IN_LO, IN_1, IN_2 and IN_3 when any are either
Bad or Uncertain.
5 MODE_BLK None The mode record of the block. MODE contains the actual, target, permitted,
and normal modes. In some function blocks, this parameter is used to request
and show the source of the setpoint, the source of the output, and/or the block
operating state.
8 OUT EU of OUT_SCALE or The analog output value and status. The number of outputs is an extensible
Percent or EU of IN parameter in some blocks.
33 OUT_HI_LIM EU of OUT_SCALE or The maximum output value allowed.
Supplied by IN
Tab. 7-1
Arithmetic Block Parameters

7-2
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
7 Arithmetic (ARTHM) Function Block

Index
Parameter Units Description
Number
34 OUT_LO_LIM EU of OUT_RANGE or The minimum output value allowed.
Supplied by IN
11 OUT_RANGE None Range of the output
9 PRE_OUT EU of OUT The pre-trip limit from SP or zero.
7 PV EU of OUT or EU of The process variable used in block execution and alarm limit detection.
PV_SCALE
10 PV_SCALE None The high and low scale values, engineering units code, and number of digits to
the right of the decimal point associated with OUT.
19 RANGE_HI None The high limit for IN.
20 RANGE_LO None The low limit for IN. If IN is less than RANGE_LO, then IN_LO is used.
3 STRATEGY None The strategy field can be used to identify grouping of blocks. This data is not
checked or processed by the block.
1 ST_REV None The revision level of the static data associated with the function block. The
revision value will be incremented each time a static parameter value in the
block is changed.
2 TAG_DESC None The user description of the intended application of the block.
35 UPDATE_EVT None This alert is generated by any changes to the static data.

Tab. 7-1 (cont’d)


Arithmetic Block Parameters

Fig. 7-2
Arithmetic Function Block Schematic

7-3
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
7-1 Block Errors

7-1 Block Errors


Table 6-2 lists conditions reported in the
BLOCK_ERR parameter.
Conditions in italics are inactive for the ARTHM
block and are listed here only for your reference.
Condition
Condition Name and Description
Number
0 Other: The output has a quality of uncertain.
1 Block Configuration Error: Select type is not configured
2 Link Configuration Error
3 Simulate Active
4 Local Override
5 Device Fault State Set
6 Device Needs Maintenance Soon
7 Input Failure/Process Variable has Bad Status: One of the inputs is Bad
or not connected.
8 Output Failure
9 Memory Failure
10 Lost Static Data
11 Lost NV Data
12 Readback Check Failed
13 Device Needs Maintenance Now
14 Power Up: The device was just powered-up.
15 Out of Service: The actual mode is out of service.

Tab. 7-2
BLOCK_ERR parameters

7-2 Modes
The ARTHM block supports the following
modes:
• Manual (Man) – The block output (OUT) • Out of Service (O/S) – The block is not
may be set manually. processed. FIELD_VAL and PV are not
• Automatic (Auto) – OUT reflects the ana- updated and the OUT status is set to Bad:
log input measurement or the simulated Out of Service. The BLOCK_ERR
value when simulation is enabled. parameter shows Out of Service. In this
mode, you can make changes to all
configurable parameters.
The target mode of a block bay be restricted
to one or more of the supported modes.

7-4
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
7-3 Alarm Detection

7-3 Alarm Detection


A block alarm will be generated whenever the
BLOCK_ERR has anerror bit set. The types of
block error for the ARTHM block aredefined
above.
Alarms are grouped into five levels of priority:
Priority
Priority Description
Number
0 The priority of an alarm condition changes to 0 after the condition that
caused the alarm is corrected.
1 An alarm condition with a priority of 1 is recognized by the system, but is
not reported to the operator.
2 An alarm condition with a priority of 2 is reported to the operator, but does
not require operator attention (such as diagnostics and system alerts).
3-7 Alarm conditions of priority 3 to 7 are advisory alarms of increasing priority.
8-15 Alarm conditions of priority 8 to 15 are critical alarms of increasing priority.

Tab. 7-3
Alarm Level Priorities

7-4 Block Execution


The Arithmetic function block provides range three inputs (IN_1, IN_2, and IN_3) through the
extension and compensation through nine (9) user selected compensation function
arithmetic types. (ARITH_TYPE) to calculate the value of func. A
There are two inputs (IN and IN_LO) used in gain is applied to func and then a bias is added
calculating PV. PV is then combined with up to to get the value PRE_OUT. In AUTO,
PRE_OUT is used for OUT.

Range Extension and Calculation of PV


When both IN and IN_LO are usable, the PV = G * IN + (1 - G) * IN_LO
following formula is applied to calculate range (G has a range from 0 to 1, for IN from
extension for PV: RANGE_LO to RANGE_HI.)

Compensation Input Calculations


For each of the inputs IN_1, IN_3, IN_4 there • When IN_(k) is usable:
is a gain and bias. The compensation terms t(k) = GAIN_IN(k) * (BIAS_IN(k) + IN_(k))
(t) are calculated as follows:
• When IN_(k) is not usable, then t(k) gets
the value of the last t(k) computed with a
usable input.

7-5
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
7-5 Status Handling

7-5 Status Handling


IN_x Use Bad
IN_x Use Uncertain
IN_LO Use Uncertain
IN Use Uncertain
For complete descriptions of supported input
options, refer to the Option Bitstring Parame-
ters topic.

7-6 Application Information


The Arithmetic function block can be used to The Arithmetic function block allows for the
calculate tank level changes based on greatly automatic compensation of this change by
changing temperature conditions in devices incorporating gain and bias adjustments to the
that depend on the physical properties of the temperature signal. It then applies both the
fluid. compensated temperature signal and the level
For example, a differential pressure cell’s ana- signal to a characteristic system equation. The
log input can be scaled initially to provide a 4- result is a level that is a true indication of fluid
20 mA signal for 0-100% of level indication. As in the vessel.
the temperature of the system rises, the density Different fluids over the same temperature
of the fluid decreases. For a system that range have different effects on level due to their
requires accurate level indication at widely thermal expansion coefficients. Vessel
ranging temperature, changing density proves geometry also plays a major role. As the height
inconvenient. of the vessel increases, the effect of thermal
expansion becomes more apparent. The
following figure shows the relative temperature
effects on a level signal.

Fig. 7-3
Relative Temperature Effects on Level

7-6
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
7-6 Application Information

The calculation is done by applying the level This allows a ratio to be set up that increases
signal to the IN connector, the liquid the level indication at block output for an
temperature to the IN_1 connector, and the increase in the tank temperature relative to
ambient air temperature to the IN_2 connector. ambient temperature.
Select the Arithmetic type (ARITH_TYPE) of
Flow Compensation - Linear.

Fig. 7-4
Arithmetic Function Block Diagram Example

This application can be applied to very large


storage tanks whose contents are subject to
thermal expansion and contraction during
seasonal changes in temperature.

7-7
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003
7-7 Advanced Topics

7-7 Advanced Topics

Arithmetic Types
The parameter ARITH_TYPE determines how
PV and the compensation terms (t) are
combined. User may select from nine (9)
commonly used math functions, depicted below.
COMP_HI and COMP_LO are compensation
limits.

If there is a divide by zero and the numerator is The square root of a negative value will equal
positive, f is set to COMP_HI; if the numerator the negative of the square root of the absolute
is negative, then f is set to COMP_LO. value. Imaginary roots are not supported.

If there is a divide by zero and numerator is COMP_LO. Compensation inputs which are
positive, f will be limited to COMP_HI; if the not usable are not included in the calculation.
numerator is negative, f will be limited to PV is always included.

7-8
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FOUNDATIONTM Fieldbus
7-8 Troubleshooting

7-8 TROUBLESHOOTING
Refer to Table 6-4 to troubleshoot any problems
that you encounter.
Symptom Possible Causes Corrective Action
Model will not leave OOS Target model not set Set target mode to something other than OOS
Configuration error BLOCK_ERR will show the configuration error set. ARITH_TYPE must be set to a
valid value and cannot be left at 0.
Resource Block The actual mode of the Resource block is OOS. See Resource block diagnostics
for corrective action.
Schedule Block is not scheduled and therefore cannot execute to go to the target mode.
Typically, BLOCK_ERR will show “Power-Up” for all blocks that are not scheduled.
Schedule the block to execute.
Status of outputs is BAD Inputs Input has BAD status.
Block alarms will not work Features FEATURES_SEL does not have Alerts enabled. Enable the Alert bit.
Notification LIM_NOTIFY is not high enough. Set equal to MAX_NOTIFY.
Status Options STATUS_OPTS has the Propagate Fault Forward bit set. This must be cleared to
cause the alarm to occur.

Tab. 7-4
Troubleshooting

7-9
FOUNDATIONTM Fieldbus Communication Instruction Manual
ETC01184
FOUNDATIONTM Fieldbus 10/2003

7-10
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FoundationTM Fieldbus

SECTION 8
Proportional / Integral / Derivative (PID) Function Block

BKCAL_IN = The analog input value and status from another block’s TRK_VAL = The value after scaling applied to OUT in Local
BKCAL_OUT output that is used forbackward output Override mode.
tracking for bumpless transfer and to pass limit status. BKCAL_OUT= The value and status required by the BKCAL_IN
CAS_IN = The remote setpoint value from another function block. input of another function block to prevent reset
FF_VAL = The feedforward control input value and status. windup and to provide bumpless transfer to closed
IN = The connection for the process variable from another loop control.
function block. OUT = The block output and status.
TRK_IN_D = Initiates the external tracking function.

The PID function block combines all of the The block supports two forms of the PID
necessary logic to perform proportional / inte- equation: Standard and Series. Choose the
gral / derivative (PID) control. The block appropriate equation using the FORM
supports mode control, signal scaling and parameter. The Standard ISA PID equation is
limiting, feedforward control, override tracking, the default selection.
alarm limit detection, and signal status
propagation.

 1 τds 
Standard Out = GAIN x e x 1 + +  + F
 τ r s +1 α x τ d s +1 

 1   τ d s +1 
Series Out = GAIN x e x 1 +  +   + F
 τ r s   α x τ d s + 1 

Where
GAIN: Proportional gain value.
tr: Integral action time constant (RESET parameter) in seconds.
s: Laplace operator
td: Derivative action time constant (RATE parameter).
a: Fixed smoothing factor of 0.1 applied to RATE.
F: Feedforward control contribution from the feedforward input (FF_VAL parameter).
e: Error between setpoint and process variable.

8-1
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
FoundationTM Fieldbus 10/2003
8 PID Function Block

To further customize the block for use in an Table 8-1 lists the PID block parameters and
application, it is possible to configure filtering, their descriptions, units of measure, and index
feedforward inputs, tracking inputs, setpoint numbers, and fig. 8-1 illustrates the internal
and output limiting, PID equation structures, and components of the PID function block.
block output action.
Index Description
Param eter Units
Num ber
ACK_OPTION 46 None Used to set auto acknow ledgment of alarms.
ALARM_HYS 47 Percent The amount the alarm value must return to w ithin the alarm limit before the associated active alarm condition
clears.
The summary alarm is used for all process alarms in the block. The cause of the alert is entered in the subcode
field. The first alert to become active w ill set the Active status in the Status parameter. As soon as the
ALARM_SUM 45 None
Unreported status is cleared by the alert reporting task, another block alert may be reported w ithout clearing the
Active status, if the subcode has changed.
ALERT_KEY 4 None The identification number of the plant unit. This information may be used in the host for sorting alarms, etc.
ALG_TYPE 74 None Selects filtering algorithm as Backw ard or Bilinear.
BAL_TIME 25 Seconds The specified time for the internal w orking value of bias to return to the operator set bias. Also used to specify
the time constant at w hich the integral term w ill move to obtain balance w hen the output is limited and the mode
is AUTO, CAS, or RCAS.
BIAS 66 EU of OUT_SCALE The bias value used to calculate output for a PD type controller.
BKCAL_HYS 30 Percent The amount the output value must change aw ay from the its output limit before limit status is turned off.
BKCAL_IN 27 EU of OUT_SCALE The analog input value and status from another block’s BKCAL_OUT output that is used for backw ard output
tracking for bumpless transfer and to pass limit status.
BKCAL_OUT 31 EU of PV_SCALE The value and status required by the BKCAL_IN input of another block to prevent reset w indup and to provide
bumpless transfer of closed loop control.
The block alarm is used for all configuration, hardw are, connection failure, or system problems in the block. The
cause of the alert is entered in the subcode field. The first alert to become active w ill set the active status in the
BLOCK_ALM 44 None
status parameter. As soon as the Unreported status is cleared by the alert reporting task, and other block alert
may be reported w ithout clearing the Active status, if the subcode has changed.
This parameter reflects the error status associated w ith the hardw are or softw are components associated w ith
BLOCK_ERR 6 None
a block. It is a bit string so that multiple errors may be show n.
BYPASS 17 None Used to override the calculation of the block. When enabled, the SP is sent directly to the output.
CAS_IN 18 EU of PV_SCALE The remote setpoint value from another block.
CONTROL_OPTS 13 None Allow s definition of control strategy options. The supported control options for the PID block are Track enable,
Track in Manual, SP-PV Track in Man, SP-PV Track in LO or IMAN, Use PV for BKCAL OUT, and Direct Acting
DV_HI_ALM 64 None The DV HI alarm data, w hich includes a value of the alarm, a timestamp of occurrence, and the state of the
alarm.
DV_HI_LIM 57 EU of PV_SCALE The setting for the alarm limit used to detect the deviation high alarm condition.
DV_HI_PRI 56 None The priority of the deviation high alarm.
DV_LO_ALM 65 None The DV LO alarm data, w hich includes a value of the alarm, a timestamp of occurrence, and the state of the
alarm.
DV_LO_LIM 59 EU of PV_SCALE The setting for the alarm limit use to detect the deviation low alarm condition.
DV_LO_PRI 58 None The priority of the deviation low alarm.
ERROR 67 EU of PV_SCALE The error (SP-PV) used to determine the control action.
FF_ENABLE 70 None Enables the use of feedforw ard calculations
FF_GAIN 42 None The feedforw ard gain value. FF_VAL is multiplied by FF_GAIN before it is added to the calculated control output.

FF_SCALE 41 None The high and low scale values, engineering units code, and number of digits to the right of the decimal point
associated w ith the feedforw ard value (FF_VAL).
FF_VAL 40 EU of FF_SCALE The feedforw ard control input value and status.
GAIN 23 None The proportional gain value. This value cannot = 0.
GRANT_DENY 12 None Options for controlling access of host computers and local control panels to operating, tuning, and alarm
parameters of the block. Not used by the device.
HI_ALM 61 None The HI alarm data, w hich includes a value of the alarm, a timestamp of occurrence, and the state of the alarm.
HI_HI_ALM 60 None The HI HI alarm data, w hich includes a value of the alarm, a timestamp of occurrence, and the state of the alarm.

HI_HI-LIM 49 EU of PV_SCALE The setting for the alarm limit used to detect the HI HI alarm condition.
HI_HI_PRI 48 None The priority of the HI HI Alarm.
HI_LIM 51 EU of PV_SCALE The setting for the alarm limit used to detect the HI alarm condition.
HI_PRI 50 None The priority of the HI alarm.
IN 15 EU of PV_SCALE The connection for the PV input from another block.
LO_ALM 62 None The LO alarm data, w hich includes a value of the alarm, a timestamp of occurrence, and the state of the alarm.

Tab. 8-1
PID Function Block System Parameters

8-2
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FoundationTM Fieldbus
8 PID Function Block

Index Description
Param eter Units
Num ber
LO_LIM 53 EU of PV_SCALE The setting for the alarm limit used to detect the LO alarm condition.
LO_LO_ALM 63 None The LO LO alarm data, w hich includes a value of the alarm, a timestamp of occurrence, and the state of the
alarm.
LO_LO_LIM 55 EU of PV_SCALE The setting for the alarm limit used to detect the LO LO alarm condition.
LO_LO_PRI 54 None The priority of the LO LO alarm.
LO_PRI 52 None The priority of the LO alarm.
MATH_FORM 73 None Selects equation f orm (series or standard).
The actual, target, permitted, and normal modes of the block.
Target: The mode to “go to”
MODE_BLK 5 None
Actual: The mode the “block is currently in” Permitted: Allow ed modes that target may take on Normal: Most
common mode for target.
OUT 9 EU of OUT SCALE The block input value and status.
OUT_HI_LIM 28 EU of OUT_SCALE The maximum output value allow ed.
OUT-LO_LIM 29 EU of OUT_SCALE The minimum output value allow ed
OUT_SCALE 11 None The high and low scale values, engineering units code, and number of digits to the right of the decimal point
associated w ith OUT.
PV 7 EU of PV_SCALE The process variable used in block execution.
PV_FTIME 16 Seconds The time constant of the first-order PV filter. It is the time required f or a 63 percent change in the IN value.
PV_SCALE 10 None The high and low scale values, engineering units code, and number of digits to the right of the decimal point
associated w ith PV.
RATE 26 Seconds The derivative action time constant.
RCAS_IN 32 EU of PV_SCALE Target setpoint and status that is provided by a supervisory host. Used w hen mode is RCAS.
RCAS_OUT 35 EU of PV_SCALE Block setpoint and status after ramping, f iltering, and limiting that is provided to a supervisory host for back
calculation to allow action to be taken under limiting conditions or mode change. Used w hen mode is RCAS.
RESET 24 Seconds per repeat The integral action time constant.

ROUT_IN 33 EU of OUT_SCALE Target output and status that is provided by a supervisory host. Used w hen mode is ROUT.
ROUT_OUT 36 EU of OUT_SCALE Block output that is provided to a supervisory host for a back calculation to allow action to be taken under limiting
conditions or mode change.
Used w hen mode is RCAS.
SHED_OPT 34 None Def ines action to be taken on remote control device timeout.
SP 8 EU of PV_SCALE The target block setpoint value. It is the result of setpoint limiting and setpoint rate of change limiting.
SP_FTIME 69 Seconds The time constant of the first-order SP filter. It is the time required f or a 63 percent change in the IN value.
SP_HI_LIM 21 EU of PV_SCALE The highest SP value allow ed.
SP_LO_LIM 22 EU of PV_SCALE The low est SP value allow ed.
SP_RATE_DN 19 EU of PV_SCALE Ramp rate for dow nw ard SP changes. When the ramp rate is set to zero, the SP is used immediately.
per second
SP-RATE_UP 20 EU of PV_SCALE Ramp rate for upw ard SP changes. When the ramp rate is set to zero, the SP is used immediately.
per second
SP_WORK 68 EU of PV_SCALE The w orking setpoint of the block af ter limiting and filtering is applied.
STATUS_OPTS 14 None Allow s selection of options for status handling and processing. The supported status option for the PID block is
Target to Manual if Bad IN.
STRATEGY 3 None The strategy field can be used to identify grouping of blocks. This data is not checked or processed by the
block.
ST_REV 1 None The revision level of the static data associated w ith the f unction block. The revision value w ill be incremented
each time a static parameter value in the block is changed.
STRUCTURE. CONFIG 75 None Def ines PID equation structure to apply controller action.
TAG_DESC 2 None The user description of the intended application of the block.
TRK_IN_D 38 None Discrete input that initiates external tracking.
TRK_SCALE 37 None The high and low scale values, engineering units code, and number of digits to the right of the decimal point
associated w ith the external tracking value (TRK_VAL).
TRK_VAL 39 EU of The value (af ter scaling from TRK_SCALE to OUT_SCALE) applied to OUT in LO mode.
TRK SCALE
UBETA 72 Percent Used to set disturbance rejection vs. tracking response action f or a 2.0 degree of freedom PID.
UGAMMA 71 Percent Used to set disturbance rejection vs. tracking response action f or a 2.0 degree of freedom PID.
UPDATE_EVT 43 None This alert is generated by any changes to the static data.

Tab. 8-1 (cont’d)


PID Function Block System Parameters

8-3
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
FoundationTM Fieldbus 10/2003
8-1 Setpoint Selection And Limiting

FF_GAIN
FF_SCALE

FF_VAL Feedforward
Calculation
BKCAL_IN
MODE

TRK_IN_D BKCAL_OUT
RCAS_OUT
ROUT_OUT

ROUT_IN
RCAS_IN
Setpoint
Limiting
And PID
CAS_IN Filtering Equation Output OUT
Limiting
Operator
Setpoint SP_HI_LIM GAIN
SP_LO_LIM RATE OUT_HI_LIM
SP_RATE_DN RESET OUT_LO_LIM
SP_RATE_UP OUT_SCALE
SP_FTIME Alarm
Detection Operator
Output
Scaling
IN and
Filtering HI_HI_LIM
HI_LIM
DV_HI_LIM
DV_LO_LIM
PV_SCALE
LO_LIM
PV_FTIME
LO_LO_LIM
TRK_VAL Convert

TRK_SCALE
OUT_SCALE

Fig. 8-1
PID Function Block Schematic

8-1 Setpoint Selection and Limiting


The setpoint of the PID block is determined by the setpoint rate of change using the
the mode. The SP_HI_LIM and SP_LO_LIM SP_RATE_UP and SP_RATE_DN
parameters can be configured to limit the parameters.
setpoint. In Cascade or RemoteCascade In Manual mode the output is entered manually
mode, the setpoint is adjusted by another by the operator, and is independent of the
function block or by a host computer, and the setpoint. In RemoteOutput mode, the output
output is computed based on the setpoint. is entered by a host computer, and is
In Automatic mode, the setpoint is entered independent of the setpoint.
manually by the operator, and the output is Figure 8-2 illustrates the method for setpoint
computed based on the setpoint. In Auto mode, selection.
it is also possible adjust the setpoint limit and

8-4
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FoundationTM Fieldbus
8-2 Filtering

Operator
Setpoint
SP_HI_LIM SP_RATE_UP
SP_LO_LIM SP_RATE_DN

Auto Auto
Man Setpoint Rate Man
Limiting Limiting
Cas Cas

Fig. 8-2
PID Function Block Setpoint Selection

8-2 Filtering
The filtering feature changes the response time The filtering feature can be configured with the
of the device to smooth variations in output FILTER_TYPE parameter, and the filter time
readings caused by rapid changes in input. constant (in seconds) can be adjusted using
the PV_FTIME or SP_FTIME parameters. Set
the filter time constant to zero to disable the
filter feature.

8-3 Feedforward Calculation


The feedforward value (FF_VAL) is scaled
(FF_SCALE) to a common range for
compatibility with the output scale
(OUT_SCALE). A gain value (FF_GAIN) is
applied to achieve the total feedforward
contribution.

8-4 Tracking
Output tracking is enabled through the control causes the block’s actual mode to revert to
options. Control options can be set in Manual Local Override.
or Out of Service mode only. The TRK_VAL parameter specifies the value
The Track Enable control option must be set to be converted and tracked into the output
to True for the track function to operate. When when the track function is operating. The
the Track in Manual control option is set to True, TRK_SCALE parameter specifies the range
tracking can be activated and maintained only of TRK_VAL.
when the block is in Manual mode. When When the TRK_IN_D parameter is True and
Track in Manual is False, the operator can the Track Enable control option is True, the
override the tracking function when the block TRK_VAL input is converted to the appropriate
is in Manual mode. Activating the track function value and output in units of OUT_SCALE.

8-5
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
FoundationTM Fieldbus 10/2003
8-5 Output Selection And Limiting

8-5 Output Selection and Limiting


Output selection is determined by the mode In Manual and RemoteOutput mode, the
and the setpoint. In Automatic, Cascade, or output may be entered manually (see also Set-
RemoteCascade mode, the output is point Selection and Limiting). The output can
computed by the PID control equation. be limited by configuring the OUT_HI_LIM and
OUT_LO_LIM parameters.

8-6 Bumpless Transfer and Setpoint Tracking


The method for can be configured tracking the The value that a master controller uses can be
setpoint by configuring the following control selected for tracking by configuring the Use PV
options (CONTROL_OPTS): for BKCAL_OUT control option. The
SP-PV Track in Man — Permits the SP to BKCAL_OUT value tracks the PV value.
track the PV when the target mode of the BKCAL_IN on a master controller connected
block is Man. to BKCAL_OUT on the PID block in an open
SP-PV Track in LO or IMan — Permits the cascade strategy forces its OUT to match
SP to track the PV when the actual mode BKCAL_IN, thus tracking the PV from the slave
of the block is Local Override (LO) or PID block into its cascade input connection
Initialization Manual (IMan). (CAS_IN). If the Use PV for BKCAL_OUT
When one of these options is set, the SP value option is not selected, the working setpoint
is set to the PV value while in the specified (SP_WRK) is used for BKCAL_OUT.
mode. Control options can be set in Manual or Out
of Service mode only. When the mode is set
to Auto, the SP will remain at the last value (it
will no longer follow the PV.

8-7 PID Equation Structures


Configure the STRUCTURE parameter to an integrator equation with a gain value applied
select the PID equation structure. Select one to the error:
of the following choices: GAIN x e(s)
• PI Action on Error, D Action on PV s
• PID Action on Error
• Action on Error, PD Action on PV Where
Set RESET to zero to configure the PID block
GAIN: Proportional gain value.
to perform integral only control regardless of
e: Error.
the STRUCTURE parameter selection. When
RESET equals zero, the equation reduces to s: Laplace operator.

8-6
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FoundationTM Fieldbus
8-8 Reverse and Direct Action

8-8 Reverse and Direct Action


To configure the block output action, enable the Track Enable, Track in Manual,
Direct Acting control option. This option SP-PV Track in Man, SP-PV
defines the relationship between a change in Track in LO or IMan, Use PV for
PV and the corresponding change in output. BKCAL_OUT, and Direct Acting
With Direct Acting enabled (True), an increase are the only control options
in PV results in an increase in the output. supported by the PID function
Control options can be set in Manual or Out block. Unsupported options are
of Service mode only. not grayed out; they appear on
the screen in the same manner
as supported options.

8-9 Reset Limiting


The PID function block provides a modified windup when output or input limits are
version of feedback reset limiting that prevents encountered, and provides the proper behavior
in selector applications.

8-10 Block Errors


Table 8-2 lists conditions reported in the are inactive for the PID block and are given
BLOCK_ERR parameter. Conditions in italics here for reference only.
Condition
Condition Nam e and Description
Num ber
0 Other :
1 Block Configuration Error: The BY_PASS parameter is not configured and is set to 0, the SP_HI_LIM is
less than the SP_LO_LIM, or the OUT_HI_LIM is less than the OUT_LO_LIM.
2 Link Configuration Error
3 Simulate Active
4 Local Override: The actual mode is LO.
5 Device Fault State Set
6 Device Needs Maintenance Soon
7 Input Failure/Process Variable has Bad Status: The parameter linked to IN is indicating a Bad status.
8 Output Failure
9 Memory Failure
10 Lost Static Data
11 Lost NV Data
12 Readback Check Failed
13 Device Needs Maintenance Now
14 Power Up
15 Out of Service: The actual mode is out of service.

Tab. 8-2
Block Error Conditions

8-7
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
FoundationTM Fieldbus 10/2003
8-11 Modes

8-11 Modes
The PID function block supports the following Local Override (LO)—The track function is
modes: active. OUT is set by TRK_VAL. The
Manual (Man)—The block output (OUT) may BLOCK_ERR parameter shows Local
be set manually. override.
Automatic (Auto)—The SP may be set Initialization Manual (IMan)—The output path
manually and the block algorithm is not complete (for example, the cascade-
calculates OUT. to-slave path might not be open). In IMan
Cascade (Cas)—The SP is calculated in mode, OUT tracks BKCAL_IN.
another block and is provided to the PID Out of Service (O/S)—The block is not
block through the CAS_IN connection. processed. The OUT status is set to Bad:
RemoteCascade (RCas)—The SP is Out of Service. The BLOCK_ERR
provided by a host computer that writes to parameter shows Out of service.
the RCAS_IN parameter. The Man, Auto, Cas, and O/S modes can be
RemoteOutput (Rout)—The OUT is provided configured as permitted modes for operator
by a host computer that writes to the entry.
ROUT_IN parameter

8-12 Alarm Detection


A block alarm will be generated whenever the In order to avoid alarm chattering when the va-
BLOCK_ERR has an error bit set. The types riable is oscillating around the alarm limit, an
of block error for the AI block are defined above. alarm hysteresis in percent of the PV span can
Process alarm detection is based on the PV be set using the ALARM_HYS parameter. The
value. The alarm limits of the following standard priority of each alarm is set in the following
alarms can be configured: parameters:
• High (HI_LIM) • HI_PRI
• High high (HI_HI_LIM) • HI_HI_PRI
• Low (LO_LIM) • LO_PRI
• Low low (LO_LO_LIM) • LO_LO_PRI
Additional process alarm detection is based • DV_HI_PRI
on the difference between SP and PV values • DV_LO_PRI
and can be configured via the following Alarms are grouped into five levels of priority
parameters:
• Deviation high (DV_HI_LIM)
• Deviation low (DV_LO_LIM)

8-8
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FoundationTM Fieldbus
8-13 Status Handling

Priority Priority Description Num ber


0 The priority of an alarm condition changes to 0 after the condition that caused the alarm is corrected.
1 An alarm condition w ith a priority of 1 is recognized by the system, but is not reported to the operator.
2 An alarm condition w ith a priority of 2 is reported to the operator, but does not require operator
attention (such as diagnostics and system alerts).
3-7 Alarm conditions of priority 3 to 7 are advisory alarms of increasing priority.
8-15 Alarm conditions of priority 8 to 15 are critical alarms of increasing priority.

Tab. 8-3
Alarm Priorities

8-13 Status Handling


If the input status on the PID block is Bad, the Target to Manual if Bad IN is the
mode of the block reverts to Manual. In only status option supported by
addition, the Target to Manual if Bad IN status the PID function block.
option can be selected to direct the target mode Unsupported options are not
to revert to manual. The status option can be grayed out; they appear on the
set in Manual or Out of Service mode only. screen in the same manner as
supported options.

8-14 Closed Loop Control


To implement basic closed loop control, control. To reduce reset action, configure the
compute the error difference between the RESET parameter to be a large value.
process variable (PV) and setpoint (SP) values The derivative term RATE applies a correction
and calculate a control output signal using a based on the anticipated change in error. De-
PID (Proportional Integral Derivative) function rivative control is typically used in temperature
block. control where large measurement lags exist.
The proportional control function responds The MODE parameter is a switch that indicates
immediately and directly to a change in the PV the target and actual mode of operation. Mode
or SP. The proportional term GAIN applies a selection has a large impact on the operation
change in the loop output based on the current of the PID block:
magnitude of the error multiplied by a gain Manual mode allows the operator to set the
value. value of the loop output signal directly.
The integral control function reduces the Automatic mode allows the operator to select
process error by moving the output in the a setpoint for automatic correction of error
appropriate direction. The integral term using the GAIN, RESET, and RATE tuning
RESET applies a correction based on the values.
magnitude and duration of the error. Set the Cascade and Remote Cascade modes use
RESET parameter to zero for integral-only a setpoint from another block in a
cascaded configuration.

8-9
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
FoundationTM Fieldbus 10/2003
8-15 Closed Loop Control

Remote Out mode is similar to Manual mode Out of Service mode disables the block for
except that the block output is supplied by maintenance.
an external program rather than by the Abrupt changes in the quality of the input signal
operator. can result in unexpected loop behavior. To
Initialization Manual is a non-target mode prevent the output from changing abruptly and
used with cascade configurations while upsetting the process, select the SP-PV Track
transitioning from manual operation to in Man I/O option. This option automatically
automatic operation. sets the loop to Manual if a Bad input status is
Local Override is a non-target mode that detected. While in manual mode, the operator
instructs the block to revert to Local can manage control manually until a Good input
Override when the tracking or fail-safe status is reestablished.
control options are activated.

8-15 Application Information


The PID function block is a powerful, flexible The following examples describe the use of the
control algorithm that is designed to work in a PID block for closed-loop control (basic PID
variety of control strategies. The PID block is loop), feedforward control, cascade control with
configured differently for different applications. master and slave, and complex cascade
control with override.

8-10
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FoundationTM Fieldbus
8-15 Application Information

8-15-1 Application Example 1


Basic PID Block for Steam Heater Control

TCV TC
101 101
Steam Supply

TT TT
100 101

Steam Heater

Condensate
Fig. 8-2
PID Function Block Steam Heater Control Example

Situation Solution
A PID block is used with an AI block and an AO The PID loop uses TT101 as an input and
block to control the flow steam used to heat a provides a signal to the analog output TCV101.
process fluid in a heat exchanger. The diagram The BKCAL_OUT of the AO block and the
below illustrates the process instrumentation. BKCAL_IN of the PID block communicate the
status and quality of information being passed
between the blocks. The status indication
shows that communications is functioning and
the I/O is working properly. The diagram below
illustrates the correct function block
configuration.

Outlet
Temperature
Input BKCAL_IN BKCAL_OUT

AI PID CAS_IN AO
Function Function Function
Block Block OUT Block OUT
OUT IN

TT101 TC101 TCV101

Fig. 8-3
PID Function Block Diagram for Steam Heater Control Example

8-11
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
FoundationTM Fieldbus 10/2003
8-15 Application Information

8-15-2 Application Example 2


Feedforward Control
Situation Solution
In the previous example, control problems can Feedforward control is added to improve the
arise because of a time delay caused by ther- response time of the basic PID control. The
mal inertia between the two flow streams temperature of the inlet process fluid (TT100)
(TT100 and TT101). Variations in the inlet is input to an AI function block and is connected
temperature (TT100) take an excessive to the FF_VAL connector on the PID block.
amount of time to be sensed in the outlet Feedforward control is then enabled
(TT101). This delay causes the product to be (FF_ENABLE), the feedforward value is scaled
out of the desired temperature range. (FF_SCALE), and a gain (FF_GAIN) is
determined. The diagrams below illustrate the
process instrumentation, and the correct
function block configuration.

TCV FF TC
101 101
Steam Supply

TT TT
100 101

Steam Heater

Condensate

Fig. 8-4
PID Function Block Feedforward Control Example
Outlet
Temperature BKCAL_IN BKCAL_OUT
Input

AI PID CAS_IN AO
OUT IN Function
Function Function
FF_VAL Block OUT
Block Block OUT

TT101 TC101 TCV101


Inlet
Temperature
Input

AI
Function
Block OUT

Fig. 8-5
PID Function Block Diagram for Feedforward Control Example

8-12
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FoundationTM Fieldbus
8-15 Application Information

8-15-3 Application Example 3


Cascade Control with Master and Slave Loops
Situation Solution
A slave loop is added to a basic PID control If the flow is controlled, steam pressure
configuration to measure and control steam variations will be compensated before they
flow to the steam heater. Variations in the steam significantly affect the heat exchanger
pressure cause the temperature in the heat temperature. The output from the master
exchanger to change. The temperature temperature loop is used as the setpoint for
variation will later be sensed by TT101. The the slave steam flow loop. The BKCAL_IN and
temperature controller will modify the valve BKCAL_OUT connections on the PID blocks
position to compensate for the steam pressure are used to prevent controller windup on the
change. The process is slow and causes master loop when the slave loop is in Manual
variations in the product temperature. The dia- or Automatic mode, or it has reached an output
gram below illustrates the process constraint. The diagram below illustrates the
instrumentation correct function block configuration.
FC TC
101 101

FT
101
TCV
101

Steam
Supply
TT TT
100 101

Steam Heater

Condensate
Fig. 8-6
PID Function Block Cascade Control Example
Outlet
Temperature
Input BKCAL_IN BKCAL_OUT

AI PID
Function Function
Block Block
OUT IN OUT

Steam TT101 TC101


Flow
Input

AI PID AO
Function Function Function
Block CAS_IN Block IN Block
OUT
OUT
IN
TCV101

Fig. 8-7
PID Function Block Diagram for Cascade Control Example

8-13
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
FoundationTM Fieldbus 10/2003
8-15 Application Information

8-15-4 Application Example 4


Cascade Control with Override
The PID function block can be used with other When the cascade between the slave PID block
function blocks for complex control strategies. and the Control Selector block is open, the open
The diagram below illustrates the function block cascade status is passed to the Control
diagram for cascade control with override. Selector block and through to the PID blocks
When configured for cascade control with supplying input to it. The Control Selector block
override, if one of the PID function blocks and the upstream (master) PID blocks have an
connected to the selector inputs is deselected, actual mode of IMan.
that PID block filters the integral value to the If the instrument connected to the AI block fails,
selected value (the value at its BKCAL_IN). The the AI block can be placed in Manual mode
selected PID block behaves normally and the and set the output to some nominal value for
deselected controller never winds up. At steady use in the Integrator function block. In this case,
state, the deselected PID block offsets its OUT IN at the slave PID block is constant and
value from the selected value by the proportio- prevents the integral term from increasing or
nal term. When the selected block becomes decreasing.
output-limited, it prevents the integral term from
winding further into the limited region.

BKCAL_IN BKCAL_OUT

Slave Controller

PID
CAS_IN Function OUT
Master Controller Block
IN
TC101 AO
PID OUT
Function Function
Block CAS_IN Block

BCAL_SEL_1

Configured for High Selection

IN_1 PID
Control Function
SEL_1 Selector OUT
Block
Function
SEL_2
Block BCAL_SEL_2

Master Controller

PID AI
Function Function
Block OUT Block

Fig. 8-8
PID Function Block Diagram for Cascade Control with Override

8-14
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FoundationTM Fieldbus
8-16 Troubleshooting

8-16 Troubleshooting

Symptom Possible Causes Corrective Action


Mode w ill not 1. Target mode not set. 1. Set target mode to something other than OOS.
leave OOS 2. Configuration error 2. BLOCK_ERR w ill show the configuration error bit set. The follow ing are parameters that must be set before the
block is allow ed out of OOS:
a. BYPASS must be off or on and cannot be left at initial value of 0.
b. OUT_HI_LIM must be less than or equal to OUT_LO_LIM.
c. SP_HI_LIM must be less than or equal to SP_LO_LIM.
3. Resource block 3. The actual mode of the Resource block is OOS. See Resource Block Diagnostics for corrective action.
4. Schedule 4. Block is not scheduled and therefore cannot execute to go to Target Mode. Schedule the block to execute.
Mode w ill not 1. Back Calculation 1. BKCAL_IN
leave IMAN a. The link is not configured (the status w ould show “Not Connected”). Configure the BKCAL_IN link to the
dow nstream block.
b. The dow nstream block is sending back a Quality of “Bad” or a Status of “Not Invited”. See the appropriate
dow nstream block diagnostics for corrective action.

Mode w ill not 1. Target mode not set. 1. Set target mode to something other than OOS.
change to 2. Input 2. IN
AUTO a. The link is not configured (the status w ould show “Not Connected”). Configure the IN link to the block.
b. The upstream block is sending back a Quality of “Bad” or a Status of “Not Invited”. See the appropriate
upstream block diagnostics for corrective action.
Mode w ill not 1.Target mode not set. 1. Set target mode to something other than OOS.
change to CAS 2. Cascade input 2. CAS_IN
a. The link is not configured (the status w ould show “Not Connected”). Configure the CAS_IN link to the block.
b. The upstream block is sending back a Quality of “Bad” or a Status of “Not Invited”. See the appropriate up
stream block diagnostics for corrective action.
Mode sheds 1. Remote Cascade Value 1. Host system is not w riting RCAS_IN w ith a quality and status of “good cascade” w ithin shed time (see 2 below ).
from RCAS to
AUTO 2. Shed Timer 2. The mode shed timer, SHED_RCAS in the resource block is set too low . Increase the value.
Mode sheds 1. Remote output value 1. Host system is not w riting ROUT_IN w ith a quality and status of “good cascade” w ithin shed time (see 2 below ).
from ROUT to
MAN 2. Shed timer 2. The mode shed timer, SHED_RCAS, in the resource block is set too low . Increase the value.
Process and/or 1. Features 1. FEATURES_SEL does not have Alerts enabled. Enable the Alerts bit.
block alarms 2. Notification 2. LIM_NOTIFY is not high enough. Set equal to MAX_NOTIFY.
w ill not w ork. 3. Status Options 3. STATUS_OPTS has Propagate Fault Forw ard bit set. This should be cleared to cause an alarm to occur.

Tab. 8-4
Troubleshooting for PID

8-15
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
FoundationTM Fieldbus 10/2003

8-16
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
10/2003 FoundationTM Fieldbus

APPENDIX
Operation with EMERSON™ Process Management DeltaV™

A-1 About DeltaV Software with AMS inside


AMSinside DeltaV software allows users to With AMSinside, users can also access status
manage their instrumentation, and to perform and diagnostic data from smart devices and
on-line configurations of their instruments. monitor their performance.
The ability to communicate with instruments and AMS leverages the I/O capabilities of the
configure instruments on-line facilitates control system to gather asset management
instrument commissioning and loop validation. data without interfering with the control system’s
operations.

A-2 Install the Analyzer onto DeltaVTM

The following procedures


assume that the DeltaV and the
analyzer are installed and
powered.

The following steps have to be performed to The files probably will be on a floppy disk
install a new device onto a DeltaVTM system: or a CD-ROM that accompanies your
• From the start menu select DeltaV > device. On CD-ROMs delivered together
Engineering > DeltaV Explorer with Emerson Process Management
• Select/Expand „Library“ (right below analyzers the files are located in the
DeltaV_System) directory \Fieldbus. Dependent on the
• Select „Fieldbus Devices“, using right existent system use the files of the
mouse button. Click on „Fieldbus appropriate subdirectory.
Devices“. This will bring up a list of options • After answering „yes“ to the first prompt,
• From the list, select „Add Device Definiti- DeltaV will start the installation.
on...“ This should give you a „Browse for Fig. A-1 shows the „Exploring DeltaV“ screen
folder“ selection box. for reference.
Browse to the directory that contains the 7
files needed to „register“ a new device with
DeltaV. These file will consist of 3 *.dll files,
*.sym, *.ffo, *.fhx and *.reg file.

A-1
FoundationTM Fieldbus Communication Instruction Manual
ETC01184
FoundationTM Fieldbus 10/2003

Fig. A-1
DeltaV Explorer

A-2
Instruction Manual
ETC01184
10/2003 FoundationTM Fieldbus MLT 1-2 & CAT 200
Instruction Manual
TM ETC01184
Foundation Fieldbus MLT 1-2 & CAT 200 10/2003

WORLD HEADQUARTERS
ROSEMOUNT ANALYTICAL EUROPE
Emerson Process Management
GmbH & Co. OHG
Industriestrasse 1
63594 Hasselroth
Germany
T 49 6055 884 0
F 49 6055 884209

Emerson Process Management


Rosemount Analytical Inc.
6565 P Davis Industrial Parkway
Solon, OH 44139 USA
T 440.914.1261
Toll Free in US and Canada 800.433.6076
F 440.914.1271
e-mail: gas.csc@EmersonProcess.com
www.raihome.com

GAS CHROMATOGRAPHY CENTER


AND LATIN AMERICA
Emerson Process Management
Rosemount Analytical Inc.
11100 Brittmoore Park Drive
Houston, TX 77041
T 713 467 6000
F 713 827 3329

EUROPE, MIDDLE EAST AND AFRICA


Emerson Process Management
Shared Services Limited
Heath Place
Bognor Regis
West Sussex PO22 9SH
England
T 44 1243 863121
F 44 1243 845354

ASIA-PACIFIC
Emerson Process Management
Asia Pacific Private Limited
1 Pandan Crescent
Singapore 128461
Republic of Singapore
T 65 6 777 8211
F 65 6 777 0947
e-mail: analytical@ap.emersonprocess.com

© Emerson Process Management GmbH & Co. OHG 2007

You might also like