Rosemount Manual: BINOS 100 2M, BINOS 100 F and CAT 100 FOUNDATION Fieldbus Communication Software-Rev 3.0 | Rosemount Manuals & Guides

Instruction Manual

ETC00624
12/2001

Instruction Manual

FoundationTM Fieldbus
Communication Option for
BINOS 100 2M, BINOS 100 F & CAT 100
Software Revision 3

1st Edition 12/2001

www.EmersonProcess.com

FoundationTM Fieldbus 100 Series Instruction Manual

ETC00624

12/2001

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 12/2001

©

2001 by Emerson Process Management

Emerson Process Management
GmbH & Co. OHG

Industriestrasse 1
D-63594 Hasselroth
Germany
T [phone]
F [phone]
Internet: www.EmersonProcess.com

C

ONTENTS

Section 1 Foundation Fieldbus Technology 1–1

1.1 Overview ................................................................................................................. 1–1

1.2 Introduction ............................................................................................................. 1–2

1.2.1 Function Blocks................................................................................................. 1–2

1.2.2 Device Descriptions........................................................................................... 1–3

1.3 Instrument-Specific Functions 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–7

1.4.5 Function Block Scheduling ................................................................................ 1–8

1.5 References.............................................................................................................. 1–9

1.5.1 Fieldbus Foundation.......................................................................................... 1–9

Section 2 Transducer Block Specification 2–1

2.1 Parameter Descriptions........................................................................................... 2–2

2.2 Parameter Attribute Definitions................................................................................ 2–6

2.3 Parameter Access Methods .................................................................................... 2–9

2.4 Enumerations ........................................................................................................ 2–11

2.4.1 Calibration Check Status................................................................................. 2–11

2.4.2 Calibration Check Step Control ....................................................................... 2–11

2.4.3 Sensor Gas Type ............................................................................................ 2–12

2.4.4 Analyzer Options............................................................................................. 2–12

2.4.5 Calibration Options.......................................................................................... 2–12

2.4.6 Calibration Valve Control................................................................................. 2–13

Rosemount Analytical i

2.4.7 Detailed Status................................................................................................ 2–13

2.4.8 Measurement Options..................................................................................... 2–13

2.4.9 Pump Controller .............................................................................................. 2–14

2.4.10 Remote Exclusive Access ............................................................................... 2–14

2.4.11 Channel Assignments ..................................................................................... 2–14

2.5 Supported Block Errors ......................................................................................... 2–14

2.5.1 Transducer Block ............................................................................................ 2–14

2.5.2 Resource Block ............................................................................................... 2–15

Section 3 Analog Input (AI) Function Block 3–1

3.1 Simulation................................................................................................................ 3–3

3.2 Filtering....................................................................................................................3–4

3.3 Signal Conversion ................................................................................................... 3–4

3.4 Block Errors............................................................................................................. 3–5

3.5 Modes ..................................................................................................................... 3–6

3.6 Alarm Detection....................................................................................................... 3–6

3.7 Status Handling....................................................................................................... 3–7

3.8 Advanced Features ................................................................................................. 3–7

3.9 Application Information............................................................................................ 3–8

3.9.1 Application Example 1....................................................................................... 3–8

3.9.2 Application Example 2....................................................................................... 3–9

3.9.3 Application Example 3..................................................................................... 3–10

3.10 Troubleshooting..................................................................................................... 3–11

Section 4 Analog Output (AO) Function Block 4–1

4.1 Setting the Output ................................................................................................... 4–2

4.2 Setpoint Selection and Limiting ............................................................................... 4–3

4.3 Conversion and Status Calculation ......................................................................... 4–3

4.4 Simulation................................................................................................................ 4–4

4.5 Action on Fault Detection ........................................................................................ 4–4

4.6 Block Errors............................................................................................................. 4–4

4.7 Modes ..................................................................................................................... 4–5

ii Rosemount Analytical

4.8 Status Handling....................................................................................................... 4–5

Section 5 Input Selector (ISEL) Function Block 5–1

5.1 Block Errors............................................................................................................. 5–3

5.2 Modes ..................................................................................................................... 5–4

5.3 Alarm Detection....................................................................................................... 5–4

5.4 Block Execution....................................................................................................... 5–4

5.5 Status Handling....................................................................................................... 5–5

5.6 Application Information............................................................................................ 5–5

5.7 Troubleshooting....................................................................................................... 5–7

Section 6 Proportional / Integral / Derivative (PID) Function Block 6–1

6.1 Setpoint Selection and Limiting ............................................................................... 6–5

6.2 Filtering....................................................................................................................6–6

6.3 Feedforward Calculation .........................................................................................6–6

6.4 Tracking .................................................................................................................. 6–6

6.5 Output Selection and Limiting.................................................................................. 6–6

6.6 Bumpless Transfer and Setpoint Tracking .............................................................. 6–7

6.7 PID Equation Structures.......................................................................................... 6–7

6.8 Reverse and Direct Action....................................................................................... 6–7

6.9 Reset Limiting.......................................................................................................... 6–8

6.10 Block Errors............................................................................................................. 6–8

6.11 Modes ..................................................................................................................... 6–8

6.12 Alarm Detection....................................................................................................... 6–9

6.13 Status Handling..................................................................................................... 6–10

6.14 Application Information.......................................................................................... 6–10

6.15 Closed Loop Control.............................................................................................. 6–10

6.15.1 Application Example 1..................................................................................... 6–12

6.15.2 Application Example 2..................................................................................... 6–13

6.15.3 Application Example 3..................................................................................... 6–14

Rosemount Analytical iii

6.15.4 Application Example 4..................................................................................... 6–15

6.16 Troubleshooting..................................................................................................... 6–16

iv Rosemount Analytical

F

IGURES

Figure 1-1. Function Block Internal Structure...................................................................... 1–3

Figure 1-2. Single Link Fieldbus Network ............................................................................ 1–5

Figure 1-3. Scheduled Data Transfer .................................................................................. 1–7

Figure 1-4. Unscheduled Data Transfer .............................................................................. 1–7

Figure 1-5. Example of Link Schedule................................................................................. 1–8

Figure 2-1. Parameter Access........................................................................................... 2–10

Figure 2-2. Calibration Check State Diagram.................................................................... 2–11

Figure 3-1. Analog Input Function Block Schematic............................................................ 3–3

Figure 3-2. Analog Input Function Block Timing Diagram ................................................... 3–4

Figure 4-1. Analog Output Function Block Schematic ......................................................... 4–2

Figure 4-2. Analog Output Function Block Timing Diagram ................................................ 4–3

Figure 5-1. Input Selector Function Block Schematic.......................................................... 5–3

Figure 6-1. PID Function Block Schematic.......................................................................... 6–5

Figure 6-2. PID Function Block Setpoint Selection.............................................................. 6–6

T

ABLES

Table 2-1. Parameter Descriptions...................................................................................... 2–2

Table 2-2. Parameter Attribute Definitions .......................................................................... 2–6

Table 2-3. Calibration Check Status Enumerations........................................................... 2–11

Table 2-4. Calibration Check Step Control Enumerations................................................. 2–11

Table 2-5. Sensor Gas Type ............................................................................................. 2–12

Table 2-6. Analyzer Options.............................................................................................. 2–12

Table 2-7. Calibration Options........................................................................................... 2–12

Table 2-8. Calibration Valve Control ................................................................................. 2–13

Table 2-9. Detailed Status................................................................................................. 2–13

Table 2-10. Measurement Options .................................................................................... 2–13

Table 2-11. Pump Controller ............................................................................................. 2–14

Table 2-12. Remote Exclusive Access .............................................................................. 2–14

Table 2-13. I/O Channel Assignments (AI Blocks) ............................................................ 2–14

Table 2-14. I/O Channel Assignments (AO Blocks) .......................................................... 2–14

Rosemount Analytical v

Table 3-1. Definitions of Analog Input Function Block System Parameters......................... 3–1

Table 3-2. Block Error Conditions .......................................................................................3–5

Table 3-3. Alarm Priorities................................................................................................... 3–7

Table 3-4. Troubleshooting AI Block ................................................................................. 3–11

Table 4-1. Analog Output Function Block System Parameters. .......................................... 4–1

Table 5-1. Input Selector Function Block System Parameters ............................................ 5–1

Table 5-2. Block Error Conditions .......................................................................................5–3

Table 5-3. Alarm Priorities................................................................................................... 5–4

Table 5-4. Troubleshooting ISEL Block. .............................................................................. 5–7

Table 6-1. PID Function Block System Parameters ............................................................ 6–2

Table 6-2. Block Error Conditions .......................................................................................6–8

Table 6-3. Alarm Priorities................................................................................................. 6–10

Table 6-4. Troubleshooting for PID ................................................................................... 6–16

vi Rosemount Analytical

1 F

OUNDATION FIELDBUS TECHNOLOGY

1.1

F
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 F
an enabling technology.

Fisher-Rosemount 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

VERVIEW

O

OUNDATION

and input/output functions to field devices.

Fieldbus is an all digital, serial, two-way communication system that

OUNDATION

Fieldbus

♦ 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.

Rosemount Analytical Foundation Fieldbus 1–1

Foundation Fieldbus Technology

1.2

NTRODUCTION

I

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.2.1 Function Blocks

Function blocks within the Fieldbus device perform the various functions required for
process control. Because each system is different, the mix and configuration of
functions are different. Therefore, the Fieldbus F

OUNDATION

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 F
parameters used in all function blocks called universal parameters. The F

OUNDATION

has established the function blocks by defining a small set of

OUNDATION

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 F

OUNDATION

specifications and definitions allow vendors to add their own

parameters by importing and subclassing specified classes. This approach permits
extending function block definitions as new requirements are discovered and as
technology advances.

Figure 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 Foundation Fieldbus Rosemount Analytical

Foundation Fieldbus Technology

Input Events Execution Control Output Events

Input Parameter

Linkages

Input
Snap

Status Status

Figure 1-1. Function Block Internal Structure

Processing

Algorithm

Output

Snap

Output Parameter

Linkages

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.

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.

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

Rosemount Analytical Foundation Fieldbus 1–3

Foundation Fieldbus Technology

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

1.3.1 Resource Blocks

1.3.2 Transducer Blocks

NSTRUMENT-SPECIFIC FUNCTIONS BLOCKS

I

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.

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

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

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.

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 Foundation Fieldbus Rosemount Analytical

Foundation Fieldbus Technology

1.4

ETWORK COMMUNICATION

N

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

(Link Active Scheduler)

LAS

Link Master

Basic Devices and/or Link Master Devices

Figure 1-2. Single Link Fieldbus Network

Fieldbus Link

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

Rosemount Analytical Foundation Fieldbus 1–5

Foundation Fieldbus Technology

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 Fisher-Rosemount 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 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.

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

• Client/Server: This type of reporting is used for request/response exchanges
between pairs of devices. Like Report Distribution reporting, the transfers are queued,
unscheduled, and prioritized. Queued means the messages are sent and received in
the order submitted for 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.

Figure 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 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.”

1–6 Foundation Fieldbus Rosemount Analytical

LAS

Schedule

CD(X,A)

Foundation Fieldbus Technology

X

Y

Z

Figure 1-3. Scheduled Data Transfer

DT(A)

AB CA D A

PS PS P S

Device X Device Y Device Z

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

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

PT(Z)

DT(M)

AB CA DA

MM

PS PS PS

Device X Device Y Device Z

Figure 1-4. Unscheduled Data Transfer

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

Rosemount Analytical Foundation Fieldbus 1–7

Foundation Fieldbus Technology

1.4.5 Function Block Scheduling

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

Device 1

Scheduled

Communication

Unscheduled

Communication

Device 2

Macrocycle Start Time

Offset from macrocycle Start

time = 0 for AI Execution

AI

AI

Offset from macrocycle Start

time = 20 for AI Communication

Offset from macrocycle Start

time = 30 for PID Execution

AO AOPID

Offset from macrocycle Start

time = 50 for AO Execution

Sequence Repeats

PID

Macrocycle

Figure 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
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.

1–8 Foundation Fieldbus Rosemount Analytical

Foundation Fieldbus Technology

1.5

The following Fieldbus F

EFERENCES

R

OUNDATION

documents should be used to gain an

understanding of Fieldbus, and are referenced wherever appropriate in the document:

Document Number Document Title

FF-890

FF-891

FF-902

FF-903

RMD-D9800039

Fieldbus Foundation™ Fieldbus Specification —
Function Block Application Process – Part 1
Fieldbus Foundation™ Fieldbus Specification —
Function Block Application Process – Part 2
Fieldbus Foundation™ Fieldbus Specification —
Transducer Block Application Process – Part 1
Fieldbus Foundation™ Fieldbus Specification —
Transducer Block Application Process – Part 2
Rosemount Common Practice Resource Block Specification

1.5.1 Fieldbus Foundation

The Fieldbus Foundation is the leading organization
dedicated to a single international, interoperable Fieldbus
standard. Established in September 1994 by a merger of WorldFIP North America and
the Interoperable 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
initiatives. The foundation's technology - F

OUNDATION

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, F

OUNDATION

Fieldbus is neither owned by any individual company, or controlled by a single nation or
regulatory body. 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 F

OUNDATION

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:

9390 Research Blvd., Suite II-250 • Austin, Texas 78759-9780 USA

Tel: [phone] • Fax: [phone]

Email: [e-mail]

Internet: www.fieldbus.org

Rosemount Analytical Foundation Fieldbus 1–9

2 T

The Transducer Block Specification provides the information necessary to interface the
CAT100 or the BINOS 100 2M to the Fieldbus. The data structures should be used for
transferring Fieldbus information between the analyzer’s Object Dictionary and other hosts
and devices on Fieldbus.

Two tables are used to describe the analyzer parameters. The Parameter Descriptions table
defines the relative index value used to reference the parameter in the analyzer Transducer
Block Object Dictionary and the mnemonic used to reference the parameter, as well as the
View(s )in which they are contained. This table also 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. The I/O channel assignments
and their status values are shown in the Channel Assignments section.

Finally the default values for parameters are defined. Static parameters will be set to the
default value when a restart with defaults is invoked in the Resource block. 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.

RANSDUCER BLOCK SPECIFICATION

Rosemount Analytical Foundation Fieldbus 2–1

Transducer Block

ARAMETER DESCRIPTIONS

2.1

P

This table gives a description of all the parameters or gives the location in the Fieldbus specifications where the description
can be found. Parameter access is described in FF-890.

Table 2-1. Parameter Descriptions

Relative

Index

Parameter Mnemonic Description View1View2View3View

4-1

63 AIR_PRESSURE The current air pressure (in hPa): if pressure sensor is installed this is a dynamic

variable; if no pressure sensor is installed we have to input the current value. If
we use remote pressure we have to input via AO block. There we have to select
appropriate CHANNEL assignment.

4 ALERT_KEY See FF-891 section 5.3. 1

64 ANALYZER_OPTS The installed analyzer options 2

66 ANALYZER_SERIAL_NUMBER The analyzer serial number 10

67 ANALYZER_SW_VERSION The version number of the analyzer software 32

8 BLOCK_ALM See FF-891 section 5.3.

6 BLOCK_ERR See FF-891 section 5.3. 2 2

21 CAL_CONSTANT_1 The zero correction offset (calculated by zero calibration). 4

42 CAL_CONSTANT_2 The zero correction offset (calculated by zero calibration). 4

59 CAL_GAS_TIME Purge delay time (in secs) for calibration gas supply 2

18 CAL_MINIMUM_SPAN_1 See FF-903 section 3.3. In the BINOS, a calibration is used for checking the

analyzer only. The calculation of the Primary Value is not effected.

39 CAL_MINIMUM_SPAN_2 See FF-903 section 3.3. In the BINOS, a calibration is used for checking the

analyzer only. The calculation of the Primary Value is not effected.

58 CAL_OPTS The calibration options. 1

16 CAL_POINT_HI_1 See FF-903 section 3.3 4

37 CAL_POINT_HI_2 See FF-903 section 3.3 4

17 CAL_POINT_LO_1 See FF-903 section 3.3 4

55

4

4

View

4-2

View

4-3

Rosemount Analytical Foundation Fieldbus 2–2

Transducer Block

Relative

Index

Parameter Mnemonic Description View1View2View3View

4-1

38 CAL_POINT_LO_2 See FF-903 section 3.3 4

22 CAL_PRESSURE_FACTOR_1 The factor of pressure influence onto concentration measurement. Relates

43 CAL_PRESSURE_FACTOR_2 The factor of pressure influence onto concentration measurement. Relates

20 CAL_SLOPE_1 This parameter represents the span correction factor (calculated by span

41 CAL_SLOPE_2 This parameter represents the span correction factor (calculated by span

56 CAL_STATE This parameter represents the present state the calibration check cycle is in.

57 CAL_STEP This parameter is used to initiate a zero or span calibration. See table 2 for the

19 CAL_UNIT_1 See FF-903 section 3.3. 2

40 CAL_UNIT_2 See FF-903 section 3.3. 2

65 CAL_VALVE_STATE The state of the calibration gas valves. 1

60 CAL_ZERO_INTERVAL The time interval (in hours) for automatic zero calibrations of both channels. 2

61 CAL_ZERO_SPAN_INTERVAL The time interval (in hours) for automatic zero & span calibrations of both

12 COLLECTION_DIRECTORY See FF-891 section 5.3.

62 DETAILED_STATUS This is a bit-enumerated value used to communicate the status of the BINOS

70 MEASUREMENT_OPTS The different kind of options for the measurement. 1

5 MODE_BLK See FF-891 section 5.3. 4 4

14 PRIMARY_VALUE_1 See FF-903 section 3.3. 5 5

35 PRIMARY_VALUE_2 See FF-903 section 3.3. 5 5

15 PRIMARY_VALUE_RANGE_1 See FF-903 section 3.3. 11

36 PRIMARY_VALUE_RANGE_2 See FF-903 section 3.3. 11

pressure to pressure factor.

pressure to pressure factor.

calibration).

calibration).

11

Refer to table 1 for the definition of states.

definition of states.

channels.

(This is similar in nature to the command 48 status bits in HART). See Table 2-9.

4

4

4

4

1

4

View

4-2

2

View

4-3

Rosemount Analytical

Foundation Fieldbus 2–3

Transducer Block

Relative

Index

Parameter Mnemonic Description View1View2View3View

13 PRIMARY_VALUE_TYPE_1 See FF-903 section 3.3 and 4.1. 2

34 PRIMARY_VALUE_TYPE_2 See FF-903 section 3.3 and 4.1. 2

71 PUMP_CTRL The instance of the device which controls the optional internal pump. 1

69 REMOTE_EXCLUSIVE This parameter disallows to switch into the local operator interface mode

(switching in local operator interface mode would disable to change a parameter
via FFBUS). After a timeout period without writing to parameters the exclusive
mode will be disabled again.

68 REMOTE_SECURITY This parameter controls access to the special service transducer block

parameters. A special access code must be entered to enable changes to this
static service parameters. After a timeout period, the parameter will be reset to 0
and access will be restricted. While service parameter access is enabled,
parameters may not be changed via the local operator interface on the field
device.

74 SENSOR_CAL_DATE See FF-903 section 3.3. 7

73 SENSOR_CAL_LOC See FF-903 section 3.3. 32

72 SENSOR_CAL_METHOD See FF-903 sections 3.3 and 4.5. 1

75 SENSOR_CAL_WHO See FF-903 section 3.3. 32

29 SENSOR_CROSS_INTF_OFFSET_1 The zero correction of cross interference compensation. 4

50 SENSOR_CROSS_INTF_OFFSET_2 The zero correction of cross interference compensation. 4

55 SENSOR_DETECTOR_SEL This parameter assigns compensation defaults for installed detector type. 1

25 SENSOR_FILTER_VALUE_1 The t90 response time (in secs) for gas change. 4

46 SENSOR_FILTER_VALUE_2 The t90 response time (in secs) for gas change. 4 4

33 SENSOR_GAS_TYPE_1 The measurement type and assigns compensation defaults for gas type. 1

54 SENSOR_GAS_TYPE_2 The measurement type and assigns compensation defaults for gas type. 1

24 SENSOR_ID_1 The id description of the channel sensor. 20

45 SENSOR_ID_2 The id description of the channel sensor. 20 20

32 SENSOR_NOISE_REDUCTION_1 This parameter represents the value for dynamic noise reduction. 4

53 SENSOR_NOISE_REDUCTION_2 This parameter represents the value for dynamic noise reduction. 4

4-1

View

4-2

1

2

View

4-3

Rosemount Analytical Foundation Fieldbus 2–4

Transducer Block

Relative

Index

Parameter Mnemonic Description View1View2View3View

31 SENSOR_PRESSURE_FACTOR_1 This parameter represents the span correction of pressure compensation. 4

52 SENSOR_PRESSURE_FACTOR_2 This parameter represents the span correction of pressure compensation. 4

26 SENSOR_RAW_CONCENTRATION_1 This parameter represents the raw value of A/D-Conversion of measurement

channel.

47 SENSOR_RAW_CONCENTRATION_2 This parameter represents the raw value of A/D-Conversion of measurement

channel.

27 SENSOR_RAW_TEMPERATURE_1 This parameter represents the raw value of A/D-Conversion of temperature

measurement.

48 SENSOR_RAW_TEMPERATURE_2 This parameter represents the raw value of A/D-Conversion of temperature

measurement.

30 SENSOR_TEMP_FACTOR_1 This parameter represents the span correction of temperature compensation. 4

51 SENSOR_TEMP_FACTOR_2 This parameter represents the span correction of temperature compensation. 4

28 SENSOR_TEMP_OFFSET_1 This parameter represents the zero correction of temperature compensation. 4

49 SENSOR_TEMP_OFFSET_2 This parameter represents the zero correction of temperature compensation. 4

23 SENSOR_TYPE_1 See FF-903 section 3.3 and 4.3. 2

44 SENSOR_TYPE_2 See FF-903 section 3.3 and 4.3. 22

1 ST_REV See FF-891 section 5.3. 222222

76 STATS_ATTEMPTS Total number of messages sent to the transducer a/d board. 4

77 STATS_FAILURES Total number of failed a/d board message attempts. 4

78 STATS_TIMEOUTS Total number of timed out a/d board message attempts. 4

3 STRATEGY See FF-891 section 5.3. 2

2 TAG_DESC See FF-891 section 5.3.

9 TRANSDUCER_DIRECTORY See FF-903 section 3.3.

10 TRANSDUCER_TYPE See FF-903 sections 3.3. 2222

7 UPDATE_EVT See FF-891 section 5.3.

11 XD_ERROR See Table 2-9 and FF-903 section 3.3. 1 1

4

4

4

4

4-1

View

4-2

View

4-3

Rosemount Analytical

Foundation Fieldbus 2–5

Transducer Block

ARAMETER ATTRIBUTE DEFINITIONS

2.2

P

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 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 Parameters), for a further explanation of this table.

Table 2-2. Parameter Attribute Definitions

Parameter Mnemonic Obj

AIR_PRESSURE S DS-65 D/S 45 800.0-1300.0 1013 hPa Note 1 Note 5

ANALYZER_OPTS S Unsigned16 S 2 Bit String O/S Note 2

ANALYZER_SERIAL_NUMBER S Octet String S 10 N/A O/S Note 2

ANALYZER_SW_VERSION S Octet String N 32 N/A Read Only

CAL_CONSTANT_n S Floating Point D 4 Read Only

CAL_GAS_TIME S Unsigned16 S 2 Sec Note 3 Yes

CAL_OPTS S Unsigned8 S 1 Bit String Note 3 Yes

CAL_POINT_HI_n S Floating Point S 4 Note 3 Yes

CAL_POINT_LO_n S Floating Point S 4 Note 3 Yes

CAL_PRESSURE_FACTOR_n S Floating Point D 4 Read Only

CAL_SLOPE_n S Floating Point D 4 Read Only

CAL_STATE S Unsigned8 D 1 See Table 2-3 0 Enumerated Read Only

CAL_STEP S Unsigned8 D/S 1 0 Enumerated Note 3 Yes

CAL_UNIT_n S Unsigned16 S 2 See FF-903 section

CAL_VALVE_STATE S Unsigned8 D/S 1 Bit String Note 3 Yes

CAL_ZERO_INTERVAL S Unsigned16 S 2 0-399 Hours Note 3 Yes

CAL_ZERO_SPAN_INTERVAL S Unsigned16 S 2 0-399 Hours Note 3 Yes

Data Type/Structure Store Size Valid Range Initial Value Units Mode Other Range

Type

Enumerated O/S Note 2

4.10 Units Codes

Check

Rosemount Analytical Foundation Fieldbus 2–6