Rosemount Manual: MLT 1, MLT 2 and CAT 200 FOUNDATION Fieldbus Communication Software-3rd Ed. | Rosemount Manuals & Guides

Instruction Manual

ETC01 184
10/2003

Instruction Manual

FoundationTM Fieldbus
Communication Option for
ML T 1, MLT 2 and CAT 200

rd

Edition 10/2003

3

www.EmersonProcess.com

Foundation Fieldbus for MLT 1, MLT 2 & CAT 200 Instruction Manual

ETC01184

10/2003

ESSENTIAL INSTRUCTIONS

READ THIS P AGE BEFORE PROCEEDING!

Emerson Process Management (Rosemount Analytical) designs, manufactures and test s
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.

• T o 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 W ARRANTY. 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 [phone]
F [phone]
Internet: www.EmersonProcess.com

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184
10/2003

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.

FOUNDATIONTM Fieldbus

Highlights an operation or
maintenance procedure,
practice, condition,
statement, etc. If not strictly
observed, could result in
injury, death, or long-term
health hazards of personnel.

Highlights an essential operating
procedure, condition or statement.

Highlights an operation or
maintenance procedure,
practice, condition,
statement, etc. If not strictly
observed, could result in
damage to or destruction of
equipment, or loss of
effectiveness.

NOTE

P-1

FOUNDATIONTM Fieldbus Communication Instruction Manual

FOUNDATIONTM Fieldbus

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.

ETC01184

10/2003

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 FOUNDATIONTM 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

FOUNDATIONTM Fieldbus

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

ETC01184

10/2003

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

Table of Contents

FOUNDATIONTM Fieldbus

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

FOUNDATIONTM Fieldbus

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

ETC01184

10/2003

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

SECTION 1

FOUNDATIONTM Fieldbus Technology

1-1 Overview

FOUNDATIONTM Fieldbus

FOUNDATIONTM Fieldbus is an all digital, serial,
two-way communication system that
interconnects field equipment such as sensors,
actuators, and controllers. Fieldbus is a Local
Area Network (LAN) for instruments used in
both process and manufacturing automation
with built-in capacity to distribute the control
application across the network. It is the ability
to distribute control among intelligent field
devices on the plant floor and digitally
communicate that information at high speed
that makes FOUNDATIONTM Fieldbus an enabling
technology.
Emerson offers a full range of products from
field devices to the DeltaV scalable control
system to allow an easy transition to Fieldbus
technology.
The Fieldbus retains the features of the
4-20 mA analog system, including
standardized physical interface to the wire, bus
powered devices on a single wire, and intrinsic
safety options, and enables additional
capabilities such as:

• Increased capabilities due to full
digital communications.

• Reduced wiring and wire
terminations due to multiple

devices on one set of wires.

• Increased selection of suppliers
due to interoperability.

• Reduced loading on control room
equipment with the distribution of
some control and input/output
functions to field devices.

• Speed options for process control
and manufacturing applications.

NOTE: The following descriptions and
definitions are not intended as a training guide
for Foundation Fieldbus technology but are
presented as an overview for those not familiar
with Fieldbus and to define device specific
attributes for the Fieldbus system engineer.
Anyone attempting to implement Fieldbus
communications and control with this analyzer
must be well versed in Fieldbus technology and
protocol and must be competent in
programming using available tools such as
DeltaV. See „References“ below for additional
sources for Fieldbus technology and
methodology.

1-2 Introduction

A Fieldbus system is a distributed system
composed of field devices and control and
monitoring equipment integrated into the
physical environment of a plant or factory.
Fieldbus devices work together to provide I/O
and control for automated processes and
operations. The Fieldbus Foundation provides
a framework for describing these systems as

a collection of physical devices interconnected
by a Fieldbus network. One of the ways that
the physical devices are used is to perform their
portion of the total system operation by
implementing one or more function blocks.

1-1

FOUNDATIONTM Fieldbus

1-2-1 Function Blocks

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184

10/2003

1-2-1 Function Blocks

Function blocks within the Fieldbus device per­form the various functions required for process
control. Because each system is different, the
mix and configuration of functions are different.
Therefore, the Fieldbus FOUNDATION has
designed a range of function blocks, each
addressing a different need.
Function blocks perform process control
functions, such as analog input (AI) and analog
output (AO) functions as well as proportional­integral-derivative (PID) functions. The
standard function blocks provide a common
structure for defining function block inputs,
outputs, control parameters, events, alarms,
and modes, and combining them into a process
that can be implemented within a single device
or over the Fieldbus network. This simplifies
the identification of characteristics that are
common to function blocks.
The Fieldbus FOUNDATION has established the
function blocks by defining a small set of
parameters used in all function blocks called
universal parameters. The FOUNDATION has also
defined a standard set of function block

classes, such as input, output, control, and
calculation blocks. Each of these classes also
has a small set of parameters established for
it. They have also published definitions for
transducer blocks commonly used with
standard function blocks. Examples include
temperature, pressure, level, and flow
transducer blocks.
The FOUNDATION specifications and definitions
allow vendors to add their own parameters by
importing and sub-classing specified classes.
This approach permits extending function block
definitions as new requirements are discovered
and as technology advances.
Fig. 1-1 illustrates the internal structure of a
function block. When execution begins, input
parameter values from other blocks are
snapped-in by the block. The input snap
process ensures that these values do not
change during the block execution. New values
received for these parameters do not affect the
snapped values and will not be used by the
function block during the current execution.

1-2

Input Events

Input Parameter

Fig. 1-1

Function Block Internal Structure

Input OutputProcessing

Status Status

Execution Control Output Events

Output

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184
10/2003

1-2-2 Device Descriptions

FOUNDATIONTM Fieldbus

Once the inputs are snapped, the algorithm
operates on them, generating outputs as it
progresses. Algorithm executions are
controlled through the setting of contained
parameters. Contained parameters are
internal to function blocks and do not appear
as normal input and output parameters.
However, they may be accessed and modified
remotely, as specified by the function block.
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
definitions that are associated with the function
blocks. Device descriptions provide for the
definition and description of the function blocks
and their parameters.
To promote consistency of definition and
understanding, descriptive information, such as
data type and length, is maintained in the device
description. Device Descriptions are written
using an open language called the Device
Description Language (DDL). Parameter
transfers between function blocks can be easily
verified because all parameters are described
using the same language. Once written, the
device description can be stored on an external
medium, such as a CD-ROM or diskette.
Users can then read the device description

A block is a tagged logical processing unit. The
tag is the name of the block. System
management services locate a block by its tag.
Thus the service personnel need only know the
tag of the block to access or change the
appropriate block parameters.
Function blocks are also capable of performing
short-term data collection and storage for
reviewing their behavior.

from the external medium. The use of an open
language in the device description permits
interoperability of function blocks within
devices from various vendors. Additionally,
human interface devices, such as operator
consoles and computers, do not have to be
programmed specifically for each type of
device on the bus. Instead their displays and
interactions with devices are driven from the
device descriptions.
Device descriptions may also include a set of
processing routines called methods. Methods
provide a procedure for accessing and
manipulating parameters within a device.

1-3

FOUNDATIONTM Fieldbus Communication Instruction Manual

FOUNDATIONTM Fieldbus

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

ETC01184

10/2003

Resource blocks contain the hardware specific
characteristics associated with a device; they
have no input or output parameters. The
algorithm within a resource block monitors and
controls the general operation of the physical
device hardware. The execution of this
algorithm is dependent on the characteristics

1-3-2 Transducer Blocks

Transducer blocks connect function blocks to
local input/output functions. They read sensor
hardware and write to effector (actuator)
hardware. This permits the transducer block to
execute as frequently as necessary to obtain
good data from sensors and ensure proper

1-3-3 Alerts

When an alert occurs, execution control sends
an event notification and waits a specified
period of time for an acknowledgment to be
received. This occurs even if the condition that
caused the alert no longer exists. If the
acknowledgment is not received within the pre­specified time-out period, the event notification
is retransmitted. This assures that alert
messages are not lost.

of the physical device, as defined by the
manufacturer. As a result of this activity, the
algorithm may cause the generation of events.
There is only one resource block defined for a
device. For example, when the mode of a
resource block is „out of service,“ it impacts all
of the other blocks.

writes to the actuator without burdening the
function blocks that use the data. The transducer
block also isolates the function block from the
vendor specific characteristics of the physical
I/O.

Two types of alerts are defined for the block,
events and alarms. Events are used to report
a status change when a block leaves a
particular state, such as when a parameter
crosses a threshold. Alarms not only report a
status change when a block leaves a particular
state, but also report when it returns back to
that state.

1-4

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184
10/2003

1-4 Network Communication

1-4 Network Communication

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

FOUNDATIONTM Fieldbus

LAS

(Link Active Scheduler)

Link Master

Fig. 1-2

Single Link Fieldbus Network

1-4-1 Link Active Scheduler (LAS)

All links have one and only one Link Active
Scheduler (LAS). The LAS operates as the bus
arbiter for the link. The LAS does the following:

• recognizes and adds new devices to the
link.

• removes non-responsive devices from the
link.

• distributes Data Link (DL) and Link
Scheduling (LS) time on the link. Data Link
Time is a network-wide time periodically
distributed by the LAS to synchronize all
device clocks on the bus. Link Scheduling
time is a link-specific time represented as
an offset from Data Link Time. It is used
to indicate when the LAS on each link
begins and repeats its schedule. It is used
by system management to synchronize
function block execution with the data
transfers scheduled by the LAS.

• polls devices for process loop data at
scheduled transmission times.

• distributes a priority-driven token to
devices between scheduled
transmissions.

Any device on the link may become the LAS,
as long as it is capable. The devices that are

Fieldbus Link

Basic Devices and/or LinkMaster Devices

capable of becoming the LAS are called link
master devices. All other devices are referred
to as basic devices. When a segment first
starts up, or upon failure of the existing LAS,
the link master devices on the segment bid to
become the LAS. The link master that wins the
bid begins operating as the LAS immediately
upon completion of the bidding process. Link
masters that do not become the LAS act as
basic devices. However, the link masters can
act as LAS backups by monitoring the link for
failure of the LAS and then bidding to become
the LAS when a LAS failure is detected.
Only one device can communicate at a time.
Permission to communicate on the bus is
controlled by a centralized token passed
between devices by the LAS. Only the device
with the token can communicate. The LAS
maintains a list of all devices that need access
to the bus. This list is called the „Live List.“
Two types of tokens are used by the LAS. A
time-critical token, compel data (CD), is sent
by the LAS according to a schedule. A non­time critical token, pass token (PT), is sent by
the LAS to each device in ascending numerical
order according to address.

1-5

FOUNDATIONTM Fieldbus

1-4-2 Device Addressing

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184

10/2003

1-4-2 Device Addressing

Fieldbus uses addresses between 0 and 255.
Addresses 0 through 15 are reserved for group
addressing and for use by the data link layer.
For all Emerson Fieldbus devices addresses
20 through 35 are available to the device. If
there are two or more devices with the same
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
reporting is used to transfer critical
process loop data, such as the process
variable. The data producers (publishers)
post the data in a buffer that is transmitted
to the subscriber (S), when the publisher

programmed address. Each of the other
devices will be given one of four temporary
addresses between 248 and 251. If a
temporary address is not available, the device
will be unavailable until a temporary address
becomes available.

receives the Compel data. The buffer
contains only one copy of the data. New
data completely overwrites previous data.
Updates to published data are transferred
simultaneously to all subscribers in a single
broadcast. Transfers of this type can be
scheduled on a precisely periodic basis.

• Report Distribution: This type of
reporting is used to broadcast and
multicast event and trend reports. The
destination address may be predefined so
that all reports are sent to the same
address, or it may be provided separately
with each report. Transfers of this type are

• Client/Server: This type of reporting is
used for request/response exchanges
between pairs of devices. Like Report Dis­tribution reporting, the transfers are
queued, unscheduled, and prioritized.
Queued means the messages are sent
and received in the order submitted for

queued. They are delivered to the
receivers in the order transmitted, although
there may be gaps due to corrupted
transfers. These transfers are unscheduled
and occur in between scheduled transfers
at a given priority.

transmission, according to their priority,
without overwriting previous messages.
However, unlike Report Distribution, these
transfers are flow controlled and employ a
retransmission procedure to recover from
corrupted transfers.

1-6

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184
10/2003

1-4-3 Scheduled Transfers

FOUNDATIONTM Fieldbus

Fig. 1-3 diagrams the method of scheduled
data transfer. Scheduled data transfers are
typically used for the regular cyclic transfer of
process loop data between devices on the
Fieldbus. Scheduled transfers use publisher/
subscriber type of reporting for data transfer.
The Link Active Scheduler maintains a list of
transmit times for all publishers in all devices

LAS

Schedule

X
Y
Z

CD(X,A)

DT(A)

AB

SP

that need to be cyclically transmitted. When it
is time for a device to publish data, the LAS
issues a Compel Data (CD) message to the
device. Upon receipt of the CD, the device
broadcasts or „publishes“ the data to all
devices on the Fieldbus. Any device that is
configured to receive the data is called a
„subscriber.“

CA

SP

DA

SP

Fig. 1-3

Scheduled Data Transfer

Device X

Device Y Device Z

LAS = Link Active Scheduler
P = Publisher
S = Subscriber
CD = Compel Data
DT = Data Transfer Packet

1-7

FOUNDATIONTM Fieldbus Communication Instruction Manual

FOUNDATIONTM Fieldbus

1-4-4 Inscheduled Transfers

1-4-4 Unscheduled Transfers

Figure 1-4 diagrams an unscheduled transfer.
Unscheduled transfers are used for things like
user-initiated changes, including set point
changes, mode changes, tuning changes, and
upload/download. Unscheduled transfers use
either report distribution or client/server type
of reporting for transferring data.
All of the devices on the Fieldbus are given a
chance to send unscheduled messages

ETC01184

10/2003

between transmissions of scheduled data. The
LAS grants permission to a device to use the
Fieldbus by issuing a pass token (PT)
message to the device. When the device
receives the PT, it is allowed to send messages
until it has finished or until the „maximum token
hold time“ has expired, whichever is the shorter
time. The message may be sent to a single
destination or to multiple destinations.

LAS

Schedule

X
Y
Z

Fig. 1-4

Unscheduled Data Transfer

PT(Z)

AB

M

P

Device X

S

LAS = Link Active Scheduler
P = Publisher
S = Subscriber
PT = Pass Token
M = Message

DT(M)

CA

P

Device Y Device Z

S

DA

M

P

S

1-8

FOUNDATIONTM Fieldbus Communication Instruction Manual

AIAIAOA

ETC01184
10/2003

1-4-5 Function Block Scheduling

1-4-5 Function Block Scheduling

FOUNDATIONTM Fieldbus

Figure 1-5 shows an example of a link
schedule. A single iteration of the link-wide
schedule is called the macrocycle. When the
system is configured and the function blocks
are linked, a master link-wide schedule is
created for the LAS. Each device maintains
its portion of the link-wide schedule, known as

Device 1

Scheduled

Communication

Unscheduled

Communication

Macrocycle Start Time

Offset from macrocycle Start

time = 0 for AI Execution

Offset from macrocycle Start

time = 20 for AI Communication

the Function Block Schedule. The Function
Block Schedule indicates when the function
blocks for the device are to be executed. The
scheduled execution time for each function
block is represented as an offset from the
beginning of the macrocycle start time.

Sequence Repeats

Offset from macrocycle Start

time = 30 for PID Execution

Device 2

Macrocycle

Fig. 1-5

Example of Link Schedule
(Showing scheduled and unscheduled communication)

To support synchronization of schedules,
periodically Link Scheduling (LS) time is
distributed. The beginning of the macrocycle
represents a common starting time for all

Offset from macrocycle Start

time = 50 for AO Execution

Function Block schedules on a link and for the
LAS link-wide schedule. This permits function
block executions and their corresponding data
transfers to be synchronized in time.

PID

OPID

1-9

FOUNDATIONTM Fieldbus

1-5 References

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184

10/2003

1-5 References

The following Fieldbus FOUNDATION documents
should be used to gain an understanding of

Document Number Document Title
FF-890 Fieldbus Foundation™ Fieldbus Specification —

Function Block Application Proces s – Part 1

FF-891 Fieldbus Foundation™ Fieldbus Specification —

Function Block Application Proces s – 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.
Established in September 1994 by a merger
of World FIP North America and the Inter­operable Systems Project (ISP), the foundation
is a not-for-profit corporation that consists of
nearly 120 of the world’s leading suppliers and
end users of process control and manufacturing
automation products. Working together, these
companies have provided unparalleled support
for a worldwide Fieldbus protocol, and have
made major contributions to the IEC/ISA
Fieldbus standards development.
Important differences exist between the
Fieldbus Foundation and other Fieldbus initia­tives. The foundation’s technology ­FOUNDATION Fieldbus - is unique insomuch
as it is designed to support mission-critical
applications where the proper transfer and
handling of data is essential. Unlike proprietary
network protocols, FOUNDATION Fieldbus is
neither owned by any individual company, or
controlled by a single nation or regulatory body.

Fieldbus, and are referenced wherever
appropriate in the document:

Rather, it is an „open,“ interoperable Fieldbus
that is based on the International Standards
Organization’s Open System Interconnect (OSI/
ISO) seven-layer communications model. The
FOUNDATION specification is compatible with
the officially sanctioned SP50 standards project
of The International Society for Measurement
and Control (ISA) and the International
Electrotechnical Committee (IEC).

Contact information:

9005 Mountain Ridge Drive

Bowie Buldg - Suite 190

Austin, TX 78759-5316, USA

Tel: [phone]

Fax: [phone]

Email: [e-mail]

Internet: www.fieldbus.org

1-10

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184
10/2003

1-6 Implemented Function Blocks

1-6 Implemented Function Blocks

For the MLT we have implemented the
following function blocks :

Inte n de d Use or
Transducer Block Channe l Assignments

Resource Block (RB)

Transd ucerBlock (T B)

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)

Analog-Input Block 4 (AI4)

Analog-Input Block 5 (AI5)

Analog-Output Block1 (AO1)

Analog-Output Block2 (AO2)

Arithmetic Block (ARTHM)

PID Block (P ID) p rop ort ional/int egral/derivative cont rol of any A I-block

Inp ut Selector Block (ISEL) s elector of any AI-block

SENSOR_FLOW_1 (see Table 7? 1)

SENSOR_FLOW_2 (see Table 7? 1)

SENSOR_PRESSURE_1(read) (see Table 7? 1)

SENSOR_PRESSURE_1(w rite) (seeTable 7? 2)

SENSOR_PRESSURE_2(w rite) (seeTable 7? 2)

th

4

order poly nomial for any AI-block

FOUNDATIONTM Fieldbus

Tab. 1-2

Implemented Function Blocks

1-11

FOUNDATIONTM Fieldbus

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184

10/2003

1-12

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184
10/2003

SECTION 2

Transducer Block

FOUNDATIONTM Fieldbus

The Transducer Block part was designed to
provide the information necessary to interface
the MLT to the Fieldbus. The data structures
should be used for transferring Fieldbus
information between the MLT’s Object
Dictionary and other hosts and devices on
Fieldbus.
Three tables are used to describe the MLT
parameters. The List of Parameters table
defines the relative index value used to
reference the parameter in the MLT Transducer
Block Object Dictionary and the mnemonic
used to reference the parameter, as well as the
View(s )in which the parameter is contained.
The Parameter Descriptions table gives a brief
description of the behavior of each of the
parameters. The Parameter Attributes table
describes the key attributes of each of the
parameters.

The transmitter specific detailed status and its
relationship to standard Fieldbus block alarms
and errors are shown in a table in the Detailed
Status section of the document. The I/O channel
assignments and their status values are shown
in the Channel Assignments section.
Finally the default values for parameters are
defined. These are the parameters which will
be loaded into the Fieldbus Interface Board’s
database before any communication to the
transducer itself is performed.
Dynamic parameter default values are
specified to aid in configuring static simulations
of the transducer block. For example, when
creating a placeholder for this device in a host
application’s database.

2-1

FOUNDATIONTM Fieldbus Communication Instruction Manual

FOUNDATIONTM Fieldbus

2-1 List of Transducer Block Parameters

2-1 List of Transducer Block Parameters

ETC01184

10/2003

This section defines parameter access for a
basic sensor.

Re la ti ve

Index

Parameter Mnemonic VIEW_1 VIEW_2

1 ST_REV 22222

2 TAG_DESC

3 STRA TEGY 2

4 ALERT_KEY 1

5 MODE_BLK 4 4

6 BLOCK_ERR 2 2

7 UPDATE_EV T

8 BLOCK_ALM

9 TRA NSDUCER_DIRECTORY

10 TRA NSDUCER_TY PE 2 2 2 2

11 XD_ERROR 1 1

12 COLL ECTION_DIRECTORY

13 PRIMARY_VALUE_TYPE_1 2

14 PRIMARY_VALUE_1 5 5

15 PRIMARY_VA LUE_RANGE_1 11

16 CAL_POINT_HI_1 4

17 CAL_POINT_LO_1 4

18 CAL_MIN_SPA N_1 4

19 CAL_UNIT_1 2

20 CAL_GAS_TIME_1 2

21 CAL_ZERO_TOLERANCE_1 4

22 CAL_SPA N_TOLERA NCE_1 4

23 CAL_SLOPE_1 4

24 CAL_CONSTANT_1 4

25 CAL_ZERO_INTERV A L_1 2

26 CAL_ZERO_DATE_1 7

27 CAL_SPA N_INTERVAL_1 2

28 CAL_SPA N_DATE_1 7

29 CAL_ ZERO_SPA N_INTERVAL_1 2

30 CAL_ ZERO_SPA N_DA TE_1 7

31 SPA N_CA L_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_ RA W_ CONCENTRA TION_1 4

38 SENSOR_A VG_CYCLES_1 2

39 SENSOR_A VG_METHOD_1 1

40 SENSOR_NOISE_REFVAL_1 4

Parameter access is described in FF-890.

VIEW_3 VIEW_3 VIEW_4 VIEW_4 VIEW_4 VIEW_4

st

1

nd

2

st

1

nd

2

rd

3

th

4

Tab. 2-1

Transducer Block Parameters

2-2

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184
10/2003

2-1 List of Transducer Block Parameters

FOUNDATIONTM Fieldbus

Re la ti ve

Index

Parameter Mnemonic VIEW_1 VIEW_2

41 SENSOR_NOISE_LEVEL_1 4

42 SENSOR_NOISE_TUNE_ 1 4

4 3 S ENSO R_ Z TEMPERA T URE_ 1 4

4 4 S ENSO R_ ST EMPERA T URE_ 1 4

4 5 S ENSO R_ TEMP_ OF FS ET_ 1 4

46 S ENSOR_ CROSS_ INTF_OFFSET_ 1 4

47 S ENSOR_ TEMP_FA CTOR_1 4

48 S ENSOR_ PRESSURE_1 5 5

49 S ENSOR_ PRESSURE_FA CTOR_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 CA L_UNIT_2 2

59 CAL_GAS_TIME_2 2

60 CAL_ZERO_TOLERANCE_2 4

61 CA L_SPA N_TOL ERA NCE_2 4

62 CAL_SLOPE_2 4

63 CAL_CONSTANT_2 4

64 CAL_ZERO_INTERV AL_2 2

65 CAL_ZERO_DATE_2 7

66 CA L_SPA N_INTERV AL _2 2

67 CA L_SPA N_DA TE_2 7

68 CAL_ Z ERO_SPA N_INTERVAL_2 2

69 CA L_ Z ERO_SPA N_DA TE_2 7

70 SPA N_CAL_DATE_2 7

71 ZERO_CAL_DATE_2 7

72 SENSOR_TYPE_2 2

73 SENSOR_RANGE_2

74 SENSOR_ID_2 30

75 S ENSOR_ FILTER_V A LUE_2 4

76 S ENSOR_ RAW _CONCENTRA TION_2 4

77 SENSOR_AVG_CYCLES_2 2

78 SENSOR_AVG_METHOD_2 1

79 SENSOR_NOISE_REFVA L_2 4

80 SENSOR_NOISE_LEVEL_2 4

VIEW_3 VIEW_3 VIEW_4 VIEW_4 VIEW_4 VIEW_4

st

1

nd

2

st

1

nd

2

rd

3

4

11

th

Tab. 2-1 (cont’d)

Transducer Block Parameters

2-3

FOUNDATIONTM Fieldbus

2-1 List of Transducer Block Parameters

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184

10/2003

Re la ti ve

Index

Parameter Mnemonic VIEW_1 VIEW_2

81 SENSOR_NOISE_TUNE_2 4

82 SENSOR_ ZTEMPERATURE_2 4

83 SENSOR_ STEMPERA TURE_2 4

8 4 SENS OR _T EMP_O FFS ET_ 2 4

85 SENSOR_ CROSS_ INTF_OFFSET_2 4

86 SENSOR_TEMP_FACTOR_2 4

87 SENSOR_ PRESSURE_2 5 5

88 SENSOR_ PRESSURE_FA CTOR_2 4

89 SENSOR_FLOW_2 5 5

90 SENSOR_OPTS_2 4

91 ANALYZER_OPTS 1

92 MEA SUREMENT_OPTS 2

93 GA S_ CTRL_ STA TE 2 2

94 CAL_STATE 2 2

95 CAL_STEP 1

96 CAL_OPTS 1

97 FUNCTION_CA LL 1

98 DETA ILED_FA ILURE 4

99 DETA ILED_MA INTENA NCE 4

100 DETA ILED_STA TUS 4

101 SIM_DETAILED_FAILURE 4

10 2 SIM_DETA ILED_MA INTENA NCE 4

103 SIM_DETAILED_STA TUS 4

104 DEVICE_TIME 7

105 MODULE_SN 20

10 6 MA NUFA CTURING_DA TE 3 0

107 ANALYZER_HW_VERSION 30

108 ANALYZER_SW_VERSION 30

109 ACCESS_MODE 1

110 STA TS_ATTEMPTS 4

111 STA TS_TIMEOUTS 4

Totals 452486116721108383

VIEW_3 VIEW_3 VIEW_4 VIEW_4 VIEW_4 VIEW_4

st

1

nd

2

st

1

nd

2

rd

3

th

4

2-4

Tab. 2-1 (cont’d)

Transducer Block Parameters

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184
10/2003

2-2 Transducer Block Parameter Descriptions

2-2 Transducer Block Parameter Descriptions

FOUNDATIONTM Fieldbus

This table gives a description of all parameters
in the above table, or gives the location in the

Parameter Mnem onic Description

ACCESS_MODE This parameter c ontrols access to the transducer block parameters. See Table 6-8.

ALERT_KEY See FF-891 sec tion 5.3.

ANALY ZER_HW_V ERSION The type of the analyzer hardw are including boot image v ers ion string

ANALY ZER_OPTS The installed analyzer options

ANALY ZER_SW_VERSION The version number of the analyzer softw are

BLOCK_ALM See FF-891 sec tion 5.3.

BLOCK_ERR See FF-891 sec tion 5.3.

CAL_CONSTANT_n The zero correction off set (c alculated by zero calibration).

CAL_GAS_TIME Purge delay time (in secs) f or c alibration gas s upply

CAL_MIN_SPAN_n See FF-903 sec tion 3.3.

CAL_OPTS The calibration options. See Table 6-5.

CAL_POINT_HI_n See FF-903 sec tion 3.3

CAL_POINT_LO_n See FF-903 sec tion 3.3

CAL_SLOPE_n This parameter represents the s pan correction fac tor (calculated by span calibration).

CAL_SPA N_DATE_n The date/time the next automatic span calibration w ill be s tarted.

CAL_SPAN_INTERVAL_n The time interval (in hours) f or automatic span calibrations (0 = OFF).

CAL_SPAN_TOLERANCE_n

CAL_STATE This parameter repres ents the present state a c alibration cycle is in.

CAL_STEP This parameter is used to control zero and/or span calibrations. See Table 6-3 for the def inition of states .

CAL_UNIT_n See FF- 903 sec tion 3.3.

CAL_ZERO_DATE_n The date/time the next automatic zero c alibration 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 nex t automatic z er o & s pan calibrations w ill be s tarted.

CAL_ZERO_SPA N_INTERVAL_n The time interval (in hours) f or automatic zero & span calibrations (0 = OFF).

CA L_Z ERO_TO LERANCE_n

COLLECTION_DIRECTORY See FF-891 sec tion 5.3.

DETAILED_FAILURE This is a bit-enumerated value used to communicate the f ailures of the device. SeeTable 6-9.

DETAILED_MA INTENANCE This is a bit-enumerated value used to communicate the maintenanc e reques ts of the device. SeeTable 6-10.

DETAILED_STA TUS 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 c lock. It is used to automatically start time/date c ontrolled proc edures .

FUNCTION_CALL This parameter is us ed to call certain device procedures. SeeTable 6-12 f or the definition of the states .

GAS_CTRL_STATE The state of controlling t he gas v alv es a s w ell as gas p umps.

MANUFA CTURING_DA TE The analyzer's manufacturing date string

MEASUREMENT_OPTS The different kind of options f or the measurement.

MODE_BLK See FF-891 section 5.3.

MODULE_SN The analyzer 's serial number

PRIMARY_VA LUE_n See FF-903 sec tion 3.3.

PRIMARY_VA LUE_RANGE_n See FF-903 sec tion 3.3.

PRIMARY_VA LUE_TYPE_n See FF-903 sec tion 3.3 and 4.1.

SENSOR_AVG_CYCLES_n

SENS OR_A V G_ METHO D_n

SENSOR_CROSS_INTF_OFFSET_n The zero correction of cross interference compensation.

SENSOR_FILTER_V ALUE_n The t90 respons e time (in secs) f or gas change.

The allowed deviation tolerance (% of CAL_POINT _HI_n) for a span calibration.

The allowed deviation tolerance (% of CAL_POINT _HI_n) for a zero c alibration.

To sync hronize it w ith the FF- central date/time w e should w rite to in certain time intervals.

The number of preaveraging cycles for digital signal filtering.

The preaveraging method for digital signal filtering (arithmetic or sliding).

Fieldbus specifications that the description can
be found.

Tab. 2-2

Transducer Block Parameter Descriptions

2-5

FOUNDATIONTM Fieldbus Communication Instruction Manual

FOUNDATIONTM Fieldbus

2-1 List of Transducer Block Parameters

Parameter Mnemonic Description

SENSOR_FLOW_n The current gas f low (in l/min) of a measurement sens or. If the optional f low sens or is installed this is a

SENSOR_ID_n String which 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 ref erence value the dynamic noise filtering becomes active.

SENSOR_NOISE_REFVAL_n This parameter is a ref erence v alue (in ppm) f or the dy namic noise f ilter.

SENSOR_NOISE_TUNE_n Tuning fac tor how extremely the dynamic nois e f ilter r educ es dynamic noises.

SENSOR_OPTS_n The installed sens or spec if ic options.

SENSOR_ PRESSURE_n

SENSOR_PRESSURE_FACTOR_n This parameter repr esents the span c orr ec tion of pres sure c ompensation.

SENSOR_RANGE_n See FF-903 section 3.3.

SENSOR_RA W_CONCENTRATION_n This parameter repres ents the raw value of A /D-Conver sion of measurement channel.

SENSOR_STEMPERATURE_n This par ameter is the temperature (in °C) used for c ompensation of span cor rec tions.

SENSOR_TEMP_FACTOR_n This parameter r epresents the s pan corr ection of temperature compensation

SENSOR_TEMP_OFFSET_n This parameter repres ents the zero correction of temperature compensation.

SENSOR_TY PE_n See FF-903 sec tion 3.3 and 4.3.

SENSOR_ZTEMPERA TURE_n This parameter is the temperature ( in °C) used f or compensation of zero c orrec tions.

SIM_DETAILED_FAILURE This is a bit-enumerated value used to simulate the f ailures 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 dev ice. SeeTable 6-11.

SPA N_CAL_DATE_n The date the last span calibration was perf ormed.

ST_REV See FF-891 section 5.3.

STATS_ATTEMPTS Total number of messages s ent to the transduc er a/d board.

STATS_FAILURES Total number of f ailed a/d board mess age attempts.

STATS_TIMEOUTS Total number of timed out a/d board mess age attempts.

STRATEGY See FF-891 section 5.3.

TAG_DESC See FF-891 section 5.3.

TRA NSDUCER_DIRECTORY See FF-903 section 3.3.

TRA NSDUCER_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 sec tion 3.3.

ZERO_CAL_DATE_n The date the last zero c alibration w as performed.

dynamic variable. If the sensor is not installed w e do not use for further evaluations.

The current press ure (in hPa) of a measurement sensor:

If internal pressure sensor is installed this is a readonly dynamic v ariable.

If no press ure sensor is ins talled w e can input the cur rent pres sure v alue.

If w e use remote pressure w e have to input via A O block. There w e have to s elect appropr iate as signment
by the CHA NNEL-parameter.

ETC01184

10/2003

Tab. 2-2 (cont’d)
Transducer Block Parameter Descriptions

2-6

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184
10/2003

2-3 Transducer Block Parameter Attribute Definitions

2-3 Transducer Block Parameter Attribute Definitions

FOUNDATIONTM Fieldbus

The parameters not described in FF-891 or FF­903 are described in the following table. This
table also includes some parameters defined
in FF-891 or FF-903, but are redefined for this
application. This table has the same definitions

Par am ete r M n e m o nic

ACCESS_MODE S Unsigned8 S 1 See Table 6-8 0 Enumer ated Y es

ANALY ZER_HW_VERSION S Octet String S 30 none Read Only

ANALY ZER_OPTS S Unsigned8 S 1 See Table 6-7 Bit String Read Only

ANALY ZER_SW_VERSION S Octet String S 30 none Read Only

CAL_CONSTA NT_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_SPA N_DA TE_n S Date-(11) D 7 0 O/S Note 5-4 Y es

CAL_SPAN_INTERV AL_n S Unsigned16 S 2 0-999 0 Hour s O/S Note 5-4 Y es

CAL_SPAN_TOLERANCE_n S Floating Point S 4 0 - 100 10 % O/S Note 5-2 Y es

CAL_STATE S Unsigned16 D 2 See Table 6-2 0 Bit String

CAL_STEP S Unsigned8 D 1 See Table 6-3 0 Enumerated Note 5-2 Yes

CAL_UNIT_n S Unsigned16 S 2 ppm, %

CA L _Z ERO_DA TE_n S Da te- (1 1) D 7 0 O/ S Not e 5- 4 Y es

CAL_ZERO_INTERVA L_n S Uns igned16 S 2 0-999 0 Hours O/S Note 5-4 Y es

CAL_ZERO_SPAN_DA TE_n S Date-(11) D 7 0 O/S Note 5-4 Yes

CAL_ZERO_SPAN_INTERVA L_n S Unsigned16 S 2 0-999 0 Hours O/S Note 5-4 Y es
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_MAINTENA NCE S Unsigned32 D 4 See Table 6-10 0 Bit String Read Only

DETAILED_STATUS S Uns igned32 D 4 See Table 6-11 0 Bit String Read Only

DEV ICE_TIME S Date-(11) D 7 0 Yes

FUNCTION_CA LL S Unsigned8 D 1 See Table 6-12 0 Enumer ated 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

PRIMA R Y _V A L UE_ n R DS - 6 5 D 5 0 PV R

Obj

Type

Data Type /

Str uctu r e

Stor e Size V alid Range

as the one in FF-891, except that the columns
for Use/Model and Direction have been
omitted because all parameters are contained.
Refer to FF-891, section 5 – Block Parame­ters, for an explanation of this table.

Initial

Value

% Enumerated O/S Note 5-2

(see FF-903

sec t. 4.10 Units Codes)

Units M ode Other

Read Only

Read Only

Ran g e
Check

Tab. 2-3

Transducer Block Parameter Attribute Definitions

2-7

FOUNDATIONTM Fieldbus

2-3 Transducer Block Parameter Attribute Definitions

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184

10/2003

Parameter Mnemonic

PRIMARY_VA LUE_RANGE_n R DS-68 S 11 0- 100% PVR O/S Note 5-2

PRIMARY_VA LUE_TYPE_n S Unsigned16 S 2

SENSOR_A VG_CYCLES_n S Unsigned16 S 2 1 none Read Only

SENSOR_A VG_METHOD_n S Uns igned8 S Read Onl y1 0 Enumerated

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

SENSOR_TYPE_n S Unsigned16 S 2

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

SPA N_CAL_DATE_n S Date-(11) S 7 0 none Read Only

STATS_ATTEMPTS S Unsigned32 D 4 0-16777215 0 Read Only

STATS_FA ILURES 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

Obj

Type

Data Type /

Str uctu re

Store Size Valid Range

See section 4.1 in FF-

903

0: arithmetic

1: s liding

See FF- 903

sect. 4.3 Sensor Types

Initial

Value

65535

(other )

65535

(Non-Std)

Units Mode Other

Enumerated Read Only

Enumerated Read Only

Range
Check

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

2-4 Transducer Block Enumerations

2-4 Transducer Block Enumerations

2-4-1 Gas Control State

FOUNDATIONTM Fieldbus

Bit Numbe r

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 0x 0200 Span Gas Valve for Snsr2 opened
8 0x 0100 Sample Gas pump for Snsr2 running

FFValue of
GAS_CTRL_

Tab. 2-4

Gas Control State

During a running calibration procedure of a
sensor (see Table 2-5) the gas control states
are controlled by this procedure.

2-4-2 Calibration States

Bit Numbe r

15 0x 8000 running z ero calibration on Snsr1
14 0x 4000 running s pan calibration on Snsr1
13 0x 2000 purging changed gas on Snsr1
12 0x 1000 running c ross interference c alibration of Snsr2 onto Sns r1
11 0x 0800 running z ero calibration on Snsr2
10 0x 0400 running s pan calibration on Snsr2

9 0x 0200 purging changed gas on Snsr2
8 0x 0100 running cross interference calibration of Snsr1 onto Sns r2

FF-Value of
CAL_STATE

Description

Description

So it is refused to change this states by
operator during this running procedures.

Tab. 2-5

Calibration States

2-9

FOUNDATIONTM Fieldbus

2-4 Transducer Block Enumerations

2-4-3 Calibration Step Control

Value CAL_STEP – De scription

0 No Action

1 Zero Calibr ation Snsr1

2 Zero Calibr ation Snsr2

3 Zero Calibr ation 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 f actory Calibration of Snsr1

16 Load f actory Calibration of Snsr2

17 Load f actory Calibration of Snsr1+2

FOUNDATIONTM Fieldbus Communication Instruction Manual

ETC01184

10/2003

Tab. 2-6

Calibration Control Enumerations

To start a calibration procedure of a sensor is
only allowed if there is no procedure already
running on the same sensor (seeTable 2-5).

2-10

If we do not want to wait for finishing the already
running procedure we have first to cancel it
before starting the new procedure.