FieldQ Valve Actuator - Fluid Control Services

fcs.web.com

FieldQ Valve Actuator - Fluid Control Services

Reference manual

DOC.RM.QM34.1 Rev: A

Sept. 2003

FieldQ Valve Actuator

Foundation Fieldbus Function Module

www.FieldQ.com

TM


Page 2

TM

1.0 Module Description 3

1.1 FieldQTM FOUNDATIONT Fieldbus Module .............. 3

1.2 FOUNDATION Fieldbus Communication .................... 4

1.3 Device Description and Methods ................................ 4

1.4 Node Address ............................................................. 4

1.5 FOUNDATION Fieldbus Function Blocks ................... 4

1.5.1 Resource Block ........................................................... 4

1.5.2 Transducer Block - Control ......................................... 5

1.5.3 Transducer Block - Auxiliary I/O .................................. 5

1.5.4 Analog Input (AI) Block ............................................... 5

1.5.5 Discrete Output (DO) Block ........................................ 5

1.5.6 Discrete Input (DI) Block ............................................. 5

1.6 Related Information .................................................... 5

1.6.1 FOUNDATION Fieldbus Installation and Wiring

Guidelines ................................................................... 5

1.6.2 Other Related Information .......................................... 5

1.7 Specifications, FOUNDATION Fieldbus Hardware ..... 5

2 Installation 6

2.1 Introduction ................................................................. 6

2.1.1 Before starting ............................................................ 6

2.2 Pneumatic connections .............................................. 6

2.2.1 Single acting (spring return) or Double acting actuator

(see fig 2.3) : ............................................................... 6

2.3 Electric Connections ................................................... 7

2.3.1 Electrical Input, Fieldbus Interface .............................. 7

2.3.2 Wiring dimensions ...................................................... 7

2.3.3 Procedure ................................................................... 7

2.3.4 Tools ............................................................................ 7

2.4 Quick Connect Option ................................................. 8

3 Initial Setup 9

3.1 Addressing .................................................................. 9

3.2 Quick Setup ................................................................ 9

3.3 Initialization ................................................................. 9

4 Detailed Configuration 10

4.1 Resource Block ......................................................... 10

4.1.1 Identification .............................................................. 10

4.1.2 Process ..................................................................... 11

4.1.3 Alarms ....................................................................... 12

4.1.4 Options ..................................................................... 12

4.1.5 PlantWeb Alerts ........................................................ 14

4.1.5.1 Conditions ................................................................. 14

4.1.5.2 Failed Alerts .............................................................. 15

4.1.5.3 Maintenance Alerts ................................................... 15

4.1.6 Advisory Alarms ........................................................ 16

4.1.7 Recommended Actions for PlantWeb Alarms .......... 16

4.2 Control Transducer Block .......................................... 17

4.2.1 Mode ......................................................................... 17

4.2.3 Events ....................................................................... 18

4.2.2 Valve/Actuator Identification ..................................... 18

4.2.3.1 Event Value ............................................................... 18

4.2.3.2 Event Limits .............................................................. 18

4.2.3.3 Event Filter ................................................................ 18

4.2.3.4 Event Options ........................................................... 18

4.2.3.5 Averages ................................................................... 19

4.2.3.6 Cycle Counters ......................................................... 19

4.2.3.7 Time in Position ........................................................ 20

4.2.3.8 Break and Travel Times ............................................. 20

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Contents

4.2.4 Initialization ............................................................... 22

4.2.4.1 Implementation of the device driver in the host system.

22

4.2.4.2 Device address. ........................................................ 22

4.2.4.3 Initialization - Using Bus Command

(digital mode) ............................................................ 22

4.2.4.4 Initialization - Using Local Buttons

(manual mode) .......................................................... 23

4.2.4.3 Initialization Commands ........................................... 23

4.2.4.4 Initialization Status .................................................... 23

4.2.5.1 If the read out on the button board is reversed or,

Readjustment of the exact positions is needed;

(manual mode) .......................................................... 24

4.2.5.2 If auto initialization routine is not completed (Status

LED is flashing)

(manual mode & digital mode) .................................. 24

4.2.5.3 Manual setting of feedback switches routine:

(manual mode) .......................................................... 24

4.2.6 Recognizing LED

(digital mode) ............................................................ 24

4.2.7 Implementation in the process. ................................. 24

4.2.8 Check functioning ..................................................... 24

4.2.9 Local Manual Control (option) .................................. 24

4.3 Auxiliary I/O Transducer Block .................................. 25

4.3.1 Mode ......................................................................... 25

4.3.2 Analog Inputs ............................................................ 26

4.4 Function Block Default Instantiation Mapping .......... 27

4.5 Channel Mapping ..................................................... 27

4.5.1 Chan 2 - Output Command Readback ..................... 27

4.5.2 Chan 3 - Discrete Output Command ........................ 27

4.5.3 Chan 4 - Discrete Output Command Readback ....... 27

4.5.4 Chan 7 & 8 - Limit Switch Input Channels ................ 27

4.5.5 Chan 9 - Temperature ............................................... 27

4.5.6 Chan 24 & 25 - Auxiliary Analog Inputs .................... 27

5 Operations and Maintenance 28

5.1 Fault State ................................................................. 28

5.2 Restart Method ......................................................... 28

5.3 Restarting the Module .............................................. 28

5.3.1 Software Restart ....................................................... 28

5.3.2 Restart Results ......................................................... 29

5.4 Status/Readback ...................................................... 29

5.5 Status Sub-index ...................................................... 29

5.5.1 Command/Position Parameters ................................ 29

5.5.2 Other Parameters ..................................................... 29

6 Block Descriptions 30

6.1 What is a Block? ....................................................... 30

6.2 Resource Block ......................................................... 31

6.2.1 Parameter List ........................................................... 31

6.2.2 Parameter Name to Label Lookup Table .................. 32

6.2.3 Resource Block Parameters (Alphabetical by Label) 33

6.3 Control Transducer Block .......................................... 46

6.3.2 Parameter Name to Label Lookup Table .................. 47

6.3.3 Control Transducer Block Parameters ...................... 48

6.4 Auxiliary I/O Transducer Block .................................. 61

6.4.1 Parameter List ........................................................... 61

6.4.2 Parameter Name to Label Lookup Table .................. 61

6.4.3 Auxiliary I/O Transducer Block Parameters .............. 62


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

1.0 Module Description

1.1 FieldQTM FOUNDATIONT Fieldbus

Module

This manual contains installation, operating, and

maintenance information for the FieldQ ®

FOUNDATION TM FieldBus module (Figure 1). This

manual describes the functionality of revision 1 of the

module.

Only qualified personnel should install, operate, and

maintain this module. If you have any questions

concerning these instructions or for information not

contained in this instruction manual, contact your

local Valve Automation sales office or sales representative

for more information.

The FieldQ module is an interoperable, processcontrolling,

communicating, microprocessor-based,

module. In addition to its primary function of controlling

the position of the valve, the FieldQ module,

using FOUNDATION fieldbus communications

protocol, gives easy access to information critical to

process operation, as well as process control. You

can gain information from the principal component of

the process, the control valve itself, by using a

personal computer or operator’s console within the

control room.

Fig 1.1 FieldQ Foundationr Fieldbus Module

Using a compatible fieldbus configuration device, you

can obtain information about the health of the module

and the actuator and valve control elements. You can

also obtain asset information about the module. You

can set input and output configuration parameters.

Using the FOUNDATION fieldbus protocol, information

from the module can be readily integrated into a

control system.

The FieldQ module is an assembly in an IP65/NEMA

4 enclosure that provides input and output signals to

control and monitor the FieldQ actuator. The module

is self-contained providing control and position

feedback via the Fieldbus interface.

Figure 2 provides a cutaway view of the module with

key connection points labeled. Connect to the module

by removing the cover, inserting the wiring through

the Electrical Access ports and connecting each wire

to the proper location on the terminal board. More

information about connecting a module can be found

in section 2.1.

After connecting the module, set the limit switches for

the module by running the initialization procedure

described in section 4.2.4.

Fig 1.2 Cutaway of the FF Module

TM

Page 3


Page 4

TM

1.2 FOUNDATION Fieldbus Communication

The FieldQ FF module uses the FOUNDATIONT

fieldbus protocol to communicate with other field

devices and the host system. FOUNDATION Fieldbus

is an all-digital, serial, two-way communication

system, which interconnects field equipment such as

transmitters, valve controllers, and process controllers.

Fieldbus is a local-area network (LAN) for

devices used in both process and manufacturing

automation with built-in capability to distribute the

control application across the network.

The fieldbus environment is the base level group of

digital networks in the hierarchy of plant networks.

The fieldbus retains the desirable features of analog

systems such as:

A standardized physical interface to the wire

Bus-powered devices on a single wire pair

Intrinsic safety options

In addition, use of FOUNDATION fieldbus enables:

Increased capabilities due to full digital communications

Reduced wiring and wire terminations due to

multiple devices on a single pair of wires

Increased selection of suppliers due to

interoperability

Reduced loading on control room equipment

available by distributing control and input/output

functions to field devices

Speed options for process control and manufacturing

applications

For more information on the operation of the FOUN-

DATION fieldbus, refer to your DeltaVT documentation

and the FOUNDATION fieldbus specifications.

1.3 Device Description and Methods

This manual describes device setup using the Device

Descriptions (DD) specified by the FOUNDATION

fieldbus protocol. Parameter access and methods are

also described in this manual. FOUNDATION fieldbus

uses the DD, Function Blocks, and a Capabilities File

to achieve interoperability between the module and

fieldbus components from other manufacturers in the

control systems including hosts and other devices.

The DD provides information to describe the data

interface to the device while the Capabilities File

provides information about the device to enable the

creation of a control strategy without a physical

device (off-line configuration).

For fieldbus devices, in addition to providing parameter

definitions and other information required by the

control system to communicate with the device, the

DD may also include methods. Methods can be used

for a variety of functions including remote restarting

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

of the switchbox. Methods are a predetermined

sequence of steps using a structured programming

language and the interface definition for the module.

How the method prompts and how messages appear

is determined by the host system. For information on

using methods on the host system, see Appendix E

and the appropriate host system documentation.

1.4 Node Address

When the FieldQ, with the FF module, is shipped, it

does not have a working address assigned. When the

module is connected to a control system, the configuration

device or host will recognize the module and a

working address will be assigned. Once the module

has a working address, the device can be configured.

Use the host system to commission the module and

assign it a working address. For information on using

the host system for device commissioning and

assigning addresses, see the appropriate host

system documentation.

1.5 FOUNDATION Fieldbus Function Blocks

Function blocks, within a fieldbus device, perform the

various functions required for process control, such

as process variable input, output, and control functions

such 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. Then, function blocks can be combined into

a process that can be implemented within a single

device or in multiple devices via the fieldbus network.

The following function blocks are implemented in the

FieldQ module.

Resource Block (RB)

Transducer Block for Control (TB-C)

Transducer Block for Auxiliary I/O (TB-A)

Analog Input (AI) Function Block

Discrete Output (DO) Function Block

Discrete Input (DI) Function Block

Function Block parameters and usage is described in

the DeltaV Documentation. Please refer to this

documentation for detailed information on function

blocks.

1.5.1 Resource Block

The Resource Block contains diagnostic, hardware

and electronics information. There are no linkable

inputs or outputs to the Resource Block.


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

1.5.2 Transducer Block - Control

The Control Transducer Block is the primary interface

to the control function of the device. This Transducer

Block contains all the parameters necessary to

provide the control function and associated diagnostics

of the device.

1.5.3 Transducer Block - Auxiliary I/O

The Auxiliary Transducer Block is the primary interface

to the auxiliary I/O available in the device. This

Transducer Block contains all the parameters necessary

to control and/or monitor the auxiliary I/O including

diagnostics associated with the auxiliary I/O.

1.5.4 Analog Input (AI) Block

The Analog Input (AI) function block processes field

device measurements and makes this data available

to other function blocks. The output value from the AI

block is in engineering units and contains a status

indicating the quality of the measurement.

The AI block supports alarming, signal scaling, signal

filtering, signal status calculation, mode control, and

simulation. The AI block is widely used for scaling

functionality.

1.5.5 Discrete Output (DO) Block

The Discrete Output (DO) function block processes a

discrete setpoint then outputs the setpoint to a

specified I/O channel to produce an output signal.

The DO function block supports mode control, output

tracking, and simulation. There is no process alarm

detection in the block. In operation, the DO function

block determines its setpoint, sets the output, and, as

an option, checks a readback signal from the field

device to confirm the physical output operation.

1.5.6 Discrete Input (DI) Block

The Discrete Input (DI) function block processes a

single discrete input from a field device and makes it

available to other function blocks. The DI function

block supports mode control, signal status propagation,

and simulation.

1.6 Related Information

1.6.1 FOUNDATION Fieldbus Installation and

Wiring Guidelines

FOUNDATIONT Fieldbus Technical Overview (available

from the Fieldbus Foundation)

1.6.2 Other Related Information

Other documents containing information related to

the FieldQ module include:

1.604.02 Function module data sheet

1.604.021 Diagnostics data sheet

DOC.FM.QM34.1 Quick Reference Guide Function

module with FOUNDATION fieldbus

1.7 Specifications, FOUNDATION Fieldbus

Hardware

Electrical Entry

4 x M20 (Option: 1/2” NPT)

Electrical Input, Fieldbus Interface

Voltage Level : 9 to 32 volts

Nominal Current : 21 mA, maximum

Reverse Polarity : Unit is not polarity sensitive

Protection

Termination : Bus must be properly terminated

per ISA SP50 guidelines

Function Blocks Available

Analog Input (AI)

Discrete Output (DO)

Discrete Input (DI)

Digital Communication Protocol

Manchester-encoded digital signal that conforms to

IEC 1158-2 and ISA 50.02

Operating Ambient Temperature Limits

-20°C to +50° C (-4° F to 122° F)

Electrical connections

Terminal Block

Optional quick connectors

Housing

Material : Aluminum Alloy

Finish : Epoxy primer and two

component polyuethane top

coating

Enclosure : IP65 / NEMA 4

TM

Page 5


Page 6

TM

2 Installation

2.1 Introduction

The FieldQ module is a two-wire device drawing all

its required power from the bus. Refer to your site

planning guide for proper wire types, termination,

length, and other specifications for a fieldbus loop. In

this manual, the following sections provide information

on the terminal board within the module, how to

connect the required signals to the terminal board,

and options for setting the switches on the FOUNDA-

TION fieldbus interface board.

2.1.1 Before starting

* Be sure that the actuator is correctly mounted

before connecting air supply and electrical wiring

(see Installation & Operation Manual FieldQ Valve

Actuator)

* Check the module label for the right execution

(see fig. 2.1)

* Check the type of actuator: single or double acting

(see fig. 2.2)

OK

OK

Fig. 2.1 Check proper mounting before connecting air

supply and electrical wiring.

OK

OK

Function Module

Label = QM34...

Actuator

Label = QS xxxx

QS xxxx = Single acting

(Spring Return)

QD xxxx = Double acting

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

2.2 Pneumatic connections

WARNINGS

* The actuator/valve combination can move

after connecting the air supply.

* The function module must be mounted

properly before connecting the air supply.

Check the maximum pressure Pmax = 8bar/

116Psi

Operating media :

* Air or inert gasses.

* Air quality according ISO 8573-1 7-5-4.

* Dew point 10K bellow operating temperature.

* For subzero applications take appropriate

measures.

2.2.1 Single acting (spring return) or Double

acting actuator (see fig 2.3) :

1 Remove the plug from the air supply (Ps).

2 Connect air supply to port (Ps).

Double

acting

function

module cover

Single

acting

Fig. 2.2 Identification Fig. 2.3 Pneumatic connections

Ps (1/4”BSP or 1/”NPT)

Ps (1/4”BSP or 1/”NPT)

Ra

Rb

Rb


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

2.3 Electric Connections

Figure 2.4 provides a graphic of the module terminal

interface. The Terminal Block provides the connection

to the fieldbus interface board.

Bus connections to the module are made through

terminal block. As shown in figure 3, this is a 6

position terminal block. Pin definitions are provided in

Table 2-1.

2.3.1 Electrical Input, Fieldbus Interface

Voltage Level : 9 to 32 volts

Nominal Current : 22 mA, typical

Reverse Polarity : Unit is not polarity

Protection sensitive

Termination : Bus must be properly

terminated per ISA SP50 guidelines

2.3.2 Wiring dimensions

Cable range : 0.14-1.5mm2 or 26-14 AWG

For massive copper : 2.5mm2 max.

2.3.3 Procedure

1 Remove function module cover and isolation cover

(see fig. 4)

2 Bring the field wiring into the module housing

through the electrical access ports. When applicable,

install conduit per local and national electrical

codes, which apply to the application.

3 Connect the FOUNDATIONT Fieldbus signal to the

applicable terminals (see fig 5).

- For eurofast® or minifast® quick connector

pinout (see fig 6.).

- For hazardous area connections, see the following

drawing supplied with the Function module

(document : DOC.HA.Q):

Intrinsically safe C0240-08

3 Put the isolation cover back in place.

4 Mount the function module cover to the housing

(see fig. 4) or continue with chapter 4.

2.3.4 Tools

Tool for terminals : Screw driver 0.6 x 3.5

Tool for cover screws : Screw driver for cross slotted

Phillips screws nr. 2

Fig. 2.4 Installing wiring

Table 2.1 Terminal connections

Terminal nr. Description

1 +

2 shield FF 1 Signal

3 -

4 +

5 shield FF 1 Signal

6 -

Notes:

* The Fieldbus connection to the module is

not polarity sensitive.

* If shields are part of the cable, cut off the

shield and wrap with electrical tape to

isolate the shield from ground.

* Do not ground the shield within the module

as the shield should be grounded at the

source of the signal.

TM

Page 7


Page 8

TM

2.4 Quick Connect Option

All Emerson Process Management devices are

offered with an optional Quick Connection for the

fieldbus signal wiring. This type of connection provides

an interface to fieldbus devices and support

modules that is easier to install and more reliable by

providing a standard connection.

1. The Quick Connect should be installed in the

module at the factory. If it is, proceed to step 3

below.

2. To install the Quick Connect refer to Figure 5:

a. Apply sealant to the threads of the Quick

Connector.

b. Insert the wire pigtail into the desired conduit

opening and the connector into the housing until

tight.

c. Cut and trim the ends of the wires and connect

to the proper terminals.

3. Connect the Mating Connector to the installed

Quick Connect connector.

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Quick connector pinouts:

(male chassis part ; Views from above)

1

2

1 = FF signal -

2 = FF signal +

3 = Not connected

4 = Shield

eurofast ® minifast ®

3

4

1

2

Figure 2.5 Quick connector wirring

3

4


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

3 Initial Setup

3.1 Addressing

To setup and initialize a fieldbus device, and have it

communicate with other devices on the bus, the

device must have a working address. Each FieldQ

function module with Foundation Fieldbus communication

has its own unique factory-set address.

Use the host system to commission the module and

assign a working address. For information on using

the host system for device commissioning and

assigning addresses, see the appropriate host

system documentation.

3.2 Quick Setup

The module is a simple fieldbus device that can be

setup quickly. When the module requires setup, the

following procedures should be used for proper

operation. Refer to section 4 for more details on

setting up the module.

1. Set the Resource Block Mode to “Out-Of-Service”.

This will place all the function blocks including the

Transducer Block in their “Out-of-Service” mode.

2. Assign the channel of all applicable function blocks

to the desired Transducer Block parameter per

section 4.5.

3. Set XD_SCALE (EU_100, EU_0, and UNITS) in

the Analog Input block as required per the channel

to which they are connected. The default values

are usually acceptable.

4. Set PV_SCALE (EU_100, EU_0, and UNITS) in

the Analog Input block as required per the channel

to which they are connected. The default values

are usually acceptable.

5. Set XD_SCALE, OUT_STATE, and PV_STATE in

the Discrete Input and Discrete Output blocks to

the desired value for the state enumerations

needed for your application.

6. Set the Target Mode of the applicable function

blocks to their desired mode.

7. Set the Target Mode of the Transducer Blocks to

“Auto”.

8. Set the Resource Block Target Mode to “Auto”.

Verify that all blocks go to the correct mode. If not,

refer to the appropriate module maintenance and

troubleshooting manual for assistance.

9. Perform an initialization of the unit per section

4.2.4

3.3 Initialization

Initialization sets the end points and limit switch

points for the actuator. This process is done automatically,

by the module, however, the user must start it

and the unit must be wired according chapter 2. The

initialization process can be started in one of two

ways (see chapter 4.2.4):

1. Initialization using bus command.

2. Initialization using local buttons.

TM

Page 9


Page 10

TM

4 Detailed Configuration

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

This section describes more detailed information for configuring the Resource and Transducer Block parameters

to setup the module. Access to each parameter depends upon the host system software. For information on

using the host system to modify block parameters, see the appropriate appendix and host system documentation.

4.1 Resource Block

The Resource Block describes the characteristics of the fieldbus device such as device name and type, manufacturer,

serial number, amount of free memory, and free time. There is only one Resource Block in the module.

The parameters for configuring the Resource Block are referenced by group within the following sections. For

complete details of the parameters listed, refer to section. Refer to the applicable host documentation for procedures

to access the referenced parameters.

4.1.1 Identification

The identification parameters are used to provide information about the device. Unless otherwise noted, no

identification parameter, if modified, will have an impact of the operations of the device. Also, most parameters are

read only, providing information about the device as indicated by the manufacturer.

Tag Description: A unique description for the

Resource Block. The Tag Description must be

unique for each block within a system. (Writable,

no effect on device)

Final Assembly Number: Number used for identification

purposes. Associated with the field device.

(Read Only)

DD Revision: Revision of the DD associated with the

resource - used by an interface device to locate

the DD file for the resource. (Read Only)

Device Type: Manufacturer’s type number associated

with the resource - used by interface devices to

locate the DD file for the resource. (Read Only)

Distributor: Private label distributor name. This is an

optional field that may or may not contain useful

data (Read Only)

Hardware Revision: Hardware revision of that

hardware in which the Resource Block resides.

(Read Only)

ITK Version: Major revision number of the

interoperability test case used in certifying this

device as interoperable. The format and range of

the version number is defined and controlled by

the Fieldbus Foundation. Note: The value of this

parameter will be zero (0) if the device has not

been registered as interoperable by the FF. (Read

only).

Manufacturer ID: Manufacturer Identification Number

- used by an interface device to locate the DD file

for the resource. (Read Only)

Message Date: Date associated with the Message

Text parameter (Writable, no effect on the device)

Message Text: Used to indicate changes made by

the user to the device’s installation, configuration,

or calibration. (Writable, no effect on the device)

Output Board SN: The serial number of the FieldBus

Interface. (Read Only)

Software Rev - All: The complete revision string

containing: Major rev, Minor rev, Build rev, Time of

build, Day of week of build, Month of build, Day of

month of build, Year of build, and name of person

who performed the build. (Read Only)

Software Rev - Build: Build of software that the

Resource Block was created with. (Read Only)

Software Rev - Major: Major revision of software that

the Resource Block was created with. (Read Only)

Software Rev - Minor: Minor revision of software

that the Resource Block was created with. (Read

Only)


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

4.1.2 Process

The Process parameters are those parameters within the Resource Block that can affect the process in which the

device is working.

Plant Unit: Identification number of the plant unit.

This information may be used in the host system

for sorting alarms. (Writable, no effect on device)

Strategy: This parameter permits the strategic

grouping of blocks so a host system operator can

identify where the block is located. The blocks may

be grouped by plant area, plant equipment, or

process. This data is not checked or processed by

the block. (Writable, no effect on device)

RCas Time-Out: Time duration, in units of 1/32 of a

millisecond, at which to give up on computer writes

to function block ROut locations. Shed from ROut

will not happen when Shed ROut is set to 0.

(Writable, effect as noted)

ROut Time-Out: Time duration, in 1/32 milliseconds,

at which to give up on computer writes to function

block ROut locations. Shed from ROut shall never

happen when Shed ROut is 0. (Writable, changing

this parameter affects the time limit for loss of

communication from a remote device (not a host).

(Writable, effect as noted)

Block Mode: All blocks have a Mode parameter,

which determines the source of the setpoint, the

destination of the output, and how the block

executes. The ability to modify a block parameter is

determined by the mode. The mode required to

change the parameter is listed in the description

for each parameter.

The block mode is determined by the Block Mode

parameter (parameter name MODE_BLK). It is a

structured parameter composed of these subindexes:

Target mode (sub-index 1). The Target Mode is the

mode requested by the user or host system. Only one

mode is allowed to be set and it must be a permitted

mode as defined by the permitted sub-index of the

mode parameter. (Writable, affects block operation,

when changed to Out-Of-Service, puts all other

function block in out-of-service, causing the device to

no longer operate.)

Actual mode (sub-index 2). This is the actual mode of

the block. The Actual Mode may differ from the Target

Mode due to operating conditions of the block. The

Actual Mode is calculated as part of block execution.

This is a read only parameter and may not be changed

by the user. (Read Only)

Permitted mode (sub-index 3). The Permitted Mode

defines the modes allowed for the block. This again

is set by the user or host system but is restricted by

the module to modes supported by the module for

the particular block. Any change request to the

Target Mode (sub-index 1) or Normal Mode (subindex

2) is checked against the Permitted Mode

sub-index to ensure the requested mode is permitted.

However, when setting the Permitted Mode, there is

no check against the Target Mode (sub-index 1) or

Normal Mode (sub-index 2). Therefore, the module

may be in a target or normal mode that is not

permitted because the Permitted sub-index was

modified after the Target or Normal Mode was set.

This will have no effect on the module until the user

attempts to modify the Target or Normal Mode. At

this time, these sub-indexes are tested against the

Permitted Mode; thus, the user cannot change the

Target or Normal Modes to what was formerly

permitted. (Writable, sets which modes are allowed

in the device)

Normal mode (sub-index 4). The Normal Mode is the

mode the block should be in during normal operating

conditions. The Normal Mode is set by the user or

host system and can only be set to a Permitted Mode

(see Permitted Mode above). The user or host system

can compare the Actual Mode to the Normal Mode

and, based on the results, determine if the block is

operating normally. (Writable, no effect on device)

Changing the Block Mode requires accessing the

Block Mode parameter. For information on using the

host system to change the Block Mode via this

parameter, see the appropriate system documentation.

TM

Page 11


Page 12

TM

4.1.3 Alarms

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

The following parameters are associated with alarm functions (not including PlantWeb Alerts) within the Resource

Block.

the device will wait before re-sending an alarm.)

Write Priority: Priority of the alarm generated by Max Alerts Allowed: The maximum number of

setting Write Lock to “Not Locked”. (Writable,

unconfirmed alert reports that the module can

affects priority of alert, 0 effectively turns off alert, send without getting a confirmation. This limit is

1 indicates alert but does not report it, 2 and above determined by the amount of memory available for

report alert with priority.)

alert reports. Use Max Alerts Allow to set a

Confirm Time: The time, in milliseconds, the module number lower than Max Alerts Possible to control

waits for confirmation of receipt of a report before alert flooding. (Read Only)

sending the alert again. The module does not retry Max Alerts Possible: The maximum number of

if Confirm Time is 0. (Writable, affects how long

unconfirmed alert notify reports allowed. If Max

Alerts Allowed is set to 0, no alerts are reported.

(Writable, Changing this parameter sets the

maximum number of unacknowledged alarms to

be supported in the device.)

4.1.4 Options

Features and Features Selected: The parameters Features and Feature Selected determine optional behavior of

the module. The Features parameter is read only and defines which features are supported by the module. (The

Feature Selected parameter is writable and determines which options are actually enabled. Below is a list of the

options applicable to the Features and Feature Selected parameters that the module supports:

Soft Write lock supported

Hard Write lock supported

Output readback supported

Change of BYPASS in an automatic mode

Unicode Strings: All configurable string variables in

the module, except tag names, are octet strings.

Either ASCII or Unicode may be used. If the

configuration device is generating Unicode octet

strings, you must set the Unicode option.

Reports Supported : The module supports alert

reports. The reports option must be set in the

Features parameter to use this feature. If it is not

set, the host system must poll for alerts.

Fault State Supported: The module supports fault

State. The Fault State Supported option must be

set in the Features parameter to use this feature. If

it is not set, then Fault State will not be implemented

in the device..

Write Locks: Inputs to the security and write lock

functions include the hardware security switch, the

hardware and software write lock bits of the

Feature Selected parameter, the Write Lock

parameter, and the Write Lock Definition parameter.

The Write Lock parameter prevents modification

of parameters within the device except to clear

the Write Lock parameter. During this time, the

block will function normally updating inputs and

outputs and executing algorithms. When the Write

Lock condition is cleared, a WRITE_ALM alert is

generated with a priority that corresponds to the

Write Priority parameter.

The Feature Selected parameter enables the user

to select a hardware or software write lock or no

write lock capability. To enable the hardware

security function, enable the Hardware Select bit

in the Feature Selected parameter. When this bit

has been enabled the Write Lock parameter

becomes read only and will reflect the state of the

hardware switch. In order to enable the software

write lock, the Software Select bit must be set in

the Feature Selected parameter. Once this bit is

set, the Write Lock parameter may be set to

“Locked”. or “Not Locked” Once the Write Lock

parameter is set to “Locked” by either the software

or the hardware lock, all user requested writes as

determined by the Write Lock Definition parameter

shall be rejected.

The Write Lock Definition parameter allows the

user to configure whether the write lock functions

(both software and hardware) will control writing to

all blocks, or only to the resource and Transducer

Blocks. Internally updated data, such as process

variables and diagnostics, will not be restricted by

the security switch. The following table displays all

possible configurations of the Write Lock parameter.


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Table 4-1 Configurations of the Write Lock parameter

Feature Feature

Selected Selected Security Write Lock Write lock Write access

Hardware Software Switch Write Lock Read/Write Definition to blocks

Sel bit sel bit

0 (off) 0 (off) NA 1 (unlocked) Read Only NA All

0 (off) 1 (on) NA 1 (unlocked) Read/Write NA All

0 (off) 1 (on) NA 2(locked) Read/Write Physical Function

Blocks Only

0 (off) 1 (on) NA 2 (locked) Read/Write Everything None

1 (on) 0 (off) 1 0 (unlocked) 1 (unlocked) Read Only NA All

1 (on) 0 (off) 1 (locked 2 (locked) Read Only Physical Function

Blocks Only

1 (on) 0 (off) 1 (locked) 2 (locked) Read Only Everything None

(1) The hardware and software write lock select bits are mutually exclusive and the hardware select has the

highest priority. When the Hardware sel bit if set to 1 (on), the Software Select bit is automatically set to 0 (off)

and is read only.

Output Readback Supported: When this option is

selected, the output function blocks (DO and AO)

will use the Readback parameter from the Transducer

Block as its readback value. If it is not

selected, then Readback is set the the value of the

“Output” parameter of the Function Block.

Download Mode: Gives access to the boot block

code for application downloads. (Writable, when

set to download mode, the device enters a special

mode for downloading new software and will not

perform its intended function.)

Write Lock Definition Parameter describing the

implementation of the Write Lock parameter.

(Writable, when set, this parameter limits access to

parameters in the device.

Write Lock: If locked, no writes are allowed, except

to unlock Write Lock. When locked, block inputs

will continue to be updated. (When set, this

parameter limits access to writable parameters in

the device.)

Start With Defaults: Controls what defaults are used

when power is applied to the module. (Writable,

resets the device and, depending on the option

selected, changes parameters to their default

values.)

TM

Page 13


Page 14

TM

4.1.5 PlantWeb Alerts

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

The Resource Block will act as a coordinator/collector for PlantWeb alerts. There will be three primary types of

alerts: 1) Failed, 2) Maintenance and 3) Advisory. These alerts contain information regarding device errors which

are detected by the software. These alert parameters are composed of 32 “Conditions”, and each parameter can

have up to 32 “Conditions”.

There is a Recommended Action parameter which displays the recommended action based on the alerts currently

active in the device.

4.1.5.1 Conditions

The following are the conditions within the PlantWeb Alerts parameters in alphabetical order. Refer to the parameter

details for how the conditions are allocated in the parameter.

Actuator - The alert has been caused by an event

associated with the actuator to which the device is

connected

Aux Analog I/O - The alert has been caused by a

function or feature associated with the Auxiliary

Analog I/O within the device.

Aux Disc I/O - The alert has been caused by a

function or feature associated with the Auxiliary

Discrete I/O within the device.

Bus Electronics - The alert has been caused by

an event within the bus electronics module in the

device

Configuration - The alert has been caused by an

event in the configuration/setup.

Deviations - The alert has been caused by an

event associated with a deviation test failing

Electronics - The alert has been caused by an

event within the general electronics of the device

External - The alert has been caused due to an

influence external to the device, not including the

actuator or valve itself.

I/O Electronics - The alert has been caused by an

event within the I/O electronics module in the

device

Instrument - The Alert has been caused by an

event within the Instrument/Controller.

Limits - The alert has been caused by an event

associated with a limit test failing

Other - The alert has been caused by an event

that cannot be associated with any of the other

possible conditions.

Pressure - The alert has been caused by an event

in the pressure control/monitor function of the

device.

Time Limits - The alert has been caused by an

event associated with a time limit being exceeded

Travel - The alert has been caused by an event in

the travel control/monitor function of the device.

User - The alerts has been caused by an event

within the device as defined by the user.

Valve - The alert has been caused by an event

associated with the valve to which the device is

connected

Valve System (Actuator and/or Valve) - The alert

has been caused by an event associated with the

valve system (valve and/or actuator) to which the

device is connected


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

4.1.5.2 Failed Alerts

A Failure Alert indicates a failure within a device that

will make the device or some part of the device nonoperational.

This implies that the device is in need of

repair and must be fixed immediately. There are five

parameters associated with Failed Alerts specifically,

they are described in the following sections.

Failed Alerts - Enabled This parameter is used to

enable the indication and reporting of each corresponding

condition. When a condition is disabled,

the device shall not detect that alert condition, it

shall not be indicated in Failed Alerts - Active or

be reported via Failed Alerts. If an alert enable

parameter is changed to ‘disabled’ while the alert is

active, it shall clear the alert and reevaluate the

alert. (Writable, only affects the applicable condition

modified. When set the condition will not be

indicated or reported).

Failed Alerts - Suppressed: This parameter will

mask any of the failed conditions listed in Failed

Alerts. Setting a bit to 1 (true) will cause the

corresponding condition to be indicated in Failed

Alerts - Active but it will not be reported to the

host via Failed Alerts. If an alert mask is changed

while the alert is active, the alert is cleared and all

the conditions are reevaluated. (Writable, only

affects the applicable condition modified. When set

the condition will be indicated however, it will not

be reported).

Failed Alerts - Priority: Designates the priority of

Failed Alerts. The default is 2 and the recommended

value is between 10 and 15. (Writable,

changes the priority of the applicable alert).

Failed Alerts - Active: This parameter displays

which of the conditions within the Failed Alerts is

active. When a device detects a condition has

become active, it shall set the corresponding bit in

the Failed Alerts - Active parameter. If it is not

suppressed, it will be reported using the associated

alert parameter. (Read Only)

Failed Alert Alarm: This parameter is used to report

the particular failed condition to the host. (Read

Only)

4.1.5.3 Maintenance Alerts

A Maintenance Alert indicates a condition within a

device that, if not attended to in the near future (the

type of alert defines the time period for “Near Future”)

will make the device or some part of the device nonoperational.

This implies that the device is in need of

repair and must be fixed as soon as possible. There

are five parameters associated with Maintenance

Alerts specifically, they are described in the following

sections.

Maintenance Alerts - Enabled This parameter is

used to enable the indication and reporting of each

corresponding condition. When a condition is

disabled, the device shall not detect that alert

condition, it shall not be indicated in Maintenance

Alerts - Active or be reported via Maintenance

Alerts. If an alert enable parameter is changed to

‘Disabled’ while the alert is active, it shall clear and

reevaluate the alert. (Writable, only affects the

applicable condition modified. When set the

condition will not be indicated or reported).

Maintenance Alerts - Suppressed: This parameter

will mask any of the failed conditions listed in

Maintenance Alerts. Setting a bit to 1 (true) will

cause the corresponding condition to be indicated

in Maintenance Alerts - Active but it will not be

reported to the host via Maintenance Alerts. If an

alert mask is changed while the alert is active, the

alert is cleared and all the conditions are reevaluated.

(Writable, only affects the applicable condition

modified. When set the condition will be

indicated however, it will not be reported).

Maintenance Alerts - Priority: Designates the

priority of Maintenance Alerts. The default is 2 and

the recommended value is between 10 and 15.

(Writable, changes the priority of the applicable

alert).

Maintenance Alerts - Active: This parameter

displays which of the conditions within the Maintenance

Alerts is active. When a device detects a

condition has become active, it shall set the

corresponding bit in the Maintenance Alerts -

Active parameter. If it is not suppressed, it will be

reported using the associated alert parameter.

(Read Only)

Maintenance Alert Alarm: This parameter is used to

report the particular failed condition to the host.

(Read Only)

TM

Page 15


Page 16

TM

4.1.6 Advisory Alarms

An Advisory Alert indicates a condition within a

device that is informational in nature. The alert is

used to notify the host that the device has detected a

conditions within the device that is not critical, will not

cause a failure if left unattended but should be

reported to the host for awareness and possible

action. There are five parameters associated with

Advisory Alerts specifically, they are described in

the following sections.

Advisory Alerts - Enabled This parameter is used to

enable the indication and reporting of each corresponding

condition. When a condition is disabled,

the device shall not detect that alert condition, it

shall not be indicated in Advisory Alerts - Active

or be reported via Advisory Alerts. If an alert

enable parameter is changed to ‘Disabled’ while

the alert is active, it shall clear and reevaluate the

alert. (Writable, only affects the applicable condition

modified. When set the condition will not be

indicated or reported).

Advisory Alerts - Suppressed: This parameter will

mask any of the failed conditions listed in Advisory

Alerts. Setting a bit to 1 (true) will cause the

corresponding condition to be indicated in Advisory

Alerts - Active but it will not be reported to

the host via Advisory Alerts. If an alert mask is

changed while the alert is active, the alert is

cleared and all the conditions are reevaluated.

(Writable, only affects the applicable condition

modified. When set the condition will be indicated

however, it will not be reported).

Advisory Alerts - Priority: Designates the priority of

Advisory Alerts. The default is 2 and the recommended

value is between 10 and 15. (Writable,

changes the priority of the applicable alert).

Advisory Alerts - Active: This parameter displays

which of the conditions within the Advisory Alerts

is active. When a device detects a condition has

become active, it shall set the corresponding bit in

the Advisory Alerts - Active parameter. If it is not

suppressed, it will be reported using the associated

alert parameter. (Read Only)

Advisory Alert Alarm: This parameter is used to

report the particular failed condition to the host.

(Read Only)

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

4.1.7 Recommended Actions for PlantWeb

Alarms

The Recommended Action parameter displays a

text string that will give a recommended course of

action to take based on which PlantWeb alerts are

active.

Recommended Action: List of Recommended

Actions displayed with a device alert. (Read Only).


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

4.2 Control Transducer Block

4.2.1 Mode

The Mode parameters are those parameters within the Control Transducer Block that can affect the mode of the

Transducer block.

Plant Unit: Identification number of the plant unit.

This information may be used in the host system

for sorting alarms. (Writable, no effect on device)

Strategy: This parameter permits the strategic

grouping of blocks so a host system operator can

identify where the block is located. The blocks may

be grouped by plant area, plant equipment, or

process. This data is not checked or processed by

the block. (Writable, no effect on device)

Tag Description: A unique description for the Resource

Block. The Tag Description must be

unique for each block within a system. (Writable,

no effect on device)

Block Mode: All blocks have a Mode parameter,

which determines the source of the setpoint, the

destination of the output, and how the block

executes. The ability to modify a block parameter is

determined by the mode. The mode required to

change the parameter is listed in the description

for each parameter.

The block mode is determined by the Block Mode

parameter (parameter name MODE_BLK). It is a

structured parameter composed of these subindexes:

Target mode (sub-index 1). The Target Mode is the

mode requested by the user or host system. Only one

mode is allowed to be set and it must be a permitted

mode as defined by the permitted sub-index of the

mode parameter. (Writable, affects block operation,

when changed to Out-Of-Service, puts all other

function block in out-of-service, causing the device to

no longer operate.)

Actual mode (sub-index 2). This is the actual mode of

the block. The Actual Mode may differ from the Target

Mode due to operating conditions of the block. The

Actual Mode is calculated as part of block execution.

This is a read only parameter and may not be changed

by the user. (Read Only)

Permitted mode (sub-index 3). The Permitted Mode

defines the modes allowed for the block. This again

is set by the user or host system but is restricted by

the module to modes supported by the module for

the particular block. Any change request to the

Target Mode (sub-index 1) or Normal Mode (subindex

2) is checked against the Permitted Mode

sub-index to ensure the requested mode is permitted.

However, when setting the Permitted Mode, there is

no check against the Target Mode (sub-index 1) or

Normal Mode (sub-index 2). Therefore, the module

may be in a target or normal mode that is not

permitted because the Permitted sub-index was

modified after the Target or Normal Mode was set.

This will have no effect on the module until the user

attempts to modify the Target or Normal Mode. At

this time, these sub-indexes are tested against the

Permitted Mode; thus, the user cannot change the

Target or Normal Modes to what was formerly

permitted. (Writable, sets which modes are allowed

in the device)

Normal mode (sub-index 4). The Normal Mode is the

mode the block should be in during normal operating

conditions. The Normal Mode is set by the user

or host system and can only be set to a Permitted

Mode (see Permitted Mode above). The user or

host system can compare the Actual Mode to the

Normal Mode and, based on the results, determine

if the block is operating normally. (Writable, no effect

on device)

Changing the Block Mode requires accessing the

Block Mode parameter. For information on using

the host system to change the Block Mode via

this parameter, see the appropriate system

documentation.

TM

Page 17


Page 18

TM

4.2.2 Valve/Actuator Identification

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

The following parameters, when configured, provide information about the valve and actuator to which the module

is connected and controlling.

Actuator Man Id: Actuator manufacturer identification

in FOUNDATION fieldbus Manufacturer ID

units. (Writable, no impact to the device.)

Actuator Model Num: Actuator model number

(Writable, no impact to the device.)

Actuator Serial Number: Actuator serial number

(Writable, no impact to the device.)

Actuator Fail Action: Specifies the action that the

actuator takes in case of failure. (Writable, changing

this parameter may cause control of the

actuator/valve to be reversed such that open = 0%

and closed = 100%

4.2.3 Events

Valve Manufacturer ID: Valve manufacturer identification

in FOUNDATION fieldbus Manufacturer ID

units. (Writable, no impact to the device.)

Valve Model Number: Valve model number (Writable,

no impact to the device.)

Valve Serial Number: Valve serial number (Writable,

no impact to the device.)

Valve Type: The valve type to included “Rotary”,

“Linear”, “Ball”, “Globe”, and “Butterfly” to name a

few.. (Writable, no impact to the device.)

Events are conditions or states within the device that, when they occur, can be reported to the user through

PlantWeb Alerts to the Host systems. When a parameter has an associated event, the information for configuring

the event as well as its value and other information are provided as sub-indices to the parameter All event

parameters will have one or more of the following indices: Event Value, High Limit, Low Limit, Filter, and Options.

Each of these indices is described in the following sections.

4.2.3.1 Event Value

This is the value associated with the parameter.

4.2.3.2 Event Limits

The event limits are a high limit and and low limit.

They are typically the parameter name followed by

.High Limit (_HI_LIMIT) or .Low Limit ( _LO_LIMIT).

These limits are compared to the event value to

determine if the event is active and an alert needs to

be generated. These limits are used in conjunction

with the Filter (_FILTER) sub-index when determining

whether an event is to be reported. If the value being

tested is larger than the High Limit or lower than the

Low Limit for the time/cycles/etc as specified by

Filter, then the event shall be flagged as active and

reported. See the Filter section below for more

information on this processing.

4.2.3.3 Event Filter

The event filter, typically the parameter name with the

Filter (_FILTER) suffix is used in conjunction with

the sub-indices (see previous paragraph) to determine

if the parameter is in an active state. Typically

Filter will be a measure of time or cycles or counts or

something similar to filter the event such that false

positives are not indicated. In order for the event to

become active, it shall exceed its limit value for the

time or cycles specified by Filter. If prior to becoming

active, the parameter value falls within the limit then

the filtering process shall be restarted.

4.2.3.4 Event Options

The event Options (_OPTIONS) sub-index is used to

provide information about the event and to configure

the event. For Status, the Options sub-index provides

the following:

A read-only indication as to the current state of the

event (active or inactive)

A read-only indication as to whether or not the

event can be masked.

A read-only indication as to the default PlantWeb

Alerts level associated with the event (levels are

Advisory, Maintenance, and Failure).

For configuration, the options sub-index provides the

following:

The ability to mask the event.

The ability to raise the PlantWeb Alert level for

which it will be reported (levels from lowest to

highest are: Advisory, Maintenance, and Failure).


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

4.2.3.5 Averages

For some parameters, it is advantageous to calculate an average value that is then tested as an independent

event still within the parameter The sub-indices associated with an average are typically in the format of parameter

name with a suffix of: Average Value (_AVG_VALUE), Average Count (_AVG_COUNT), Average Max

(_AVG_MAX), Average Min (_AVG_MIN). The meaning of each of these is:

The sub-index Average Value is the average value

of the last Average Count parameter values.

The sub-indices Average Max and Min are the

Maximum and Minimum values respectively of the

last Average Count parameter values.

Cycle Count - Actuator: The number of cycles

associated with the Actuator. This parameter is

composed of the following sub-indices:

- Actuator Cycle Counter: Current Cycle Counter

value for the Actuator. (Read Only)

- Actuator Cycle Ctr Limit: The Limit associated with

the event for this parameter (Writable, sets the upper

limit associated with the counter.)

- Actuator Cycle Ctr Options: Status / options subindex.

(Writable per section 4.2.3.4 above)

Cycle Count - Controller: The number of cycles

associated with the Controller. This parameter is

composed of the following sub-indices:

- Controller Cycle Counter: Current Cycle Counter

value for the Controller. (Read Only)

- Controller Cycle Ctr Limit: The Limit associated with

the event for this parameter (Writable, sets the upper

limit associated with the counter.)

- Controller Cycle Ctr Options: Status / options subindex.

(Writable per section 4.2.3.4 above)

When an average value is being calculated, and

the number of counts is less than Average Count,

the average is calculated based on the current

count value until Average Count is reached.

Setting the bit “Clear Average Data” in the Options

sub-index clears the Average Value, Max, and

Min sub-indices.

4.2.3.6 Cycle Counters

Cycle counters are used to count the number of times a component of a typical final control element has been

cycled. A cycle is considered movement in one direction or a change in direction. When a valve is stroked from

open to close, that is one cycle, when it is stroked from close to open, that is another cycle. The FieldQ counts the

number of cycles for the 4 major components, the Controller, Solenoid, Actuator, and Valve. An event associated

with each cycle counter can be set to alert the host system when the number of cycles for the counter has

exceeded a user set maximum.

Cycle Count - Solenoid: The number of cycles

associated with the Solenoid. This parameter is

composed of the following sub-indices:

- Solenoid Cycle Counter: Current Cycle Counter

value for the Solenoid. (Read Only)

- Solenoid Cycle Ctr Limit: The Limit associated with

the event for this parameter (Writable, sets the upper

limit associated with the counter.)

- Solenoid Cycle Ctr Options: Status / options subindex.

(Writable per section 4.2.3.4 above)

Cycle Count - Valve: The number of cycles associated

with the Valve. This parameter is composed of

the following sub-indices:

- Valve Cycle Counter: Current Cycle Counter value for

the Valve. (Read Only)

- Valve Cycle Ctr Limit: The Limit associated with the

event for this parameter (Writable, sets the upper limit

associated with the counter.)

- Valve Cycle Ctr Options: Status / options sub-index.

(Writable per section 4.2.3.4 above)

TM

Page 19


Page 20

TM

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

4.2.3.7 Time in Position

The Time in Position parameter is used as a timer to indicate the amount of time the final control element has

been in its current position (“Open” or “Closed”). When the final control element position changes states, the

timer is reset and counting starts over from zero. The timer is only reset to zero when the final control element

reaches the other state, should it not reach the other state, and return to its original state, the timer will not be

reset. An event associated with the Time in Position parameter can be set to alert the host system when the

amount of time has exceeded a user set High Limit.

Time in Position: The amount of time, in seconds,

that the final control element has been in its

current position. This parameter is composed of

the following sub-indices:

- Time In Position Value: Current value of the Time In

Position timer. (Read Only).

- Time In Position Limit: The Limit associated with the

event for this parameter (Writable, sets the upper limit

associated with the counter.)

- Time In Position Options: Status / options sub-index.

(Writable per section 4.2.3.4 above)

4.2.3.8 Break and Travel Times

Break and travel times are used to indicate the amount of time the final control element takes 1)to indicate an

open or close movement has started once commanded to move, and 2) to travel from one state to the other.

Break time is consider the amount of time, in milliseconds, that the device requires from the time it is commanded

by the IO card to change states until the applicable limit switch indicates that the final control element

has moved away from its current state.

Travel time is the amount of time, in milliseconds, that the final control element requires to travel from its current

state to its commanded state. The time starts when the applicable limit switch indicates the final control element

has started moving and the target limit switch indicates it has reached its destination.

An event associated with each time value, and its average value, can be set to alert the host system when the

time has exceeded a user set maximum.

Open Break Time: The break time associated with

opening the Valve. This parameter is composed of

the following sub-indices:

- Open Break Time Value: The break time associated

with last open movement of the final control element.

(Read Only)

- Open Break Time High Limit: The Hi Limit value

associated with the event. (Writable, sets the upper

limit associated with the event.)

- Open Break Time Low Limit: The Lo Limit value

associated with the event. (Writable, sets the lower

limit associated with the event.)

- Open Break Time Filter: Number of times for which

the value must be in a limit condition before an event

will be recorded. (Writable, used to filter the event.)

- Open Break Time Options: Status / options subindex.

(Writable per section 4.2.3.4 above)

- Open Break Time Average: The average open break

time of the last N times the final control element was

commanded to Open. N is the count as defined in the

Open Break Time Avg Count sub-index below. (Read

Only)

- Open Avg Value High Limit: The Hi Limit value

associated with the event. (Writable, sets the upper

limit associated with the event.)

- Open Break Time Avg Low Limit: The Lo Limit value

associated with the event. (Writable, sets the lower

limit associated with the event.)

- Open Break Time Avg Count: The number of break

cycles included in average (Writable, affects the

average value only.)

- Open Break Time Avg Max: The Maximum Break

time value included in Average (Read Only)

- Open Break Time Avg Min: The Minimum Break time

value included in Average (Read Only)

- Open Break Time Avg Options: Status / options subindex.

(Writable per section 4.2.3.4 above)

Close Break Time: The break time associated with

closing the Valve. This parameter is composed of

the following sub-indices:

- Close Break Time Value: The break time associated

with last close movement of the final control element.

(Read Only)

- Close Break Time High Limit: The Hi Limit value

associated with the event. (Writable, sets the upper

limit associated with the event.)

- Close Break Time Low Limit: The Lo Limit value

associated with the event. (Writable, sets the lower

limit associated with the event.)

- Close Break Time Filter: Number of times for which

the value must be in a limit condition before an event

will be recorded. (Writable, used to filter the event.)

- Close Break Time Options: Status / options subindex.

(Writable per section 4.2.3.4 above)

- Close Break Time Average: The average close break

time of the last N times the final control element was

commanded to Close. N is the count as defined in the

Close Break Time Avg Count sub-index below. (Read

Only)

- Close Avg Value High Limit: The Hi Limit value

associated with the event. (Writable, sets the upper

limit associated with the event.)


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

- Close Break Time Avg Low Limit: The Lo Limit value

associated with the event. (Writable, sets the lower

limit associated with the event.)

- Close Break Time Avg Count: The number of break

cycles included in average (Writable, affects the

average value only.)

- Close Break Time Avg Max: The Maximum Break

time value included in Average (Read Only)

- Close Break Time Avg Min: The Minimum Break time

value included in Average (Read Only)

- Close Break Time Avg Options: Status / options subindex.

(Writable per section 4.2.3.4 above)

Open Travel Time: The travel time associated with

opening the Valve. This parameter is composed of

the following sub-indices:

- Open Travel Time Value: The travel time associated

with last open movement of the final control element.

(Read Only)

- Open Travel Time High Limit: The Hi Limit value

associated with the event. (Writable, sets the upper

limit associated with the event.)

- Open Travel Time Low Limit: The Lo Limit value

associated with the event. (Writable, sets the lower

limit associated with the event.)

- Open Travel Time Filter: Number of times for which

the value must be in a limit condition before an event

will be recorded. (Writable, used to filter the event.)

- Open Travel Time Options: Status / options subindex.

(Writable per section 4.2.3.4 above)

- Open Travel Time Average: The average open travel

time of the last N times the final control element was

commanded to Open. N is the count as defined in the

Open Travel Time Avg Count sub-index below. (Read

Only)

- Open Avg Value High Limit: The Hi Limit value

associated with the event. (Writable, sets the upper

limit associated with the event.)

- Open Travel Time Avg Low Limit: The Lo Limit value

associated with the event. (Writable, sets the lower

limit associated with the event.)

- Open Travel Time Avg Count: The number of travel

cycles included in average (Writable, affects the

average value only.)

- Open Travel Time Avg Max: The Maximum Travel time

value included in Average (Read Only)

- Open Travel Time Avg Min: The Minimum Travel time

value included in Average (Read Only)

- Open Travel Time Avg Options: Status / options subindex.

(Writable per section 4.2.3.4 above)

Close Travel Time: The travel time associated with

closing the Valve. This parameter is composed of

the following sub-indices:

- Close Travel Time Value: The travel time associated

with last close movement of the final control element.

(Read Only)

- Close Travel Time High Limit: The Hi Limit value

associated with the event. (Writable, sets the upper

limit associated with the event.)

- Close Travel Time Low Limit: The Lo Limit value

associated with the event. (Writable, sets the lower

limit associated with the event.)

- Close Travel Time Filter: Number of times for which

the value must be in a limit condition before an event

will be recorded. (Writable, used to filter the event.)

- Close Travel Time Options: Status / options subindex.

(Writable per section 4.2.3.4 above)

- Close Travel Time Average: The average close travel

time of the last N times the final control element was

commanded to Close. N is the count as defined in the

Close Travel Time Avg Count sub-index below. (Read

Only)

- Close Avg Value High Limit: The Hi Limit value

associated with the event. (Writable, sets the upper

limit associated with the event.)

- Close Travel Time Avg Low Limit: The Lo Limit value

associated with the event. (Writable, sets the lower

limit associated with the event.)

- Close Travel Time Avg Count: The number of travel

cycles included in average (Writable, affects the

average value only.)

- Close Travel Time Avg Max: The Maximum Travel

time value included in Average (Read Only)

- Close Travel Time Avg Min: The Minimum Travel time

value included in Average (Read Only)

- Close Travel Time Avg Options: Status / options subindex.

(Writable per section 4.2.3.4 above)

TM

Page 21


Page 22

TM

4.2.4 Initialization

Initialization sets the end points and limit switch

points for the actuator. This process is done automatically,

by the module, however, the user must start it.

The initialization process can be started in one of two

ways:

1) Initialization via the bus,

2) Initialization with the local buttons.

WARNING:

* During the initialization routine the actuator

/valve combination will cycle several times.

* Before initialization check whether the

actuator and valve have the same “Open”

and “Closed” positions .

* Be sure the isolation cover is in place

before the initialization routine is started.

* Be sure the valve stroke can be completed

without obstruction before the initialization

routine is started.

Important:

* Manual mode is enabled by default to

perform auto-initialization at the unit.

* In manual mode only monitoring the module

is possible, controlling the module is

not possible.

* Digital mode can be enabled by the host

system.

* The buttons are disabled in digital mode.

* To be able to change the transducer block,

it must be set to “Out of service”.

4.2.4.1 Implementation of the device driver in the

host system.

These drivers are available from www.FieldQ.com.

See the documentation of your host system how to

implement these device drivers in your host system.

4.2.4.2 Device address.

Each FieldQ function module with Foundation

Fieldbus communication has its own unique factoryset

address.

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

4.2.4.3 Initialization - Using Bus Command

(digital mode)

The parameter for Initialization is the Initialization

Record as defined below. Two sub-indices are used,

one as a command to the module and the other as a

status from the module.

Initialization Record: The Initialization command

and status. This parameter is composed of the

following sub-indices:

- Initialization Command: Command sub-index to

start initialization. (Writable, this command will

cause the device to start its initialization process,

which in turn will cause the actuator and valve to

move.)

- Initialization Status: The status of the initialization

process. (Read Only)

To initialize the actuator via the fieldbus, perform the

following steps using the host system. Refer to the

host system operation manuals for accessing parameters

in the device.

1. Place the Control Transducer Block in its “Out-of-

Service” mode.

2. Command the FieldQ Module to start initialization

by writing the “Auto Initialize” command to the

Initialization Command sub-index of the “Initialization

Record” parameter.

3. Monitor the Initialization Status sub-index of the

Initialization Record parameter to see when the

initialization process is complete.

4. Refer to section 4.2.4.3 if the initialization process

does not complete without errors.

5. Return the Control Transducer Block to the “Auto”

mode once initialization is complete.

Switch points D 4°

D = Deadband =

D


Closed

Fig. 4.1 Feedback characteristic

Open


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

4.2.4.4 Initialization - Using Local Buttons

(manual mode)

To initialize the actuator using the local buttons,

perform the following steps using the host system

and local buttons. Refer to the host system operation

manuals for accessing parameters within the FieldQ

FF module.

Buttons are default enabled.

To enable the local buttons, the control mode must be

changed from bus to local. The following steps will

enable the local buttons.

1. Place the Control Transducer Block in its “Out-of-

Service” mode.

2. Enable the keypad by writing “Manual Mode” to

the Control Type parameter.

3. Place the Control Transducer Block in its “Auto”

mode.

Closed button

Closed LED

Status LED

Open LED

Open button

* Buttons are default enabled.

* ”Open” and “Closed” LED are disabled.

Fig. 4.2 Initialization buttons (behind front cover of

module).

Push

4 sec.

Fig. 4.3 Starting of initialization using the local

buttons

With the Transducer Block back in “Auto”, initialization

can be invoked locally at the actuator, via the

local buttons, by performing the following steps:

1. Remove the access cover of the module revealing

the local buttons.

2. Press and hold the “Open” and “Close” button at

the same time for 4 seconds.

3. Status LED will blink.

4. Actuator will cycle twice.

5. When initialization is complete, the LED will be a

steady green.

6. If the LED is not steady, then there was an error

during initialization. Refer to section 4.2.4.3 if the

initialization process does not complete without

errors.

7. Change the “Control Type” parameter to “Digital”

to limit access to the module via the local buttons.

With the Transducer Block in “Auto”, the block will

recognize when the local buttons are being used and

will signal the host that this is occurring by setting the

status on the Readback parameter to “Good

(Cascade):Local Override:not limited”, for normal

local button operation. However, when initialization is

started, the limited state will change from “Not

limited” to “Constant”. This status will tell the process

when and why the actuator is being controlled

locally and allow the host to take action as required

when the local action is complete.

4.2.4.3 Initialization Commands

The following are the initialization commands for the

module:

No Action - Default value

Start Zero Point Adjustment

Start Initialization

Reset-Valve Travel - Errors and Counters

Reset-Internal Control Loop - Errors and Counters

Abort Current Initialization

4.2.4.4 Initialization Status

The following is the status returned by the module

during initialization and when initialization is complete.

Undetermined

Running

Aborted

Time Out

Abort by means of Emergency Override

Zero Point Error

Successful

No Valid Data

TM

Page 23


Page 24

TM

4.2.5.1 If the read out on the button board is

reversed or,

Readjustment of the exact positions is

needed;

(manual mode)

Do as follows:

1 Check if the actuator is correctly mounted to the

valve, if yes:

2 Push the correct position button on the board for 5

seconds

3 The corresponding LED starts to blink

4 Push the button again to confirm

5 The other position changes automatically

4.2.5.2 If auto initialization routine is not

completed (Status LED is flashing)

(manual mode & digital mode)

1 Check supply pressure

2 Check Actuator assembly code (see Installation &

Operation Manual FieldQ Valve Actuator)

3 Repeat auto initialization routine

4 When the actuator does not move within 5 seconds,

the auto initialization will not complete.

5 Preform the steps of chapter 4.2.4

4.2.5.3 Manual setting of feedback switches

routine:

(manual mode)

1 Move the actuator to the closed position (see

chapter 5)

2 Push the “closed” button on the board for 5 seconds.

3 The corresponding LED starts to blink.

4 Push the “closed” button again to confirm.

5 Move the actuator to the open position (see

chapter 5)

6 Push the “open” button on the board for 5 seconds.

7 The corresponding LED starts to blink.

8 Push the “open” button again to confirm.

4.2.6 Recognizing LED

(digital mode)

To recognize a particular FieldQ actuator in the plant,

it is possible to send a recognizing signal from the

host system. “Recognizing LED” can be activated in

the transducer block. This signal is send to the

module the status LED will blink for 1 minute.

4.2.7 Implementation in the process.

The function module is now ready to be implemented

in your process. See the documentation of your host

system how to implement the device.

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

4.2.8 Check functioning

For function test the unit must be connected to a host

system and power must be connected (see chapter

3).

1 Send an “Open” command to the Foundation

Fieldbus module.

2 Actuator moves to “Open” position.

3 Send an “Close” command to the Foundation

Fieldbus module.

4 Actuator moves to “Closed” position.

Note:

For sending the “Open” or “Closed” command, check

the applicable sections of the documentation supplied

with the host system and Reference Manual Fieldbus

Foundation Function Module (DOC.RM.QM34,

available on request or through www.FieldQ.com)

5 Put the isolation cover back in place and mount the

function module cover to the housing (see fig. 4).

4.2.9 Local Manual Control (option)

In case of an emergency or for maintenance purposes,

the FieldQ can be operated localy.

To operate the optional local manual control, use a

screw driver and turn it 90°.

It is possible to rotate the screw multiple cycles. The

unit will toggle every 90° between “Open” and

“Closed”.

3

2 (90˚)

Fig. 4.4 Local Manual Control (option)

0

1

1

1

0


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

4.3 Auxiliary I/O Transducer Block

4.3.1 Mode

The Mode parameters are those parameters within the Auxiliary Transducer Block that can affect the mode of the

Transducer block.

Plant Unit: Identification number of the plant unit.

This information may be used in the host system

for sorting alarms. (Writable, no effect on device)

Strategy: This parameter permits the strategic

grouping of blocks so a host system operator can

identify where the block is located. The blocks may

be grouped by plant area, plant equipment, or

process. This data is not checked or processed by

the block. (Writable, no effect on device)

Tag Description: A unique description for the Resource

Block. The Tag Description must be

unique for each block within a system. (Writable,

no effect on device)

Block Mode: All blocks have a Mode parameter,

which determines the source of the setpoint, the

destination of the output, and how the block

executes. The ability to modify a block parameter is

determined by the mode. The mode required to

change the parameter is listed in the description

for each parameter.

The block mode is determined by the Block Mode

parameter (parameter name MODE_BLK). It is a

structured parameter composed of these subindexes:

Target mode (sub-index 1). The Target Mode is the

mode requested by the user or host system. Only one

mode is allowed to be set and it must be a permitted

mode as defined by the permitted sub-index of the

mode parameter. (Writable, affects block operation,

when changed to Out-Of-Service, puts all other

function block in out-of-service, causing the device to

no longer operate.)

Actual mode (sub-index 2). This is the actual mode of

the block. The Actual Mode may differ from the Target

Mode due to operating conditions of the block. The

Actual Mode is calculated as part of block execution.

This is a read only parameter and may not be changed

by the user. (Read Only)

Permitted mode (sub-index 3). The Permitted Mode

defines the modes allowed for the block. This again

is set by the user or host system but is restricted by

the module to modes supported by the module for

the particular block. Any change request to the

Target Mode (sub-index 1) or Normal Mode (subindex

2) is checked against the Permitted Mode

sub-index to ensure the requested mode is permitted.

However, when setting the Permitted Mode, there is

no check against the Target Mode (sub-index 1) or

Normal Mode (sub-index 2). Therefore, the module

may be in a target or normal mode that is not

permitted because the Permitted sub-index was

modified after the Target or Normal Mode was set.

This will have no effect on the module until the user

attempts to modify the Target or Normal Mode. At

this time, these sub-indexes are tested against the

Permitted Mode; thus, the user cannot change the

Target or Normal Modes to what was formerly

permitted. (Writable, sets which modes are allowed

in the device)

Normal mode (sub-index 4). The Normal Mode is the

mode the block should be in during normal operating

conditions. The Normal Mode is set by the user

or host system and can only be set to a Permitted

Mode (see Permitted Mode above). The user or

host system can compare the Actual Mode to the

Normal Mode and, based on the results, determine

if the block is operating normally. (Writable, no effect

on device)

Changing the Block Mode requires accessing the

Block Mode parameter. For information on using

the host system to change the Block Mode via

this parameter, see the appropriate system

documentation.

TM

Page 25


Page 26

TM

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

4.3.2 Analog Inputs

The Auxiliary Analog Inputs provide a mechanism for getting an analog signal of 4-20 mA or 0 - 10 VDC into the

device and to other devices via the bus. The analog inputs are assigned to a channel and can be passed to other

devices via the Analog Input Function block.

Auxiliary Analog Input 1: The parameter associated

with the 4-20mA analog input. This parameter is

composed of the following sub-indices:

Note: This parameter has no effect on the device.

The information is received and processed by the

block and passed on to the host via an Analog

Input function block. This parameter can generate

alerts based on the analog input value.

Auxiliary Input 1 Status: The status sub-index associated

with the value sub-index. This sub-index is status

passed to the connected Analog input block. (Read

Only)

Auxiliary Input 1 Value: The value associated with the

analog input. This sub-index is the value passed to the

connected Analog input block. (Read Only)

Auxiliary Input 1 100% Engineering Units: The

engineering unit value which represents the upper end

of range of the associated block parameter. (Read

Only)

Auxiliary Input 1 0% Engineering Units: The engineering

unit value which represents the lower end of range

for the associated block parameter. (Read Only)

Auxiliary Input 1 Units Index: Device Description units

code index for the engineering unit descriptor for the

associated block value. (Writable, changes units

associated with the sub-index).

This sub-index can have two values, the absolute

value of the input expressed in milliamps or a percentage

value based on the range of the input.

Auxiliary Input 1 High Limit: The high limit value

associated with the event. (Writable, sets the upper

limit associated with the event.)

Auxiliary Input 1 Low Limit: The low limit value

associated with the event. (Writable, sets the lower

limit associated with the event.)

Auxiliary Input 1 Filter: Number of times for which the

value must be in a limit condition before an event will

be recorded. (Writable, used to filter the event.)

Auxiliary Input 1 Options: Status / options sub-index.

(Writable per section 4.2.3.4 above)

Auxiliary Analog Input 2: The parameter associated

with the 0 - 10 VDC analog input. This parameter is

composed of the following sub-indices:

Note: This parameter has no effect on the device.

The information is received and processed by the

block and passed on to the host via an Analog

Input function block. This parameter can generate

alerts based on the analog input value.

Auxiliary Input 2 Status: The status sub-index associated

with the value sub-index. This sub-index is status

passed to the connected Analog input block. (Read

Only)

Auxiliary Input 2 Value: The value associated with the

analog input. This sub-index is the value passed to the

connected Analog input block. (Read Only)

Auxiliary Input 2 100% Engineering Units: The

engineering unit value which represents the upper end

of range of the associated block parameter. (Read

Only)

Auxiliary Input 2 0% Engineering Units: The engineering

unit value which represents the lower end of range

for the associated block parameter. (Read Only)

Auxiliary Input 2 Units Index: Device Description units

code index for the engineering unit descriptor for the

associated block value. (Writable, changes units

associated with the sub-index).

This sub-index can have two values, the absolute

value of the input expressed in Volts DC or a percentage

value based on the range of the input.

Auxiliary Input 2 High Limit: The Hi Limit value

associated with the event. (Writable, sets the upper

limit associated with the event.)

Auxiliary Input 2 Low Limit: The Lo Limit value

associated with the event. (Writable, sets the lower

limit associated with the event.)

Auxiliary Input 2 Filter: Number of times for which the

value must be in a limit condition before an event will

be recorded. (Writable, used to filter the event.)

Auxiliary Input 2 Options: Status / options sub-index.

(Writable per section 4.2.3.4 above)


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

4.4 Function Block Default Instantiation Mapping

The following table defines the function blocks for the module. The table also lists the base index of the function

blocks in the Object Dictionary. Refer to section 4.5 for information on how the blocks can be assigned to channels

for information processing.

Table 4-2. Function Block Mapping

Block Base

Resource 1000

Transducer - Control 1100

Transducer - Auxiliary 1200

Discrete Input (DI) 1300

Discrete Input (DI) 1400

Discrete Output (DO) 1500

Analog Input (AI) 1600

Analog Input (AI) 1700

4.5 Channel Mapping

The function blocks within the module use the Channel parameter to determine the data they will process. Different

channels provide different data and require different blocks in order to handle the data. The fieldbus interface

limits the choice of channel numbers to those allowed by the block for the particular device.

Note: Channels not available in the device are not settable within the block.

Refer to the block descriptions in section 7 for more information on channels in the I/O blocks.

Table 4-3. Function Block Channel Mapping

Chan Parameter BlockType

2 Final Position Value AI

3 Final Value DO DO

4 Final Position Value DO DI

7 Close Input DI

8 Open Input DI

9 Temperature AI

24 Auxiliary Analog Input 1 AI

25 Auxiliary Analog Input 2 AI

4.5.1 Chan 2 - Output Command Readback

This channel provides the current valve travel value

as a percentage of the input range where 0% is

closed and 100% is fully open. This channel is

connected to an Analog Input block in order to

publish the information on the bus.

4.5.2 Chan 3 - Discrete Output Command

This channel is the discrete command to the device

in the form of “Open” and “Close”. This channel is

connected to a Discrete Output block in order to

subscribe to information on the bus.

4.5.3 Chan 4 - Discrete Output Command

Readback

This channel is similar to channel 2 in the sense that

it provides the travel value for the valve expressed as

a discrete value in the form of “Open”, “Closed”,

“Opening”, “Closed”, “Stopped”. This channel is

connected to a Discrete Input block in order to

publish the information on the bus.

4.5.4 Chan 7 & 8 - Limit Switch Input Channels

The Switch Input channels are used to indicate the

state of the Limit Switches. The value for a switch is:

“On” - Indicates that the Limit Switch is active.

“Off” - Indicates that the Limit Switch is inactive.

These channels are connected to a Discrete Input

blocks in order to publish the information on the bus.

4.5.5 Chan 9 - Temperature

This is the temperature of the electronics module

expressed in units of degrees centigrade (§C). This

channel is connected to an Analog Input block in

order to publish the information on the bus.

4.5.6 Chan 24 & 25 - Auxiliary Analog Inputs

These are the channels assigned to the analog

inputs into the device. These channels are connected

to Analog Input blocks in order to publish the information

on the bus.

TM

Page 27


Page 28

TM

5 Operations and Maintenance

5.1 Fault State

The fault state parameter, when active, indicates a

loss of communication to an output block, a fault

promoted to an output block, or loss of a physical

contact. If the fault state is active, the output function

blocks perform their Fault State actions. Selecting

the feature Fault State enables the ability to manually

set and clear the fault state of the device. Setting

the Set Fault State parameter to “Set” manually

places the instrument in the fault state. Setting the

Clear Fault State parameter to “Clear” clears the

device fault state if no faults are currently active. You

can test the actions the output blocks will perform by

manually setting the fault state active.

5.2 Restart Method

The following method is provided with the FieldQ

Module Device Description:

Restart

Method Description:

Master Reset - Available via the Resource Block,

the Master Reset method is required for restarting

the switchbox without removing power. It also

allows the user to set data within the switchbox to

its default state. In addition to restarting the

switchbox, this method also performs switchbox

integrity tests to verify that it is acceptable to

restart the switchbox. This method is only available

via the Resource Block and is described in detail

in the detailed setup section (section 4.1).

5.3 Restarting the Module

You can restart the module via three different mechanisms.

Depending on which restart option is used; the

communication links, static parameters, etc. may be

affected. However, due to the effect that a restart can

have on the module, and therefore the process,

restarting the module should be used cautiously.

WARNING

Restarting the FieldQ may cause loss of control

of the process.

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

5.3.1 Software Restart

There are three different Restart options, they are

“Restart Resource”, “Restart Processor”, and “Restart

with Defaults”. The following is a brief description

for each of the restart options:

Restart Resource - Performing a “Restart Resource”

has no observable effect on the module

resetting the dynamic variables in the Function

Blocks. However, the dynamic variable within the

module are reset and this could cause a “bump” in

your process.

Restart Processor - Performing a “Restart Processor”

has the same effect as removing power from

the module and re-applying power. This is typically

used to restart the Foundation Fieldbus Interface

card should the Interface Card and the Module I/O

card get out of sync due to incorrect power application.

Restart with Defaults - Performing a “Restart with

Defaults” should be done with care. This restart

sets the static parameters of the function blocks in

the module to their default state. It also disconnects

all links within the module. After performing a

“Restart with Defaults”, a “Restart Processor”

should be performed. Within the FieldQ Series of

modules, the “Restart with Defaults” option is the

only option that will read certain data from the

FieldQ Communications board.

The following list contains the parameters that are set

to their default value as part of the “Restart with

Defaults” command. Refer to section 6 for a description

of the parameters and their default values. The

parameters are:

Action Type

Block Mode

Static Revision

Strategy

Tag Description

The Transducer Block Tag is also set to a fixed value

as follows:

Block Tag = “TRANSDUCERxxxxx” where “xxxxx”

is spaces


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

5.3.2 Restart Results

When the Fieldbus Interface is restarted, it attempts

to communicate with the IO board by reading and

downloading initial startup parameters. If the Interface

Board cannot communicate with the IO board,

the Transducer Blocks will remain in “Out-Of-Service”

and report an “Initialization Fault” via the I/O

Status parameter in the Transducer Blocks. This fault

will also be propagated to the readback parameter of

the Output Function block connected to the Transducer

Block. To clear the fault, verify the FieldQ has

power and the Fieldbus Interface is connected

properly to the FieldQ. Reset the Fieldbus Interface

(see section 5.3) and verify the problem has cleared.

If not, refer to the FieldQ Maintenance and Troubleshooting

Manual for assistance.

5.4 Status/Readback

The I/O Status and Final Position Value parameters

indicate the health of the FieldQ. These parameters

provide a functional status (I/O status) as well as a

positional status (Final Position Value). The Final

Position Value - DO parameter is provided as a

Channel within the FieldQ and can be assigned to a

separate Discrete Input function Block. However, to

save communication and Function Block resources,

the information is automatically passed to the Output

Block via the Final Position Value - DO parameter

and is sent to the control block via the output block’s

Back Cal Out parameter.

Final Position Value - Discrete provides a positional

indication of the module as “Opened”, “Closed”,

“Opening”, “Closing” or “Stopped”. The limit

switches within the FieldQ, in conjunction with the

command issued, determine these values. The

status sub-index of this command is described

below in section 4.4.3.

I/O Status provides a functional indication of the

module status. The following applies to this status:

I/O Communications Fault - This is an indication that

the Fieldbus Board cannot communicate with the

FieldQ Comm Board. This is usually indicative of the

FieldQ not having power (the Fieldbus Interface is

powered by the bus, independently from the FieldQ). It

can also indicate a problem with the interface cable

between the Fieldbus Interface Board and the FieldQ I/

O Board.

I/O Initialization Failure - When the Fieldbus Interface

goes through a Restart, either by cycling power or via

the Resource Block Restart parameter, it attempts to

download/upload initialization data to/from the FieldQ

Com-board. If the Fieldbus Interface cannot communicate

with the FieldQ Comm Board or the upload/

download generates an error, then this status flag is

set. This error indication will be cleared once the

Fieldbus Interface can initialize the Comm Board.

Limit Switch Fault - This status indicates that a fault

exists in the Limit Switch function of the device.

Initializaing the device may clear the fault. If not, then

the FF function module may need to be replaced.

Unit Recognizing Active - This status indicates that the

“Recognizing” function of the device is active.

5.5 Status Sub-index

The Status sub-index is available in two forms as

defined in the following sections. The parameters are

grouped as Command/Position parameters and

Other Parameters. The Status is the same for each

parameter in a group. The Status sub-index is

divided into three components: 1) Quality; 2) Quality

Substatus; 3) Limit. Refer to the Fieldbus Foundation

specifications and Appendix TBD for a more detailed

description of the Status attribute. The valid Status

values for the Transducer Block are described below.

5.5.1 Command/Position Parameters

The Command/Position parameters are those

parameters that affect the desired position of the

module or reflect the position of the module. The

status for these parameters can have the following

values:

- “Good Non Cascade, Not Limited” - Normal

status

- “Bad, Device Failure” - Communications Fault or

Initialization failure on startup. All blocks will also

be out-of-service.

5.5.2 Other Parameters

The other parameters are those parameters that do

not affect the desired position of the module or reflect

the position of the module. The status for these

parameters can have the following values:

- “Good Non Cascade, Not Limited” - Normal

status

TM

Page 29


Page 30

TM

6 Block Descriptions

6.1 What is a Block?

A block is the basic unit of automation available in the

module. There are three types of blocks: Resource

Block, Transducer Blocks, and Function Blocks.

A device contains only one Resource Block. The

resource Block contains data that is specific to the

hardware that is associated with the resource. There

are no links to this block and the data within the block

is not processed in the way that a Function Block

processes data (i.e. there is nothing to execute). The

parameter set is intended to be the minimum required

for the Function Blocks associated with the

resource in which it resides and to help identify the

device on the network.

A Transducer Block manages data that moves

between a function block and the device input/output

(I/O) such as sensors and position switches that

provide process data for automated process control.

Transducer blocks control access to I/O devices

through a device independent interface and manufacturer

specific parameters defined for use by function

blocks. Transducer blocks also perform functions,

such as calibration and linearization, on I/O data to

convert it to a device independent representation.

The transducer block to function blocks interface is

defined as one or more implementation independent

channels.

A Function Block is defined as an Input/Output (I/O)

function block or as a control block. Control Block

work with the IO block to form a control strategy. IO

function blocks provide the interface between the

device specific transducer block and the host and

control blocks. IO function block accept input data

parameters from or provide output data to a Transducer

Block. They provide the processing necessary,

using algorithm(s) and control parameters that are

part of the function block. In turn, the function block

generates output parameters or accepts input

parameters that can be used by other function blocks

to complete an automated process.

Table 6-1.Identifying acronym

Function Block

Name Acronym

Analog Input AI

Discrete Input DI

Discrete Output DO

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Block parameters define the inputs, outputs, and data

used by a function block. Each parameter is identified

by a parameter name that is unique within the

function block. An index number is also defined for

each parameter.

Access to each parameter depends upon the host

system software. For information on using a specific

host system to modify block parameters, see the

appropriate system documentation.

Resource and Transducer Blocks also use parameter

information. The following sections define the parameters

for the FieldQ Resource and Transducer Blocks.

The parameter information is provided in the following

format:

Label: The parameter string as defined by the device

description (DD) for the device.

Parameter Name: The name of the parameter,

defined by the DD.

Index Number: A unique, numeric identifier, generated

for each parameter indicating its offset from

the start of the parameter list for the block. The first

index number is 1..

Mode: Indicates the mode the block needs to be in in

order to modify the parameter.

Range: Represents the range of values the parameter

can assume.

Initial Value: The value assigned to the parameter

when the FieldQ module is issued a “Restart with

defaults” command, which resets all parameter

values to initial or factory settings.

Units: Engineering units, such as “milliseconds”

(msec) or “cycles”, associated with the parameter.

Device Impact: Indicates what the device will do if

the parameter is changed.

Description: provides a detailed description for the

parameter.

Parameter Structure: When a parameter contains

sub-indices, they are listed in table format following

this definition. The data in the table is defined using

the same definitions as above.

In the following sections, a complete detailed list of all

the parameters in each block is provided. Section 6.2

provides the list of parameters for the Resource

Block, section 6.3 provides the list of parameters for

the Control Transducer Block, and section 6.4 provides

the parameters for the Auxiliary Transducer

Block


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

6.2 Resource Block

6.2.1 Parameter List

Table 6-1 Parameter Index is a list of the parameters in the Resource Block listed by index number. Refer to

section 6.2.3 for a detailed description of each parameter in Alphabetic order.

Table 6-2 Parameter Index

Label Index Label Index

Static Revision 1 License String 43

Tag Description 2 TB License Options 44

Strategy 3 FB License Options 45

Plant Unit 4 Diagnostics Options 46

Block Mode 5 Misc Options 47

Block Error 6 Software Revision - Major 48

Resource State 7 Software Revision - Minor 49

Test Read/Write 8 Software Revision - Build 50

DD Resource 9 Software Revision - All 51

Manufacturer ID 10 Hardware Revision 52

Device Type 11 Output Board Serial Number 53

Device Revision 12 Final Assembly Number 54

DD Revision 13 Detailed Status 55

Grant / Deny 14 Summary Status 56

Hardware Types 15 Message Date 57

Restart 16 Message Text 58

Features Available 17 Self Test 59

Features Selected 18 Write Lock Definition 60

Cycle Type Available 19 Save Configuration Now 61

Cycle Type Selected 20 Save Configuration Blocks 62

Min Cycle Time 21 Start With Defaults 63

Memory Size 22 Simulate Jumper Status 64

Min NV Cycle Time 23 Security Jumper Status 65

Free Space 24 Simulate Jumper State 66

Free Time 25 Download Mode 67

RCas Time-Out 26 Recommended Action 68

ROut Time-Out 27 Failed Alerts - Priority 69

Fault State 28 Failed Alerts - Enabled 70

Set Fault State 29 Failed Alerts - Suppressed 71

Clear Fault State 30 Failed Alerts - Active 72

Max Alerts Allowed 31 Failed Alerts - Alarm 73

Max Alerts Possible 32 Maintenance Alerts - Priority 74

Confirm Time 33 Maintenance Alerts - Enabled 75

Write Lock 34 Maintenance Alerts - Suppressed 76

Update Event 35 Maintenance Alerts - Active 77

Block Alarm 36 Maintenance Alerts - Alarm 78

Alarm Summary 37 Advisory Alerts - Priority 79

Acknowledge Option 38 Advisory Alerts - Enabled 80

Write Priority 39 Advisory Alerts - Suppressed 81

Write Alarm 40 Advisory Alerts - Active 82

ITK Version 41 Advisory Alerts - Alarm 83

Private Label Distributor 42 Health Index 84

TM

Page 31


Page 32

TM

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

6.2.2 Parameter Name to Label Lookup Table

Throughout this document, parameters are referred to by their common name or label. However, not all interface

systems support the use of the parameter label and instead use the parameter name when referring to the block

parameters. The following table is provided as a cross-reference of the Resource Block parameter name to the

parameter label.

Table 6-3 Parameter Name to Label Cross reference

Name Index Label Name Index Label

ST_REV 1 Static Revision DEV_STRING 43 License String

TAG_DESC 2 Tag Description XD_OPTIONS 44 TB License Options

STRATEGY 3 Strategy FB_OPTIONS 45 FB License Options

ALERT_KEY 4 Plant Unit DIAG_OPTIONS 46 Diagnostics Options

MODE_BLK 5 Block Mode MISC_OPTIONS 47 Misc Options

BLOCK_ERR 6 Block Error RB_SFTWR_REV_MAJOR 48 Software Revision - Major

RS_STATE 7 Resource State RB_SFTWR_REV_MINOR 49 Software Revision - Minor

TEST_RW 8 Test Read/Write RB_SFTWR_REV_BUILD 50 Software Revision - Build

DD_RESOURCE 9 DD Resource RB_SFTWR_REV_ALL 51 Software Revision - All

MANUFAC_ID 10 Manufacturer HARDWARE_REV 52 Hardware Revision

DEV_TYPE 11 Device Type OUTPUT_BOARD_SN 53 Output Board Serial Number

DEV_REV 12 Device Revision FINAL_ASSY_NUM 54 Final Assembly Number

DD_REV 13 DD Revision DETAILED_STATUS 55 Detailed Status

GRANT_DENY 14 Grant / Deny SUMMARY_STATUS 56 Summary Status

HARD_TYPES 15 Hardware Types MESSAGE_DATE 57 Message Date

RESTART 16 Restart MESSAGE_TEXT 58 Message Text

FEATURES 17 Features Available SELF_TEST 59 Self Test

FEATURE_SEL 18 Features Selected DEFINE_WRITE_LOCK 60 Write Lock Definition

CYCLE_TYPE 19 Cycle Type Available SAVE_CONFIG_NOW 61 Save Configuration Now

CYCLE_SEL 20 Cycle Type Selected SAVE_CONFIG_BLOCKS 62 Save Configuration Blocks

MIN_CYCLE_T 21 Min Cycle Time START_WITH_DEFAULTS 63 Start With Defaults

MEMORY_SIZE 22 Memory Size SIMULATE_IO 64 Simulate Status

NV_CYCLE_T 23 Min NV Cycle Time SECURITY_IO 65 Security IO

FREE_SPACE 24 Free Space SIMULATE_STATE 66 Simulate State

FREE_TIME 25 Free Time DOWNLOAD_MODE 67 Download Mode

SHED_RCAS 26 RCas Time-Out RECOMMENDED_ACTION 68 Recommended Action

SHED_ROUT 27 ROut Time-Out FAILED_PRI 69 Failed Alerts - Priority

FAULT_STATE 28 Fault State FAILED_ENABLE 70 Failed Alerts - Enabled

SET_FSTATE 29 Set Fault State FAILED_MASK 71 Failed Alerts - Suppressed

CLR_FSTATE 30 Clear Fault State FAILED_ACTIVE 72 Failed Alerts - Active

MAX_NOTIFY 31 Max Alerts Allowed FAILED_ALM 73 Failed Alerts - Alarm

LIM_NOTIFY 32 Max Alerts Possible MAINT_PRI 74 Maintenance Alerts - Priority

CONFIRM_TIME 33 Confirm Time MAINT_ENABLE 75 Maintenance Alerts - Enabled

WRITE_LOCK 34 Write Lock MAINT _MASK 76 Maintenance Alerts - Suppressed

UPDATE_EVT 35 Update Event MAINT _ACTIVE 77 Maintenance Alerts - Active

BLOCK_ALM 36 Block Alarm MAINT _ALM 78 Maintenance Alerts - Alarm

ALARM_SUM 37 Alarm Summary ADVISE_PRI 79 Advisory Alerts - Priority

ACK_OPTION 38 Acknowledge Option ADVISE_ENABLE 80 Advisory Alerts - Enabled

WRITE_PRI 39 Write Priority ADVISE _MASK 81 Advisory Alerts - Suppressed

WRITE_ALM 40 Write Alarm ADVISE _ACTIVE 82 Advisory Alerts - Active

ITK_VER 41 ITK Version ADVISE _ALM 83 Advisory Alerts - Alarm

DISTRIBUTOR 42 Private Label Distributor HEALTH_INDEX 84 Health Index


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

6.2.3 Resource Block Parameters (Alphabetical by Label)

Label: Acknowledge Option

Parameter Name : ACK_OPTION

Index Number : 38

Mode : All

Range

0 : Auto Acknowledge Disabled

1 : Auto Acknowledge Enabled

Initial Value : 0

Units : NA

Device Impact: when enabled, the device automatically

acknowledges alerts sent to the host.

Description: Selection of whether alerts associated

with the block will be automatically acknowledged.

Label: Advisory Alerts - Active

Parameter Name: ADVISE_ACTIVE

Index Number: 82

Mode: All

Range: NA

Initial Value: 0

Units: E

Device Impact: Read Only, No Impact on the Device

Description: Enumerated list of advisory conditions

currently active within a device.

Label: Advisory Alerts - Alarm

Parameter Name: ADVISE_ALM

Index Number: 83

Mode: ALL

Device Impact: Read Only, No Impact on the Device

Description: Parameter used to report the Alarm to

the host.

Parameter Structure:

Sub- Name Range Units Initial Description

index Value

.1 Unacknow- 0:Undefined

ledged 1:Acknowledged

2:Unacknowledged

.2 Alarm State 0:Undefined 0

1:Clear

- Reported

2:Clear

- Not reported

3:Active

- Reported

4:Active

- Not reported

.3 Time Stamp

.4 Subcode 0

.5 Value 0

Label: Advisory Alerts - Enabled

Parameter Name: ADVISE_ENABLE

Index Number: 80

Mode: All

Range: NA

Initial Value: 0

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: An indication of the Advisory Alerts that

are enabled. A condition is “Enabled” when its

corresponding bit is active

Label: Advisory Alerts - Priority

Parameter Name: ADVISE_PRI

Index Number: 79

Mode: All

Range: 0-15

Initial Value: 0

Units: None

Device Impact: Determines the priority associated

with the Advisory Alerts.

Description: Designates the alarming priority of the

Advisory Alerts. All conditions within the Advisory

Alerts parameter will have the same priority. A value

of 0 effectively disables Advisory Alerts. A value of 1

effectively suppresses all the Advisory Alerts, a value

of 2 or greater allows the Advisory Alerts to be

processed. The priority value is also passed to the

host via a sub-index in the Advisory Alarm parameter.

Label: Advisory Alerts - Suppressed

Parameter Name: ADVISE_MASK

Index Number: 81

Mode: All

Range: NA

Initial Value: 0

Units: NA

Device Impact: Prevents active conditions from

being reported.

Description: Provides a means of suppressing the

reporting of Advisory Alerts. When a condition is

suppressed, it is indicated in the Advisory Alerts -

Active parameter, however it is not reported to the

host via the Advisory Alerts - Alarm parameter.

TM

Page 33


Page 34

TM

Label: Alarm Summary

Parameter Name: ALARM_SUM

Index Number: 37

Mode: All

Range: NA

Initial Value: NA

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: The current alert status, unacknowledged

states, unreported states, and disabled states

of the alarms associated with the function block. This

summary is associated with the Resource Block

alarms as defined by the Fieldbus standards and is

not associated with PlantWeb Alerts.

Label: Block Alarm

Parameter Name: BLOCK_ALM

Index Number: 36

Mode: ALL

Device Impact: Read Only, No Impact on the Device

Description: Parameter used to report the Alarm to

the host.

Parameter Structure:

Sub- Name Range Units Initial Description

index Value

.1 Unacknow- 0:Undefined

ledged 1:Acknowledged

2:Unacknowledged

.2 Alarm State 0:Undefined 0

1:Clear

- Reported

2:Clear

- Not reported

3:Active

- Reported

4:Active

- Not reported

.3 Time Stamp

.4 Subcode 0

.5 Value 0

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Block Error

Parameter Name: BLOCK_ERR

Index Number: 6

Mode: All

Range: The following are the errors defined for this

parameter, however, not all the errors are applicable

to the Resource Block.

0: Other

1: Block Configuration Error

2: Link Configuration Error

3: Simulate Active

4: Local Override

5: Device Fail-Safe Set

6: Device needs Maintenance Soon

7: Input Failure / Bad PV

8: Output Failure

9: Memory Failure

10: Lost Static Data

11: Lost NV Data

12: Readback Check Failed

13: Device needs Maintenance Now

14: Power-up

15: Out-of-Service

Initial Value: 0

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: This parameter reflects the error status

associated with the hardware or software components

associated with a block. It is a bit string, so that

multiple errors may be shown.


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Block Mode

Parameter Name: MODE_BLK

Index Number: 5

Mode: ALL

Range:

7: Out-of-service (O/S)

3: Automatic (AUTO)

Initial Value: 0x80, 0x80, 0x88, 0x08

Units:

Device Impact: Sets the mode of the block. Can

cause the block to stop processing.

Description:

All blocks have a mode parameter, which determines

the source of the set point, the destination

of the output, and how the block executes. The

ability to modify a block parameter is determined

by the mode. The mode required to change the

parameter is listed in the description for each

parameter.

The block mode is determined by the Block Mode

parameter (parameter name MODE_BLK). It is a

structured parameter composed of the subindexes:

actual, target, permitted, and normal. The

following describes each of the sub-indexes:

Permitted mode - (sub-index 3) The Permitted Mode

defines the modes allowed for the block. This parameter

is set by the user or host system but is restricted

by the module to modes supported by the module for

the particular block. Any change request to the Target

or Normal sub-index is checked against the permitted

sub-index to ensure the requested mode is permitted.

However, when setting the Permitted mode, there is no

check against any of the other sub-indexes (Normal or

Target modes). Therefore, the module may be in a

Normal or Target mode that is not permitted because

the permitted sub-index was modified after the Normal

or Target mode was set. This will have no effect on the

module until the user attempts to modify the Target or

Normal mode. At this time these sub-indexes are

tested against the Permitted modes, thus the user

cannot change the Normal or Target modes to what

was formerly permitted.

Normal mode - (sub-index 4) The normal mode is the

mode the block should be in during normal operating

conditions. The normal mode is set by the user or host

system and can only be set to a permitted mode (see

permitted mode above). The user or host system can

compare the actual mode to the normal mode and,

based on the results, determine if the block is operating

normally.

Target mode - (sub-index 1) The Target mode is the

mode requested by the user or host system. Only one

mode is allowed to be set and it must be a permitted

mode as defined by the permitted sub-index of the

mode parameter.

Actual mode - (sub-index 2) This is the current mode

of the block and is set by the block, it can not be

modified by the user. The actual mode may differ from

the target modes due to operating conditions of the

block. The actual mode is calculated as part of block

execution.

Changing the block mode requires accessing the

Block Mode parameter. For information on using

the host system to change the block mode via this

parameter, see the appropriate system documentation.

Label: Clear Fault State

Parameter Name: CLR_FSTATE

Index Number: 30

Mode: All

Range: 1 (OFF) or 2 (CLEAR)

Initial Value: Off

Units: NA

Device Impact: Clears the fault state condition within

the device.

Description: Selecting “Clear” clears the device fault

state, if no faults are currently active. See also

Features Select.

Label: Confirm Time

Parameter Name: CONFIRM_TIME

Index Number: 33

Mode: All

Range: 0 to 232

Initial Value: 640,000

Units: 1/32 millisecond

Device Impact: Affects how long the device will wait

before re-sending an alarm to the host.

Description: The time, in milliseconds, the module

waits for confirmation of receipt of a report before

trying again. The module does not retry if Confirm

Time is 0.

Label: Cycle Type Available

Parameter Name: CYCLE_TYPE

Index Number: 19

Mode: All

Range:

0: Scheduled

1: Completion of block execution

2: Manufacturer specific

Initial Value: NA

Units: NA

Device Impact: Read Only

Description: Indicates if function block execution can

be scheduled.

TM

Page 35


Page 36

TM

Label: Cycle Type Selected

Parameter Name: CYCLE_SEL

Index Number: 20

Mode: All

Range:

0: Scheduled

1: Completion of block execution

2: Manufacturer specific

Initial Value: 0

Units: NA

Device Impact: No

Description: Indicates if function block execution can

be scheduled. If bit 0 is active, the function blocks

execute per the function block schedule. Default is

“Scheduled”.

Label: DD Resource

Parameter Name: DD_RESOURCE

Index Number: 9

Mode: All

Range: String

Initial Value: NA

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: String identifying the tag of the resource

that contains the Device Description for this resource.

Label: DD Revision

Parameter Name: DD_REV

Index Number: 13

Mode: All

Range: String

Initial Value: NA

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Revision of the device description (DD)

associated with this device, used by the interface

device to locate the DD file for this device.

Label: Detailed Status

Parameter Name: DETAILED_STATUS

Index Number: 55

Mode: All

Range:

0x00000080 - RAM Integrity Error

0x00000040 - ROM (Flash) Integrity Error

0x00000020 - Register Test Failure

0x00000010 - NV Integrity Error

0x00000008 - HW/SW Incompatible

0x00000004 - Manufacturing Block Integrity Error

0x00000002 - Sensor Transducer Error

0x00000001 - LOI Error

Initial Value: NA

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Additional status bit string

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Device Revision

Parameter Name: DEV_REV

Index Number: 12

Mode: All

Range: NA

Initial Value: NA

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Manufacturer revision number associated

with this device, used by the interface device to

locate the DD file for this device.

Label: Device Type

Parameter Name: DEV_TYPE

Index Number: 11

Mode: All

Range:

0xD3A0 - FieldQ Pneumatic Valve Actuator

Initial Value: D3A0

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Identifies the type of device where this

block is located, used by the interface device to

locate the DD file for this device.

Label: Diagnostics Options

Parameter Name: DIAG_OPTIONS

Index Number: 46

Mode: All

Range: NA

Initial Value: NA

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Indicates which diagnostics licensing

options are enabled.

Label: Download Mode

Parameter Name: DOWNLOAD_MODE

Index Number: 67

Mode: OOS

Range:

0 - Uninitialized

1 - Run Mode

2 - Download Mode

Initial Value: 0

Units: NA

Device Impact: Sets the download mode of the

device. This will stop all IO processing within the

module.

Description: Gives access to the boot block code for

over-the-wire downloads.


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Failed Alerts - Active

Parameter Name: ADVISE_ACTIVE

Index Number: 82

Mode: All

Range: NA

Initial Value: 0

Units: E

Device Impact: Read Only, No Impact on the Device

Description: Enumerated list of Failed conditions

currently active within a device.

Label: Failed Alerts - Alarm

Parameter Name: ADVISE_ALM

Index Number: 83

Mode: ALL

Device Impact: Read Only, No Impact on the Device

Description: Parameter used to report the Alarm to

the host.

Parameter Structure:

Sub- Name Range Units Initial Description

index Value

.1 Unacknow- 0:Undefined

ledged 1:Acknowledged

2:Unacknowledged

.2 Alarm State 0:Undefined 0

1:Clear

- Reported

2:Clear

- Not reported

3:Active

- Reported

4:Active

- Not reported

.3 Time Stamp

.4 Subcode 0

.5 Value 0

Label: Failed Alerts - Enabled

Parameter Name: ADVISE_ENABLE

Index Number: 80

Mode: All

Range: NA

Initial Value: 0

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: An indication of the Failed Alerts that

are enabled. A condition is “Enabled” when its

corresponding bit is active

Label: Failed Alerts - Priority

Parameter Name: ADVISE_PRI

Index Number: 79

Mode: All

Range: 0-15

Initial Value: 0

Units: None

Device Impact: Determines the priority associated

with the Failed Alerts.

Description: Designates the alarming priority of the

Failed Alerts. All conditions within the Failed Alerts

parameter will have the same priority. A value of 0

effectively disables Failed Alerts. A value of 1 effectively

suppresses all the Failed Alerts, a value of 2 or

greater allows the Failed Alerts to be processed. The

priority value is also passed to the host via a subindex

in the Failed Alarm parameter.

Label: Failed Alerts - Suppressed

Parameter Name: ADVISE_MASK

Index Number: 81

Mode: All

Range: NA

Initial Value: 0

Units: NA

Device Impact: Prevents active conditions from

being reported.

Description: Provides a means of suppressing the

reporting of Failed Alerts. When a condition is suppressed,

it is indicated in the Failed Alerts - Active

parameter, however it is not reported to the host via

the Failed Alerts - Alarm parameter.

Label: Fault State

Parameter Name: FAULT_STATE

Index Number: 28

Mode: All

Range:

0: Clear

1: Active

Initial Value: Clear

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Indicates a condition set by loss of

communication to an output block, fault promoted to

an output block, or a physical contact. When the Fault

state is “Active”, the output function blocks perform

their Fault State actions.

TM

Page 37


Page 38

TM

Label: FB License Options

Parameter Name: FB_OPTIONS

Index Number: 45

Mode: All

Range: NA

Initial Value: 0

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Indicates which function block licensing

options are enabled.

Label: Features Available

Parameter Name: FEATURES

Index Number: 17

Mode: All

Range: See Features Available

Initial Value: Device Specific

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: See Features Selected

Label: Features Selected

Parameter Name: FEATURE_SEL

Index Number: 18

Mode: All

Range:

1 - Reports supported

2 - Fault state supported

3 - Soft write lock supported

5 - Output readback supported (Always selected in

FieldQ)

Initial Value: All available

Units: NA

Device Impact: Will enable or disable the features

specified.

Description:

Permits selecting the desired feature from those

that are available. Available features for FieldQ

Series modules include:

Reports - Selecting reports enables alarm and event

reporting. Reporting of specific alarms may be

disabled.

Fault State - Selecting fault state enables the ability to

manually set and clear the fault state.

Soft Write Lock - When selected, permits using the

Write Lock parameter to prevent any external change

to static or nonvolatile parameter values. Block

connections and calculation results will proceed

normally, but the configuration is locked. See also the

Write Lock parameter description.

Output Readback - When selected, permits the

Transducer Block output to be feedback to the

Readback parameter in the Output function block.

Within the FieldQ, this option is always selected.

The default is all features selected.

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Final Assembly Number

Parameter Name: FINAL_ASSY_NUM

Index Number: 54

Mode: All

Range: 0 to 232

Initial Value: 0

Units: NA

Device Impact: No impact to the device

Description: Number used for identification purposes.

Associated with the field device.

Label: Free Space

Parameter Name: FREE_SPACE

Index Number: 24

Mode: All

Range: 0 to 232

Initial Value: Device Specific

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Indicates the percentage of memory

(see parameter 22, Memory Size) available for

additional function blocks.

Label: Free Time

Parameter Name: FREE_TIME

Index Number: 25

Mode: All

Range: 0 to 232

Initial Value: Device Specific

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Percent of the block processing time

that is free to process additional blocks. Because no

more function blocks may be configured in FieldQ

Series modules, this parameter value is 0.

Label: Grant/Deny

Parameter Name: GRANT_DENY

Index Number: 14

Mode: All

Range:

1: Grant

2: Deny

Initial Value: 0

Units: NA

Device Impact: No impact on the device

Description: Options for controlling access of host

computer and local control panels to operating,

tuning and alarm parameters of the block.


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Hardware Revision

Parameter Name: HARDWARE_REV

Index Number: 52

Mode: All

Range: 0 to 255

Initial Value: Device Specific

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Revision of hardware that contains the

Resource Block.

Label: Hardware Types

Parameter Name: HARD_TYPES

Index Number: 15

Mode: All

Range:

0 = Scalar Input

1 = Scalar Output

2 = Discrete Input

3 = Discrete Output

Initial Value: 3

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Indicates the types of hardware available

as channel numbers on this device.

Label: Health Index

Parameter Name: HEALTH_INDEX

Index Number: 84

Mode: All

Range: 0 - 100

Initial Value: 100

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Parameter representing the overall

health of the device, 10 being perfect and 1 being

nonfunctioning. The value will be set based on the

active PWA alarms in accordance with the requirements

stated in “Device Alerts and Health Index

PlantWeb Implementation Rules.” Each device may

implement it own unique mapping between the PWA

parameters and

Label: ITK Version

Parameter Name: ITK_VER

Index Number: 41

Mode: All

Range: 0 to 65535

Initial Value: Set by Fieldbus Foundation

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Indicates the major revision number of

the interoperability test case used in certifying this

device as interoperable. The format and range of the

version number is defined and controlled by the

Fieldbus Foundation. Note: The value of this parameter

will be zero (o) if the device has not been registered

as interoperable by the FF.

Label: License String

Parameter Name: DEV_STRING

Index Number: 43

Mode: All

Range: String

Initial Value: Spaces

Units: NA

Device Impact: No Impact on the Device

Description: Used to load new licensing into the

device. The value can be written but will always be

read back with a value of 0.

Label: Maintenance Alerts - Active

Parameter Name: ADVISE_ACTIVE

Index Number: 82

Mode: All

Range: NA

Initial Value: 0

Units: E

Device Impact: Read Only, No Impact on the Device

Description: Enumerated list of Maintenance

conditions currently active within a device.

Label: Maintenance Alerts - Alarm

Parameter Name: ADVISE_ALM

Index Number: 83

Mode: ALL

Device Impact: Read Only, No Impact on the Device

Description: Parameter used to report the Alarm to

the host.

Parameter Structure:

Sub- Name Range Units Initial Description

index Value

.1 Unacknow- 0:Undefined

ledged 1:Acknowledged

2:Unacknowledged

.2 Alarm State 0:Undefined 0

1:Clear

- Reported

2:Clear

- Not reported

3:Active

- Reported

4:Active

- Not reported

.3 Time Stamp

.4 Subcode 0

.5 Value 0

TM

Page 39


Page 40

TM

Label: Maintenance Alerts - Enabled

Parameter Name: ADVISE_ENABLE

Index Number: 80

Mode: All

Range: NA

Initial Value: 0

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: An indication of the Maintenance Alerts

that are enabled. A condition is “Enabled” when its

corresponding bit is active

Label: Maintenance Alerts - Priority

Parameter Name: ADVISE_PRI

Index Number: 79

Mode: All

Range: 0-15

Initial Value: 0

Units: None

Device Impact: Determines the priority associated

with the Maintenance Alerts.

Description: Designates the alarming priority of the

Maintenance Alerts. All conditions within the Maintenance

Alerts parameter will have the same priority. A

value of 0 effectively disables Maintenance Alerts. A

value of 1 effectively suppresses all the Maintenance

Alerts, a value of 2 or greater allows the Maintenance

Alerts to be processed. The priority value is also

passed to the host via a sub-index in the Maintenance

Alarm parameter.

Label: Maintenance Alerts - Suppressed

Parameter Name: ADVISE_MASK

Index Number: 81

Mode: All

Range: NA

Initial Value: 0

Units: NA

Device Impact: Prevents active conditions from

being reported.

Description: Provides a means of suppressing the

reporting of Maintenance Alerts. When a condition is

suppressed, it is indicated in the Maintenance Alerts

- Active parameter, however it is not reported to the

host via the Maintenance Alerts - Alarm parameter.

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Manufacturer ID

Parameter Name: MANUFAC_ID

Index Number: 10

Mode: All

Range: 0 to 232

Initial Value: 0x564144 (decimal 5,652,804)

Units:

Device Impact: Read Only, No Impact on the Device

Description: The manufacturer of the device where

this block is located, used by the interface device to

locate the DD file for this device. The ID number

assigned by the Fieldbus Foundation for Valve

Automation is 5,652,804 (564144 hex).

Label: Max Alerts Allowed

Parameter Name: MAX_NOTIFY

Index Number: 31

Mode: All

Range: 0 to 255

Initial Value: Set by the manufacturer for the particular

device

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: The maximum number of unconfirmed

alert reports that the module can send without getting

a confirmation. This limit is determined by the amount

of memory available for alert reports. Use Max Alerts

Allow to set a number lower than Max Alerts Possible

to control alert flooding.

Label: Max Alerts Possible

Parameter Name: LIM_NOTIFY

Index Number: 32

Mode: All

Range: 0 to MAX_NOTIFY

Initial Value: MAX_NOTIFY

Units: NA

Device Impact: Changing this parameter sets the

maximum number of unacknowledged alarms to be

supported in the device.

Description: The maximum number of unconfirmed

alert notify reports allowed. See Max Alerts Poss. If

Max Alerts Allow is set to 0, no alerts are reported.

Label: Memory Size

Parameter Name: MEMORY_SIZE

Index Number: 22

Mode: All

Range: 0 to 65535

Initial Value: Device Specific

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Indicates memory, in kilobytes, available

for additional function blocks. Because no more

function blocks may be configured in the module, this

parameter value is 0.


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Message Date

Parameter Name: MESSAGE_DATE

Index Number: 57

Mode: All

Range: String

Initial Value: Spaces

Units: NA

Device Impact: No Impact on the Device

Description: Date associated with the

MESSAGE_TEXT parameter.

Label: Message Text

Parameter Name: MESSAGE_TEXT

Index Number: 58

Mode: All

Range: String

Initial Value: Spaces

Units: NA

Device Impact: No Impact on the Device

Description: Used to indicated changes made by the

user to the device’s installation, configuration or

initialization.

Label: Min Cycle Time

Parameter Name: MIN_CYCLE_T

Index Number: 21

Mode: All

Range: 0 to 232

Initial Value: Device Specific

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: The shortest time in which the device

can execute its function block schedule (macrocycle).

Label: Min NV Cycle Time

Parameter Name: NV_CYCLE_T

Index Number: 23

Mode: All

Range: 0 to 232

Initial Value: Device Specific

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Minimum time interval required to write

parameters to non-volatile memory. Zero indicates

data cannot be written to non-volatile memory.

Label: Misc Options

Parameter Name: MISC_OPTIONS

Index Number: 47

Mode: All

Range: String

Initial Value: Device Specific

Units: NA

Device Impact: Read Only, No Impact on the Device.

Description: Indicates which miscellaneous licensing

options are enabled.

Label: Output Board Serial Number

Parameter Name: OUTPUT_BOARD_SN

Index Number: 53

Mode: All

Range: 0 to 232

Initial Value: Device Specific

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Fieldbus Interface serial number.

Label: Plant Unit

Parameter Name: ALERT_KEY

Index Number: 4

Mode: ALL

Range: 1 to 255

Initial Value: 0

Units: NA

Device Impact: No impact to the device

Description: Identification number of the plant unit.

This information may be used in the host system for

sorting alarms.

Label: Private Label Distributor

Parameter Name: DISTRIBUTOR

Index Number: 42

Mode: All

Range:

0x564144, FieldQ

Initial Value: 0x564144

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Private Label Distributor. Identifies the

company that is responsible for the distribution of this

Field Device to customers.

Label: RCas Time-Out

Parameter Name: SHED_RCAS

Index Number: 26

Mode: All

Range: 0 to 232

Initial Value: 640,000

Units: 1/32 millisecond

Device Impact: Changing this parameter affects the

time limit for loss of communication from a remote

device (not a host).

Description: Time duration, in 1/32 milliseconds, at

which to give up on computer writes to function block

RCas locations. Shed from RCas shall never happen

when Shed RCas is 0.

TM

Page 41


Page 42

TM

Label: Recommended Action

Parameter Name: RECOMMENDED_ACTION

Index Number: 68

Mode: All

Range: 0 to 65535

Initial Value: 0

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Numbered list of recommended actions

displayed with a device alert.

Label: Resource State

Parameter Name: RS_STATE

Index Number: 7

Mode: All

Range: 0 to 255

Initial Value: NA

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Indicates the state of the function

blocks. As shown in figure 1-1, five states are possible:

Start Restart - The module is in this state when

power is applied. In this state the memory and

other hardware necessary for reliable operation is

tested. If all hardware tests pass, the module state

moves to Initialization. If a hardware failure is

detected, the module state changes to Failure.

Initialization - The module can enter this state

from the Start/Restart or Failure states. In the

Initialization state, all unreported function block

alarms are automatically confirmed and acknowledged.

Once the module is considered operational,

block execution is scheduled and the

module state moves to On-line Linking.

Online Linking - In this state, all defined links are

evaluated. Once defined links are established, the

module state changes to Online.

Online - The module will be in this state if it is

operational and all defined links are established. If

one or more defined links are detected as not

established, the state changes to Online linking.

Standby - The module enters this state if the

Resource Block mode is Out of Service. In this

state all function block modes are forced to Out of

Service. The Transducer Block mode is not affected.

When the Resource Block mode is

changed to Auto, the module state changes to

Start Restart.

Failure - This state may be entered from any other

state except Standby. The module moves to this

state whenever a hardware or memory failure is

detected which would prevent reliable operation.

When the failure clears, the module state moves to

Initialization.

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Restart

Parameter Name: RESTART

Index Number: 16

Mode: All

Range:

1: Run

2: Restart resource

3: Restart with defaults

4: Restart processor

Initial Value: 1

Units: NA

Device Impact: Read Only, No Effect on Device

Description: There are four possible initialization

values that can be entered into the Restart parameter.

See Restarting the Module, section 5.3.

Label: ROut Time-Out

Parameter Name: SHED_ROUT

Index Number: 27

Mode: All

Range: 0 to 232

Initial Value: 640,000

Units: 1/32 millisecond

Device Impact: Changing this parameter affects the

time limit for loss of communication from a remote

device (not a host).

Description: Time duration, in 1/32 milliseconds, at

which to give up on computer writes to function block

ROut locations. Shed from ROut shall never happen

when Shed ROut is 0.

Label: Save Configuration Blocks

Parameter Name: SAVE_CONFIG_BLOCKS

Index Number: 62

Mode: All

Range:

Initial Value:

Units:

Device Impact: Read Only, No Impact on the Device

Description: Number of EEPROM blocks that have

been modified since last burn. This value will count

down to zero when the configuration is saved.

Label: Save Configuration Now

Parameter Name: SAVE_CONFIG_NOW

Index Number: 61

Mode: All

Range:

0 - Uninitialized

1 - No save

2 - Burn EEPROM

Initial Value: 0

Units: NA

Device Impact:

Description: Controls saving of configuration in

EEPROM.


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Security Jumper Status

Parameter Name: SECURITY_IO

Index Number: 65

Mode: All

Range:

1 - Jumper off

2 - Jumper on

Initial Value: Hardware Specific

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Status of security jumper/switch.

Label: Self Test

Parameter Name: SELF_TEST

Index Number: 59

Mode: OOS

Range:

0 - Uninitialized

1 - No self test

2 - Self test

Initial Value: 0

Units: NA

Device Impact: Will cause the device to initiate an

internal self test which will stop the control processing

and may change the output state.

Description: Instructs Resource Block to perform

self-test.

Label: Set Fault State

Parameter Name: SET_FSTATE

Index Number: 29

Mode: All

Range:

1: Off

2: Set

Initial Value: 0

Units: NA

Device Impact: Forces the device into its Fault State

condition which will force the output to change

depending on Fault State options within the applicable

Function Block(s)

Description: Allows manually placing the module in

the fault state by selecting SET. See also Features

Select.

Label: Simulate Jumper State

Parameter Name: SIMULATE_STATE

Index Number: 66

Mode: All

Range:

1 - Jumper off, no simulation

2 - Jumper on, no simulation

3 - Jumper on, simulation OK

Initial Value: NA

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: The state of the simulate jumper. See

also Simulate Jumper Status (SIMULATE_IO, 64).

Label: Simulate Jumper Status

Parameter Name: SIMULATE_IO

Index Number: 64

Mode: All

Range:

1 - Jumper switch in off position

2 - Jumper switch in on position

Initial Value: NA

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Status of simulate jumper/switch. See

also Simulate Jumper State (SIMULATE_STATE, 66).

Label: Software Revision - All

Parameter Name: RB_SFTWR_REV_ALL

Index Number: 51

Mode: All

Range: String

Initial Value: Device Specific

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Software revision string containing the

following fields: major revision, minor revision, build,

time of build, day of week of build, month of build, day

of month of build, year of build, initials of builder.

Label: Software Revision - Build

Parameter Name: RB_SFTWR_REV_BUILD

Index Number: 50

Mode: All

Range: 0 to 255

Initial Value: Device Specific

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Build of software used to create the

Resource Block.

Label: Software Revision - Major

Parameter Name: RB_SFTWR_REV_MAJOR

Index Number: 48

Mode: All

Range: 0 to 255

Initial Value: Device Specific

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Major revision of the software used to

create the Resource Block.

Label: Software Revision - Minor

Parameter Name: RB_SFTWR_REV_MINOR

Index Number: 49

Mode: All

Range: 0 to 255

Initial Value: Device Specific

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: Minor revision of the software used to

create the Resource Block.

TM

Page 43


Page 44

TM

Label: Start With Defaults

Parameter Name: START_WITH_DEFAULTS

Index Number: 63

Mode: All

Range:

0 - Uninitialized

1 - do not power up with NV defaults

2 - power up with default node address

3 - power up with pd_tag and node address tag

4 - power up with default data for the entire communications

stack (no application data.

Initial Value: 0

Units: NA

Device Impact: Affects how the device will operate

when power is applied (re-applied) to the device.

Description: Controls what defaults are used at

power-up.

Label: Static Revision

Parameter Name: ST_REV

Index Number: 1

Mode: All

Range: 0 to 256

Initial Value: 0

Units: NA

Device Impact: No Impact on the Device

Description:

Label: Strategy

Parameter Name: STRATEGY

Index Number: 3

Mode: ALL

Range: 0 to 65535

Initial Value: 0

Units: NA

Device Impact: No impact to the device

Description: This parameter permits the strategic

grouping of blocks so a host system operator can

identify where the block is located. The blocks may

be grouped by plant area, plant equipment, or

process. This data is not checked or processed by

the block.

Label: Summary Status

Parameter Name: SUMMARY_STATUS

Index Number: 56

Mode: All

Range:

0 - Uninitialized

1 - No repair needed

2 - Repairable

3 - Call service center

Initial Value: 0

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: A number indicating device repair

status.

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Tag Description

Parameter Name: TAG_DESC

Index Number: 2

Mode: ALL

Range: String

Initial Value: all spaces

Units: NA

Device Impact: No impact to the device

Description: A unique description for the Resource

Block. The tag description must be unique for each

block within a system.

Label: TB License Options

Parameter Name: XD_OPTIONS

Index Number: 44

Mode: All

Range: Device Specific

Initial Value: Device Specific

Units: NA

Device Impact:

Description: Indicates which Transducer Block

licensing options are enabled.

Label: Test Read/Write

Parameter Name: TEST_RW

Index Number: 8

Mode: All

Range: Device Specific

Initial Value: Device Specific

Units: NA

Device Impact: Used only during conformance

testing

Description: Read/write test parameter - used only

for conformance testing.

Parameter Structure: Per Fieldbus Foundation

Specifications

Label: Update Event

Parameter Name: UPDATE_EVT

Index Number: 35

Mode: ALL

Range: Per FF DS-73

Initial Value: Per FF DS-73

Units: Per FF DS-73

Device Impact: Read only, No Impact on the Device

Description: Alert generated by a change to static

data,


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Write Alarm

Parameter Name: WRITE_ALM

Index Number: 40

Mode: All

Range: Per FF DS-72

Initial Value: Per FF DS-73

Units: Per FF DS-73

Device Impact: Read Only, No Impact on the Device

Description: This alert is generated if the write lock

parameter is cleared.

Parameter Structure: Per Fieldbus Foundation

Specifications

Label: Write Lock

Parameter Name: WRITE_LOCK

Index Number: 34

Mode: All

Range:

1 - Not Locked

2 - Locked

Initial Value: 1

Units: NA

Device Impact:

Description: If Locked, no writes from anywhere are

allowed, except to unlock Write Lock. When locked,

block inputs will continue to be updated.

Label: Write Lock Definition

Parameter Name: DEFINE_WRITE_LOCK

Index Number: 60

Mode: OOS

Range:

0 - Uninitialized

1 - Everything locked

2 - Physical device locked

Initial Value: 0

Units: NA

Device Impact:

Description: Enumerated value describing the

implementation of the WRITE_LOCK parameter.

Label: Write Priority

Parameter Name: WRITE_PRI

Index Number: 39

Mode: All

Range: 0 to 15

Initial Value: 0

Units: NA

Device Impact: No Impact on the device other than

to change the priority of the alarm.

Description: Priority of the alarm generated by

setting Write Lock to NOT LOCKED.

TM

Page 45


Page 46

TM

6.3 Control Transducer Block

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

6.3.1 Parameter List

Table 6-3 Parameter Index is a list of the parameters in the Resource Block listed by index number. Refer to

section 6.3.3 for a detailed description of each parameter in Alphabetic order.

Table 6-4 Parameter Index

Label Index Label Index

Static Revision 1 Shutdown Options 36

Tag Description 2 Open Input 37

Strategy 3 Close Input 38

Alert Key 4 Reserved 39

Mode Block 5 Temperature 40

Block Error 6 Initialization Record 41

Update Event 7 Reserved 42

Block Alarm 8 Reserved 43

Transducer Directory 9 Cycle Count Set Point 44

Transducer Type 10 Cycle Count Solenoid 45

Transducer Error 11 Cycle Count Actuator 46

Collection Directory 12 Cycle Count Valve 47

Reserved 13 Reserved 48

Final Value DO 14 Time In Position 49

Reserved 15 Open Break Time 50

Reserved 16 Close Break Time 51

Reserved 17 Open Travel Time 52

Final Position Value 18 Close Travel Time 53

Final Position Value DO 19 Reserved 54

Reserved 20 Reserved 55

Reserved 21 Position Feedback 56

Reserved 22 Reserved 57

Actuator Fail Action 23 Reserved 58

Actuator Man Id 24 Reserved 59

Actuator Model Num 25 Deadband 60

Actuator Serial Number 26 Control Type 61

Valve Manufacturer Id 27 Reserved 62

Valve Model Number 28 Reserved 63

Valve Serial Number 29 Reserved 64

Valve Type 30 Reserved 65

Initialization Location 31 Low Range 66

Initialization Date 32 High Range 67

Initialization Person 33 Reserved 68

I/O Options 34 Version Information 69

I/O Status 35


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

6.3.2 Parameter Name to Label Lookup Table

Throughout this document, parameters are referred to by their common name or label. However, not all interface

systems support the use of the parameter label and instead use the parameter name when referring to the block

parameters. The following table is provided as a cross-reference of the control Transducer Block parameter name

to the parameter label.

Table 6-4 Control Transducer Block Parameter Name to Label Lookup Table

Name Index Label Name Index Label

ACT_FAIL_ACTION 23 Actuator Fail Action XD_CAL_LOC 31 Initialization Location

ACT_MAN_ID 24 Actuator Man Id XD_CAL_WHO 33 Initialization Person

ACT_MODEL_NUM 25 Actuator Model Num INITIALIZATION_RECORD 41 Initialization Record

ACT_SN 26 Actuator Serial Number LOW_RANGE 66 Low Range

BLOCK_ALM 8 Block Alarm OPEN_BREAK_TIME 50 Open Break Time

BLOCK_ERR 6 Block Error OPEN_INPUT 37 Open Input

MODE_BLK 5 Block Mode OPEN_TRAVEL_TIME 52 Open Travel Time

CLOSE_BREAK_TIME 51 Close Break Time ALERT_KEY 4 Plant Unit

CLOSE_INPUT 38 Close Input POSITION_FEEDBACK 56 Position Feedback

CLOSE_TRAVEL_TIME 53 Close Travel Time SHUTDOWN 36 Shutdown Options

COLLECTION_DIRECTORY 12 Collection Directory ST_REV 1 Static Revision

CONTROL_TYPE 61 Control Type STRATEGY 3 Strategy

CYCLE_COUNT_ACT 46 Cycle Count Actuator TAG_DESC 2 Tag Description

CYCLE_COUNT_SP 44 Cycle Count Controller TEMPERATURE 40 Temperature

CYCLE_COUNT_SOL 45 Cycle Count Solenoid TIME_IN_POSITION 49 Time In Position

CYCLE_COUNT_VLV 47 Cycle Count Valve TRANSDUCER_DIRECTORY 9 Transducer Directory

DEADBAND 60 Deadband XD_ERROR 11 Transducer Error

FINAL_POSITION_VALUE 18 Final Position Value TRANSDUCER_TYPE 10 Transducer Type

FINAL_POSITION_VALUE_DO 19 Final Position Value DO UPDATE_EVT 7 Update Event

FINAL_VALUE_DO 14 Final Value DO VALVE_MAN_ID 27 Valve Manufacturer Id

HIGH_RANGE 67 High Range VALVE_MODEL_NUM 28 Valve Model Number

IO_OPTIONS 34 I/O Options VALVE_SN 29 Valve Serial Number

IO_STATUS 35 I/O Status VALVE_TYPE 30 Valve Type

XD_CAL_DATE 32 Initialization Date VERSION_INFORMATION 69 Version Information

TM

Page 47


Page 48

TM

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

6.3.3 Control Transducer Block Parameters

The following is a list of the parameters for the module control Transducer Block. Parameters are listed in alphabetical

order by label. See Table 63 for the alphabetical listing of parameters by name.

Label: Actuator Fail Action

Parameter Name: ACT_FAIL_ACTION

Index Number: 23

Mode: Out of Service

Range: The following actions are possible.

0: Uninitialized

1: Self closing

2: Self opening

3: Hold last

4: Maximum value

5: Minimum value

255: Indeterminate

Initial Value: 0

Units: NA

Device Impact: Changing this parameter may cause

control of the actuator/valve to be reversed such that

open = 0% and closed = 100%

Description: Specifies the action that the actuator

takes in case of failure

Label: Actuator Man Id

Parameter Name: ACT_MAN_ID

Index Number: 24

Mode: All

Range: 0 to 232

Initial Value: 0

Units: NA

Device Impact: No impact to the device

Description: Actuator manufacturer identification in

FOUNDATION fieldbus (mfg ID units). See also

Manufacturer ID in the Resource Block

Label: Actuator Model Num

Parameter Name: ACT_MODEL_NUM

Index Number: 25

Mode: All

Range: String

Initial Value: All Spaces

Units: NA

Device Impact: No impact to the device

Description: Actuator model number

Label: Actuator Serial Number

Parameter Name: ACT_SN

Index Number: 26

Mode: ALL

Range: String

Initial Value: All Spaces

Units: NA

Device Impact: No impact to the device

Description: Actuator serial number

Label: Block Alarm

Parameter Name: BLOCK_ALM

Index Number: 8

Mode: ALL

Device Impact: Read Only, No Impact on the Device

Description: Parameter used to report the Alarm to

the host.

Parameter Structure:

Sub- Name Range Units Initial Description

index Value

.1 Unacknow- 0:Undefined

ledged 1:Acknowledged

2:Unacknowledged

.2 Alarm State 0:Undefined 0

1:Clear

- Reported

2:Clear

- Not reported

3:Active

- Reported

4:Active

- Not reported

.3 Time Stamp

.4 Subcode 0

.5 Value 0


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Block Error

Parameter Name: BLOCK_ERR

Index Number: 6

Mode: All

Range: The following are the errors defined for this

parameter, however, not all the errors are applicable

to the Resource Block.

0: Other

1: Block Configuration Error

2: Link Configuration Error

3: Simulate Active

4: Local Override

5: Device Fail-Safe Set

6: Device needs Maintenance Soon

7: Input Failure / Bad PV

8: Output Failure

9: Memory Failure

10: Lost Static Data

11: Lost NV Data

12: Readback Check Failed

13: Device needs Maintenance Now

14: Power-up

15: Out-of-Service

Initial Value: 0

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: This parameter reflects the error status

associated with the hardware or software components

associated with a block. It is a bit string, so that

multiple errors may be shown.

Label: Block Mode

Parameter Name: MODE_BLK

Index Number: 5

Mode: ALL

Range:

7: Out-of-service (O/S)

3: Automatic (AUTO)

Initial Value: 0x80, 0x80, 0x88, 0x08

Units:

Device Impact: Sets the mode of the block. Can

cause the block to stop processing.

Description:

All blocks have a mode parameter, which determines

the source of the set point, the destination

of the output, and how the block executes. The

ability to modify a block parameter is determined

by the mode. The mode required to change the

parameter is listed in the description for each

parameter.

The block mode is determined by the Block Mode

parameter (parameter name MODE_BLK). It is a

structured parameter composed of the subindexes:

actual, target, permitted, and normal. The

following describes each of the sub-indexes:

Permitted mode - (sub-index 3) The Permitted Mode

defines the modes allowed for the block. This parameter

is set by the user or host system but is restricted

by the module to modes supported by the module for

the particular block. Any change request to the Target

or Normal sub-index is checked against the permitted

sub-index to ensure the requested mode is permitted.

However, when setting the Permitted mode, there is no

check against any of the other sub-indexes (Normal or

Target modes). Therefore, the module may be in a

Normal or Target mode that is not permitted because

the permitted sub-index was modified after the Normal

or Target mode was set. This will have no effect on the

module until the user attempts to modify the Target or

Normal mode. At this time these sub-indexes are

tested against the Permitted modes, thus the user

cannot change the Normal or Target modes to what

was formerly permitted.

Normal mode - (sub-index 4) The normal mode is the

mode the block should be in during normal operating

conditions. The normal mode is set by the user or host

system and can only be set to a permitted mode (see

permitted mode above). The user or host system can

compare the actual mode to the normal mode and,

based on the results, determine if the block is operating

normally.

Target mode - (sub-index 1) The Target mode is the

mode requested by the user or host system. Only one

mode is allowed to be set and it must be a permitted

mode as defined by the permitted sub-index of the

mode parameter.

Actual mode - (sub-index 2) This is the current mode

of the block and is set by the block, it can not be

modified by the user. The actual mode may differ from

the target modes due to operating conditions of the

block. The actual mode is calculated as part of block

execution.

Changing the block mode requires accessing the

Block Mode parameter. For information on using

the host system to change the block mode via this

parameter, see the appropriate system documentation.

TM

Page 49


Page 50

TM

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Close Break Time

Parameter Name: CLOSE_BREAK_TIME

Index Number: 51

Mode: ALL

Device Impact: Can send an alert via PlantWeb alerts when configured to do so.

Description: Parameter for the Close Break Time. The Close Break time is the time from when the IO Card

issues the command to open until the Close Limit switch goes to its inactive state.

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 Close Break Time Value 0 to 2 32 msec Last close break time

[CLOSE_BRK_TIM_VALUE]

.2 Close Break Time High Limit 0 to 2 32 msec 232-2 Hi Limit value

[CLOSE_BRK_TIM_HI_LIMIT]

.3 Close Break Time Low Limit 0 to 2 32 msec 0 Low Limit value

[CLOSE_BRK_TIM_LO_LIMIT]

.4 Close Break Time Filter 5 - 5000 cycles 10 Time period for which value must be in a limit

[CLOSE_BRK_TIM_FILTER] condition before an event will be recorded

.5 Close Break Time Options See section 4.2.3 2 Status / options sub-index

[CLOSE_BRK_TIM_OPTIONS]

.6 Close Break Time Average >0 msec 0 Average close break time

[CLOSE_BRK_AVG_VALUE]

.7 Close Avg Value High Limit 0 to 2 32 Msec Max Average Hi Limit value

[CLOSE_BRK_AVG_HI_LIMIT]

.8 Close Break Time Avg Low Limit 0 to 2 32 Msec 0 Average Low Limit value

[CLOSE_BRK_AVG_LO_LIMIT]

.9 Close Break Time Avg Count 10 to 5000 Cycles 10 Number of break cycles included in average

[CLOSE_BRK_AVG_COUNT]

.10 Close Break Time Avg Max 0 to 2 32 msec Maximum Break time in Average

[CLOSE_BRK_AVG_MAX]

.11 Close Break Time Avg Min 0 to 2 32 msec Minimum Break time in Average

[CLOSE_BRK_AVG_MIN]

.12 Close Break Time Avg Options See section 4.2.3 2 Status / options sub-index

[CLOSE_BRK_AVG_OPTIONS]

Label: Close Input

Parameter Name: CLOSE_INPUT

Index Number: 38

Mode: ALL

Range:

0x00-Inactive/False/Off

0x01-Active/True/On (i.e., Closed)

Initial Value: 0

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: A discrete input to indicate if the close

switch is active.


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Close Travel Time

Parameter Name: CLOSE_TRAVEL_TIME

Index Number: 53

Mode: ALL

Device Impact: Can send an alert via PlantWeb alerts when configured to do so.

Description: Parameter for the Close Travel Time. The Close Travel time is the time from when the Open Limit

switch goes inactive until the Close Limit switch indicates Active.

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 Close Travel Time Value 0 to 2 32 msec Last close travel time

[CLOSE_TVL_TIM_VALUE]

.2 Close Travel Time High Limit 0 to 2 32 msec 232-2 Hi Limit value

[CLOSE_TVL_TIM_HI_LIMIT]

.3 Close Travel Time Low Limit 0 to 2 32 msec 0 Low Limit value

[CLOSE_TVL_TIM_LO_LIMIT]

.4 Close Travel Time Filter 5 - 5000 cycles 10 Time period for which value must be in a limit

[CLOSE_TVL_TIM_FILTER] condition before an event will be recorded

.5 Close Travel Time Options See section 4.2.3 2 Status / options sub-index

[CLOSE_TVL_TIM_OPTIONS]

.6 Close Travel Time Average >0 msec 0 Average close travel time

[CLOSE_TVL_AVG_VALUE]

.7 Close Avg Value High Limit 0 to 2 32 Msec Max Average Hi Limit value

[CLOSE_TVL_AVG_HI_LIMIT]

.8 Close Travel Time Avg Low Limit 0 to 2 32 Msec 0 Average Low Limit value

[CLOSE_TVL_AVG_LO_LIMIT]

.9 Close Travel Time Avg Count 10 to 5000 Cycles 10 Number of travel cycles included in average

[CLOSE_TVL_AVG_COUNT]

.10 Close Travel Time Avg Max 0 to 2 32 Msec Maximum Travel time in Average

[CLOSE_TVL_AVG_MAX]

.11 Close Travel Time Avg Min 0 to 2 32 Msec Minimum Travel time in Average

[CLOSE_TVL_AVG_MIN]

.12 Close Travel Time Avg Options See section 4.2.3 2 Status / options sub-index

[CLOSE_TVL_AVG_OPTIONS]

Label: Collection Directory

Parameter Name: COLLECTION_DIRECTORY

Index Number: 12

Mode: All

Range: 1

Initial Value: 1

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: A directory that specifies the number,

starting indices, and DD Item IDs of the data collections

in each transducer within a Transducer Block.

Label: Control Type

Parameter Name: CONTROL_TYPE

Index Number: 61

Mode: All

Range:

1 : Digital - Bus Control

2 : Manual - Local Control

Initial Value: 1

Units: NA

Device Impact: When in manual allows the device to

be opened and closed with the local keypad.

Description: Used to enable the local keypad and

indicators.

TM

Page 51


Page 52

TM

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Cycle Count - Actuator

Parameter Name: CYCLE_COUNT_ACT

Index Number: 46

Mode: ALL

Device Impact: Can send an alert via PlantWeb alerts when configured to do so.

Description: The number of cycles associated with the actuator. A cycle is a change in state; it is not a change in

state and then back to the original state. Open to Close is one cycle, Close to Open is another.

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 Actuator Cycle Counter 0 to 2 32 Cycles 0 Current Cycle Counter value for actuator

[CYCLE_COUNTER_ACT]

.2 Actuator Cycle Ctr Limit 0 to 2 32 Cycles 2 32 -2 Hi Limit

[COUNTER_ACT_HI_LIMIT]

.3 Actuator Cycle Ctr Options See section 4.2.3 2 Status / options sub-index

[COUNTER_ACT_OPTIONS]

Label: Cycle Count - Controller

Parameter Name: CYCLE_COUNT_SP

Index Number: 44

Mode: ALL

Device Impact: Can send an alert via PlantWeb alerts when configured to do so.

Description: The number of cycles associated with the controller. A cycle is a change in state; it is not a change

in state and then back to the original state. Open to Close is one cycle, Close to Open is another.

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 Controller Cycle Counter 0 to 2 32 Cycles 0 Current Cycle Counter value for actuator

[CYCLE_COUNTER_SP]

.2 Controller Cycle Ctr Limit 0 to 2 32 Cycles 2 32 -2 Hi Limit

[COUNTER_SP_HI_LIMIT]

.3 Controller Cycle Ctr Options See section 4.2.3 2 Status / options sub-index

[COUNTER_SP_OPTIONS]

Label: Cycle Count - Solenoid

Parameter Name: CYCLE_COUNT_SOL

Index Number: 45

Mode: ALL

Device Impact: Can send an alert via PlantWeb alerts when configured to do so.

Description: The number of cycles associated with the solenoid. A cycle is a change in state; it is not a change in

state and then back to the original state. Open to Close is one cycle, Close to Open is another.

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 Solenoid Cycle Counter 0 to 2 32 Cycles 0 Current Cycle Counter value for actuator

[CYCLE_COUNTER_SOL]

.2 Solenoid Cycle Ctr Limit 0 to 2 32 Cycles 2 32 -2 Hi Limit

[COUNTER_SOL_HI_LIMIT]

.3 Solenoid Cycle Ctr Options See section 4.2.3 2 Status / options sub-index

[COUNTER_SOL_OPTIONS]


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Cycle Count - Valve

Parameter Name: CYCLE_COUNT_VLV

Index Number: 47

Mode: ALL

Device Impact: Can send an alert via PlantWeb alerts when configured to do so.

Description: The number of cycles associated with the valve. A cycle is a change in state; it is not a change in

state and then back to the original state. Open to Close is one cycle, Close to Open is another.

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 Valve Cycle Counter 0 to 2 32 Cycles 0 Current Cycle Counter value for actuator

[CYCLE_COUNTER_VLV]

.2 Valve Cycle Ctr Limit 0 to 2 32 Cycles 2 32 -2 Hi Limit

[COUNTER_VLV_HI_LIMIT]

.3 Valve Cycle Ctr Options See section 4.2.3 2 Status / options sub-index

[COUNTER_VLV_OPTIONS]

Label: Deadband

Parameter Name: DEADBAND

Index Number: 60

Mode: All

Range: 0 to 99.9%

Initial Value: 0.5

Units: %

Device Impact: Changes how the module controls

position.

Description: Deadband used by the Positioner.

Defines the maximum error required between

setpoint and the position before the controller will

move to compensate.

Label: Final Position Value

Parameter Name: FINAL_POSITION_VALUE

Index Number: 18

Mode: All

Range: 0-100%

Initial Value: NA

Units: %

Device Impact: Read Only, No impact on the device

Description: Characterized travel value for the

device..

Label: Final Position Value DO

Parameter Name: FINAL_POSITION_VALUE_DO

Index Number: 19

Mode: All

Range:

0x00 Closed

0x01 Opened

0x02 Stopped

0x04 Opening

0x05 Closing

Initial Value: NA

Units: NA

Device Impact: Read Only, No impact on the device

Description: Characterized position in discrete

states.

Label: Final Value DO

Parameter Name: FINAL_VALUE_DO

Index Number: 14

Mode: All

Range:

0x00 Close

0x01 Open

0x02 Stop

Initial Value: NA

Units: NA

Device Impact: Used to command the device to a

specific discrete position.

Description: Discrete set point in discrete states.

Label: High Range

Parameter Name: HIGH_RANGE

Index Number: 67

Mode: All

Range: 0-100%

Initial Value: NA

Units: %

Device Impact: Read Only, no impact on device

Description: Specifies the High value associated

with the travel range as a function of the total range

available from the travel sensor.

TM

Page 53


Page 54

TM

Label: I/O Options

Parameter Name: IO_OPTIONS

Index Number: 34

Mode: Out of Service

Range:

1:Hardware Readback Enable

2:Valve Control Readback Enable

3:Pressure Control Enable

4:Parameter Write Lock Enable

5:No Open Stop Present

6:No Close Stop Present

7:Calculate Torque from Pressure

8:Calculate Torque from AI 1

Initial Value: Depends on hardware config.

Units: NA

Device Impact: Enables or disables optional features

or functionality within the device.

Description: Settable options associated with the

Transducer Block.

Label: I/O Status

Parameter Name: IO_STATUS

Index Number: 35

Mode: ALL

Range:

0x00: None

0x02: Communications Fault

0x04: IO Initialization Fault

0x08: Limit Switch Fault

0x10: Unit Recognizing Active

Initial Value: NA

Units: NA

Device Impact: Read Only, no Impact on device.

Description: Current device status, including status

from I/O card.

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Initialization Date

Parameter Name: XD_CAL_DATE

Index Number: 32

Mode: All

Range: String

Initial Value: Spaces

Units: NA

Device Impact: No Impact on the device

Description: The date the device was last initialized

Label: Initialization Location

Parameter Name: XD_CAL_LOC

Index Number: 31

Mode: All

Range: String

Initial Value: Spaces

Units: NA

Device Impact: No Impact on the device

Description: The location where device was last

initialized

Label: Initialization Person

Parameter Name: XD_CAL_WHO

Index Number: 33

Mode: All

Range: String

Initial Value: Spaces

Units: NA

Device Impact: No Impact on the device

Description: The name of the person to last initialize

the device.


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Initialization Record

Parameter Name: INITIALIZATION_RECORD

Index Number: 41

Mode: Mixed

Device Impact: This command will cause the Device to start its initialization process which in turn will cause the

actuator and valve to move.

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 Initialization Command 0 : No Action - Default value 0 Command to start initialization

[INITIALIZATION_CMD] 1 : Start Zero Point Adjustment

2 : Start Initialization

7 : Reset-Valve Travel

- Errors and Counters

10 : Reset-Internal Control Loop

- Errors and Counters

255: Abort Current Initialization

.2 Initialization Status 0 : Undetermined Initialization Status from device

[INITIALIZATION_STATUS] 1 : Running

2 : Aborted

11 : Time Out

20 : Abort by means of Emergency Override

30 : Zero Point Error

254: Successful

255: No Valid Data

Label: Low Range

Parameter Name: LOW_RANGE

Index Number: 66

Mode: All

Range: 0-100%

Initial Value: NA

Units: %

Device Impact: Read Only, no impact on device

Description: Specifies the Low value associated with the travel range as a function of the total range available

from the travel sensor.

TM

Page 55


Page 56

TM

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Open Break Time

Parameter Name: OPEN_BREAK_TIME

Index Number: 50

Mode: ALL

Device Impact: Can send an alert via PlantWeb alerts when configured to do so.

Description: Parameter for the Open Break Time. The Open Break time is the time from when the IO Card issues

the command to Close until the Open Limit switch goes to its inactive state.

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 Open Break Time Value 0 to 2 32 msec Last open break time

[OPEN_BRK_TIM_VALUE]

.2 Open Break Time High Limit 0 to 2 32 msec 2 32 -2 Hi Limit value

[OPEN_BRK_TIM_HI_LIMIT]

.3 Open Break Time Low Limit 0 to 2 32 msec 0 Low Limit value

[OPEN_BRK_TIM_LO_LIMIT]

.4 Open Break Time Filter 5 - 5000 cycles 10 Time period for which value must be in a limit

[OPEN_BRK_TIM_FILTER] condition before an event will be recorded

.5 Open Break Time Options See section 4.2.3 2 Status / options sub-index

[OPEN_BRK_TIM_OPTIONS]

.6 Open Break Time Average >0 msec 0 Average open break time

[OPEN_BRK_AVG_VALUE]

.7 Open Avg Value High Limit 0 to 2 32 Msec Max Average Hi Limit value

[OPEN_BRK_AVG_HI_LIMIT]

.8 Open Break Time Avg Low Limit 0 to 2 32 Msec 0 Average Low Limit value

[OPEN_BRK_AVG_LO_LIMIT]

.9 Open Break Time Avg Count 10 to 5000 Cycles 10 Number of break cycles included in average

[OPEN_BRK_AVG_COUNT]

.10 Open Break Time Avg Max 0 to 2 32 msec Maximum Break time in Average

[OPEN_BRK_AVG_MAX]

.11 Open Break Time Avg Min 0 to 2 32 msec Minimum Break time in Average

[OPEN_BRK_AVG_MIN]

.12 Open Break Time Avg Options See section 4.2.3 2 Status / options sub-index

[OPEN_BRK_AVG_OPTIONS]

Label: Open Input

Parameter Name: OPEN_INPUT

Index Number: 37

Mode: ALL

Range: 0x00-Inactive/False/Off

0x01-Active/True/On (i.e., Open)

Initial Value: 0

Units:

Device Impact: Read Only, No impact on the Device

Description: Discrete input to indicate if the open switch is active.


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Open Travel Time

Parameter Name: OPEN_TRAVEL_TIME

Index Number: 52

Mode: ALL

Device Impact: Can send an alert via PlantWeb alerts when configured to do so.

Description: Parameter for the Open Travel Time. The Open Travel time is the time from when the Close Limit

switch goes inactive until the Open Limit switch indicates Active.

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 Open Travel Time Value 0 to 2 32 msec Last open travel time

[OPEN_TVL_TIM_VALUE]

.2 Open Travel Time High Limit 0 to 2 32 msec 2 32 -2 Hi Limit value

[OPEN_TVL_TIM_HI_LIMIT]

.3 Open Travel Time Low Limit 0 to 2 32 msec 0 Low Limit value

[OPEN_TVL_TIM_LO_LIMIT]

.4 Open Travel Time Filter 5 - 5000 cycles 10 Time period for which value must be in a

[OPEN_TVL_TIM_FILTER] limit condition before an event will be recorded

.5 Open Travel Time Options See section 4.2.3 2 Status / options sub-index

[OPEN_TVL_TIM_OPTIONS]

.6 Open Travel Time Average >0 msec 0 Average open travel time

[OPEN_TVL_AVG_VALUE]

.7 Open Avg Value High Limit 0 to 2 32 Msec Max Average Hi Limit value

[OPEN_TVL_AVG_HI_LIMIT]

.8 Open Travel Time Avg Low Limit 0 to 2 32 Msec 0 Average Low Limit value

[OPEN_TVL_AVG_LO_LIMIT]

.9 Open Travel Time Avg Count 10 to 5000 Cycles 10 Number of travel cycles included in average

[OPEN_TVL_AVG_COUNT]

.10 Open Travel Time Avg Max 0 to 2 32 msec Maximum Travel time in Average

[OPEN_TVL_AVG_MAX]

.11 Open Travel Time Avg Min 0 to 2 32 msec Minimum Travel time in Average

[OPEN_TVL_AVG_MIN]

.12 Open Travel Time Avg Options See section 4.2.3 2 Status / options sub-index

[OPEN_TVL_AVG_OPTIONS]

Label: Plant Unit

Parameter Name: ALERT_KEY

Index Number: 4

Mode: ALL

Range: 1 to 255

Initial Value: 0

Units: NA

Device Impact: No impact to the device

Description: Identification number of the plant unit. This information may be used in the host system for sorting

alarms.

TM

Page 57


Page 58

TM

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Position Feedback

Parameter Name: POSITION_FEEDBACK

Index Number: 56

Mode: ALL

Device Impact: Read Only, No impact on the device

Description: Structure used to define the type of feedback into the device. Also includes the A/D values for the

High (maximum) feedback value and the Low (minimum) value.

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 Feedback Type 0 : Normal - CCW Bit Enum 0x09 The type of feedback used by the device

[FEEDBACK_TYPE] 1 : Invert - CW

2 : Sliding Stem

3 : Rotary

4 : Non-Contacting

5 : Switches - Internal

6 : Switches - External (DI 1 & 2)

.2 Feedback High N/A Factory A/D value indicating the maximum value

[FEEDBACK_HI] of the position feedback sensor

.3 Feedback Low N/A Factory A/D value indicating the minimum value

[FEEDBACK_LO] of the position feedback sensor

Label: Shutdown Options

Parameter Name: SHUTDOWN

Index Number: 36

Device Impact: Changes the way the device will shut down when a failure occurs or it is commanded to shutdown.

Description: This parameter is used in conjunction with the Output Function Block to condifure how the device

will shutdown if a failure should occur.

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 Shutdown Options 0 : Inactive Bit Enum Settable Options associated with shutting

[SHUTDOWN_OPTIONS] 1 : Active down the transducer block (i.e. ESD or

Failsafe)

.2 Shutdown Value -25% to 125% Enum Fail Safe Value Value to be used when go to value option

[SHUTDOWN_VALUE] is selected

Label: Static Revision

Parameter Name: ST_REV

Index Number: 1

Mode: All

Range: 0 to 256

Initial Value: 0

Units: NA

Device Impact: No Impact on the Device

Description:

Label: Strategy

Parameter Name: STRATEGY

Index Number: 3

Mode: ALL

Range: 0 to 65535

Initial Value: 0

Units: NA

Device Impact: No impact to the device

Description: This parameter permits the strategic

grouping of blocks so a host system operator can

identify where the block is located. The blocks may be

grouped by plant area, plant equipment, or process.

This data is not checked or processed by the block.


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Tag Description

Parameter Name: TAG_DESC

Index Number: 2

Mode: ALL

Range: String

Initial Value: all spaces

Units: NA

Device Impact: No impact to the device

Description: A unique description for the Resource Block. The tag description must be unique for each block

within a system.

Label: Temperature

Parameter Name: TEMPERATURE

Index Number: 40

Device Impact: Can send an alert via PlantWeb alerts when configured to do so.

Description: The temperature as measured on the electronics assembly, expressed in degree centigrade.

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 Temperature Status N/A

[TEMPERATURE_STATUS]

.2 Temperature Value % N/A

[TEMPERATURE_VALUE]

.3 Temperature High Limit 0 - MAX msec MAX Maximum Value, if exceeded for filter

[TEMPERATURE_HI_LIMIT] time, will trigger event

.4 Temperature Low Limit 0 - MAX msec 0 Minimum Value, if below for filter time, will

[TEMPERATURE_LO_LIMIT] trigger event

.5 Temperature Filter 1 - 5000 msec 10 Time period for which value must be in a

[TEMPERATURE_FILTER] limit condition before and event will be

recorded

.6 Temperature Options See section 4.2.3 2 Status / options sub-index

[TEMPERATURE_OPTIONS]

Label: Time In Position

Parameter Name: TIME_IN_POSITION

Index Number: 49

Mode: ALL

Device Impact: Can send an alert via PlantWeb alerts when configured to do so.

Description: Parameter with event to indicate the amount of time, in seconds, the unit has been in its current

position (Open or closed).

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 Time in Position Value 0 to 2 32 sec Time in current position

[TIME_IN_POS_VALUE]

.2 Position High Limit 0 to 2 32 sec Max Maximum value, if exceeded will trigger event

[TIME_IN_POS_HI_LIMIT]

.3 Time in Position Options See section 4.2.3 2 Status / options sub-index

[TIME_IN_POS_OPTIONS]

TM

Page 59


Page 60

TM

Label: Transducer Directory

Parameter Name: TRANSDUCER_DIRECTORY

Index Number: 9

Mode: All

Range: 1, 1

Initial Value: 1, 1

Units: NA

Device Impact: Read Only, No impact to the device

Description: A directory that specifies the number

and starting indices of the transducers in the Transducer

Block. For further information, please refer to

the Transducer Block Application Process Specification

- Part 1 (FF-902).

Label: Transducer Error

Parameter Name: XD_ERROR

Index Number: 11

Mode: All

Range: 0: No error

Initial Value: 0

Units: NA

Device Impact: Read Only, No impact to the device

Description: Extensions to Block Error indicated by

the “Other” bit 0 being set.

Label: Transducer Type

Parameter Name: TRANSDUCER_TYPE

Index Number: 10

Mode: All

Range: 106

Initial Value: 106

Units:

Device Impact: Read Only, No impact to the device

Description: Identifies the type of Transducer Block.

Label: Update Event

Parameter Name: UPDATE_EVT

Index Number: 7

Mode: ALL

Range: Per FF DS-73

Initial Value: Per FF DS-73

Units: Per FF DS-73

Device Impact: Read only, No Impact on the Device

Description: Alert generated by a change to static

data,

Label: Valve Manufacturer ID

Parameter Name: VALVE_MAN_ID

Index Number: 27

Mode: ALL

Range: 0 to 232

Initial Value: 0

Units: NA

Device Impact: No impact to the device

Description: Valve manufacturer identification in

FOUNDATION fieldbus (mfg ID units). See also

Manufacturer ID in the Resource Block

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Valve Model Number

Parameter Name: VALVE_MODEL_NUM

Index Number: 28

Mode: ALL

Range: String

Initial Value: All Spaces

Units: NA

Device Impact: No impact to the device

Description: Valve model number

Label: Valve Serial Number

Parameter Name: VALVE_SN

Index Number: 29

Mode: ALL

Range: String

Initial Value: All Spaces

Units: NA

Device Impact: No impact to the device

Description: Valve serial number

Label: Valve Type

Parameter Name: VALVE_TYPE

Index Number: 30

Mode: ALL

Range:

0:Undefined

1:Linear (General)

2:Rotary (General)

3:Ball

4:V-Ball

5:Globe

6:Butterfly

7:Gate

255:Other

Initial Value: 2

Units: NA

Device Impact: No impact to the device

Description: The valve type. For informational

purposes only. Is not used by internal software.

Label: Version Information

Parameter Name: VERSION_INFORMATION

Index Number: 67

Mode: All

Range: NA

Initial Value: NA

Units: NA

Device Impact: Read Only, No impact to the device

Description:


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

6.4 Auxiliary I/O Transducer Block

6.4.1 Parameter List

Table 65 is a list of the parameters in the Resource

Block listed by index number. Refer to section Error!

Reference source not found. for a detailed description

of each parameter in Alphabetic order.

Table 6-5 Parameter Index

Label Index

Static Revision 1

Tag Description 2

Strategy 3

Alert Key 4

Mode Block 5

Block Error 6

Update Event 7

Block Alarm 8

Transducer Dir 9

Transducer Type 10

Transducer Error 11

Collection Directory 12

I/O Options 13

I/O Status 14

Reserved 15

Reserved 16

Reserved 17

Reserved 18

Reserved 19

Reserved 20

Reserved 21

Reserved 22

Auxiliary Analog Input 1 23

Auxiliary Analog Input 2 24

6.4.2 Parameter Name to Label Lookup Table

Throughout this document, parameters are referred

to by their common name or label. However, not all

interface systems support the use of the parameter

label and instead use the parameter name when

referring to the block parameters. The following table

is provided as a cross-reference of the auxiliary I/O

Transducer Block parameter name to the parameter

label.

Table 6-6 Auxiliary I/O Transducer Block Parameter Name to

Label Lookup Table

Name Index Label

AUX_AI_1_INPUT 23 Auxiliary Analog Input 1

AUX_AI_2_INPUT 24 Auxiliary Analog Input 2

BLOCK_ALM 8 Block Alarm

BLOCK_ERR 6 Block Error

MODE_BLK 5 Block Mode

COLLECTION_DIRECTORY 12 Collection Directory

IO_OPTIONS 13 I/O Options

IO_STATUS 14 I/O Status

ALERT_KEY 4 Plant Unit

ST_REV 1 Static Revision

STRATEGY 3 Strategy

TAG_DESC 2 Tag Description

TRANSDUCER_DIRECTORY 9 Transducer Directory

XD_ERROR 11 Transducer Error

TRANSDUCER_TYPE 10 Transducer Type

UPDATE_EVT 7 Update Event

TM

Page 61


Page 62

TM

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

6.4.3 Auxiliary I/O Transducer Block Parameters

The following is a list of the parameters for the module auxiliary I/O Transducer Block.

Label: Auxiliary Analog Input 1

Parameter Name: AUX_AI_1_INPUT

Index Number: 23

Mode: ALL

Device Impact: This parameter has No Impact on the Device. The information is received and processed by the

block and passed on to the host via an Analog Input function block. This parameter can generate alerts based on

the analog input value.

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 AI 1 Status

.2 AI 1 Value Sub-index.5 Auxiliary Analog Input Number 1 Value

.3 AI 1 100% Engineering Units 20 MA

.4 AI 1 0% Engineering Units 4 MA

.5 AI 1 Units Index 4-20 mA 1211 1211 mA (milliamperes)1342 % (Percent )

.6 AI 1 High Limit 0 to maximum msec Max Maximum value, if exceeded for filter time will

trigger event

.7 AI 1 Low Limit 0 to maximum msec 0 Minimum value, if below for filter time will trigger

event

.8 AI 1 Filter 1 - 5000 sec 10 Time period for which value must be in a limit

condition before an event will be recorded

.9 AI 1 Options See section 4.2.3 2 Status / options sub-index

Label: Auxiliary Analog Input 2

Parameter Name: AUX_AI_2_INPUT

Index Number: 24

Mode: ALL

Device Impact: This parameter has No Impact on the Device. The information is received and processed by the

block and passed on to the host via an Analog Input function block. This parameter can generate alerts based on

the analog input value.

Parameter Structure:

Sub- Label [Name] Range Units Initial Description

index Value

.1 AI 2 Status

.2 AI 2 Value Sub-index.5 Auxiliary Analog Input Number 2 Value

.3 AI 2 100% Engineering Units 20 MA

.4 AI 2 0% Engineering Units 4 MA

.5 AI 2 Units Index 4-20 mA 1240 1240 V (volts)1342 % (Percent )

.6 AI 2 High Limit 0 to maximum msec max Maximum value, if exceeded for filter time will

trigger event

.7 AI 2 Low Limit 0 to maximum msec 0 Minimum value, if below for filter time will

trigger event

.8 AI 2 Filter 1 - 5000 sec 10 Time period for which value must be in a limit

condition before an event will be recorded

.9 AI 2 Options See section 4.2.3 2 Status / options sub-index


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Block Alarm

Parameter Name: BLOCK_ALM

Index Number: 8

Mode: ALL

Device Impact: Read Only, No Impact on the Device

Description: Parameter used to report the Alarm to

the host.

Parameter Structure:

Sub- Name Range Units Initial Description

index Value

.1 Unacknow- 0:Undefined

ledged 1:Acknowledged

2:Unacknowledged

.2 Alarm State 0:Undefined 0

1:Clear

- Reported

2:Clear

- Not reported

3:Active

- Reported

4:Active

- Not reported

.3 Time Stamp

.4 Subcode 0

.5 Value 0

Label: Block Error

Parameter Name: BLOCK_ERR

Index Number: 6

Mode: All

Range: The following are the errors defined for this

parameter, however, not all the errors are applicable

to the Resource Block.

0: Other

1: Block Configuration Error

2: Link Configuration Error

3: Simulate Active

4: Local Override

5: Device Fail-Safe Set

6: Device needs Maintenance Soon

7: Input Failure / Bad PV

8: Output Failure

9: Memory Failure

10: Lost Static Data

11: Lost NV Data

12: Readback Check Failed

13: Device needs Maintenance Now

14: Power-up

15: Out-of-Service

Initial Value: 0

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: This parameter reflects the error status

associated with the hardware or software components

associated with a block. It is a bit string, so that

multiple errors may be shown.

TM

Page 63


Page 64

TM

Label: Block Mode

Parameter Name: MODE_BLK

Index Number: 5

Mode: ALL

Range:

7: Out-of-service (O/S)

3: Automatic (AUTO)

Initial Value: 0x80, 0x80, 0x88, 0x08

Units:

Device Impact: Sets the mode of the block. Can

cause the block to stop processing.

Description:

All blocks have a mode parameter, which determines

the source of the set point, the destination

of the output, and how the block executes. The

ability to modify a block parameter is determined

by the mode. The mode required to change the

parameter is listed in the description for each

parameter.

The block mode is determined by the Block Mode

parameter (parameter name MODE_BLK). It is a

structured parameter composed of the subindexes:

actual, target, permitted, and normal. The

following describes each of the sub-indexes:

Permitted mode - (sub-index 3) The Permitted

Mode defines the modes allowed for the block.

This parameter is set by the user or host system

but is restricted by the module to modes supported

by the module for the particular block. Any change

request to the Target or Normal sub-index is

checked against the permitted sub-index to ensure

the requested mode is permitted.

However, when setting the Permitted mode, there

is no check against any of the other sub-indexes

(Normal or Target modes). Therefore, the module

may be in a Normal or Target mode that is not

permitted because the permitted sub-index was

modified after the Normal or Target mode was set.

This will have no effect on the module until the

user attempts to modify the Target or Normal

mode. At this time these sub-indexes are tested

against the Permitted modes, thus the user cannot

change the Normal or Target modes to what was

formerly permitted.

Normal mode - (sub-index 4) The normal mode is

the mode the block should be in during normal

operating conditions. The normal mode is set by

the user or host system and can only be set to a

permitted mode (see permitted mode above). The

user or host system can compare the actual mode

to the normal mode and, based on the results,

determine if the block is operating normally.

Target mode - (sub-index 1) The Target mode is

the mode requested by the user or host system.

Only one mode is allowed to be set and it must be

a permitted mode as defined by the permitted subindex

of the mode parameter.

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Actual mode - (sub-index 2) This is the current

mode of the block and is set by the block, it can not

be modified by the user. The actual mode may

differ from the target modes due to operating

conditions of the block. The actual mode is calculated

as part of block execution.

Changing the block mode requires accessing the

Block Mode parameter. For information on using

the host system to change the block mode via this

parameter, see the appropriate system documentation.

Label: Collection Directory

Parameter Name: COLLECTION_DIRECTORY

Index Number: 12

Mode: All

Range: 1

Initial Value: 1

Units: NA

Device Impact: Read Only, No Impact on the Device

Description: A directory that specifies the number,

starting indices, and DD Item IDs of the data collections

in each transducer within a Transducer Block.

Label: I/O Options

Parameter Name: IO_OPTIONS

Index Number: 13

Mode: Out of Service

Range:

0:Hardware Readback 1 Enable

1:Hardware Readback 2 Enable

2:Hardware Readback 3 Enable

3:Hardware Readback 4 Enable

4:Valve Control Readback 1 Enable

5:Valve Control Readback 2 Enable

6:Valve Control 1 Enable

7:Valve Control 2 Enable

8:Parameter Write Lock Enable

Initial Value: Depends on hardware config.

Units:

Description: Settable options associated with the

Transducer Block.

Label: I/O Status

Parameter Name: IO_STATUS

Index Number: 14

Mode: ALL

Range:

0:I/O Communications Fault

1:I/O Initialization Fault

2:Aux DO 1

3 - 31:Reserved

Initial Value: 0

Units:

Description: Current device status, including status

from I/O card.


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

Label: Plant Unit

Parameter Name: ALERT_KEY

Index Number: 4

Mode: ALL

Range: 1 to 255

Initial Value: 0

Units: NA

Device Impact: No impact to the device

Description: Identification number of the plant unit.

This information may be used in the host system for

sorting alarms.

Label: Static Revision

Parameter Name: ST_REV

Index Number: 1

Mode: All

Range: 0 to 256

Initial Value: 0

Units: NA

Device Impact: No Impact on the Device

Description:

Label: Strategy

Parameter Name: STRATEGY

Index Number: 3

Mode: ALL

Range: 0 to 65535

Initial Value: 0

Units: NA

Device Impact: No impact to the device

Description: This parameter permits the strategic

grouping of blocks so a host system operator can

identify where the block is located. The blocks may be

grouped by plant area, plant equipment, or process.

This data is not checked or processed by the block.

Label: Tag Description

Parameter Name: TAG_DESC

Index Number: 2

Mode: ALL

Range: String

Initial Value: all spaces

Units: NA

Device Impact: No impact to the device

Description: A unique description for the Resource

Block. The tag description must be unique for each

block within a system.

Label: Transducer Directory

Parameter Name: TRANSDUCER_DIRECTORY

Index Number: 9

Mode: All

Range: 1, 1

Initial Value: 1, 1

Units: NA

Device Impact: Read Only, No impact to the device

Description: A directory that specifies the number

and starting indices of the transducers in the Transducer

Block. For further information, please refer to

the Transducer Block Application Process Specification

- Part 1 (FF-902).

Label: Transducer Error

Parameter Name: XD_ERROR

Index Number: 11

Mode: All

Range: 0: No error

Initial Value: 0

Units:

Description: Extensions to Block Error indicated by

the “Other” bit 0 being set.

Label: Transducer Type

Parameter Name: TRANSDUCER_TYPE

Index Number: 10

Mode: All

Range: 106

Initial Value: 106

Units:

Device Impact: Read Only, No impact to the device

Description: Identifies the type of Transducer Block.

Label: Update Event

Parameter Name: UPDATE_EVT

Index Number: 7

Mode: ALL

Range: Per FF DS-73

Initial Value: Per FF DS-73

Units: Per FF DS-73

Device Impact: Read only, No Impact on the Device

Description: Alert generated by a change to static

data,

TM

Page 65


Page 66

TM

Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003


Reference manual Foundation Fieldbus Function Module

DOC.RM.QM34.1 Rev: A

Sept. 2003

TM

Page 67


EUROPE MIDDLE EAST & AFRICA SOUTH AFRICA

P.O. Box 223 P.O. Box 979

7550 AE Hengelo (O) Isando

Asveldweg 11 1600

7556 BT Hengelo (O) 2 Monteer Road

The Netherlands Isando

Tel. +31 74 256 10 10 South Africa

Fax. +31 74 291 09 38 Tel. +27 11 974 3336

Info.ValveAutomation-EMA@EmersonProcess.com Fax. +27 11 974 7005

Info.ValveAutomation-SA@EmersonProcess.com

GERMANY

Postfach 500155 NORTH & SOUTH AMERICA

D-47870 Willich 9009 King Palm Drive

Siemensring 112 Tampa

D-47877 Willich Florida

Germany 33619

Tel. +49 2154 499660 United States of America

Fax. +49 2154 499 66 13 Tel. +1 936 372 5575

Info.ValveAutomation-BRD@EmersonProcess.com Fax. + 1 281 463 5106

Info.ValveAutomation-USA@EmersonProcess.com

UNITED KINGDOM

6 Bracken Hill SINGAPORE

South West Industrial Estate 28 Third Lok Yang Road

Peterlee Singapore 628016

Co Durham Tel. +65 626 24 515

SR8 2LS Fax. +65 626 80 028

United Kingdom Info.ValveAutomation-AP@EmersonProcess.com

Tel +44 (0) 191 5180020

Fax +44 (0) 191 5180032 Please visit our website for up to date product data.

Info.ValveAutomation-UK@EmersonProcess.com www.FieldQ.com

All Rights Reserved.

We reserve the right to modify or improve the designs or specifications of the products

mentioned in this manual at any time without notice. Emerson Process Management

does not assume responsibility for the selection, use or maintenance of any product.

Responsibility for proper selection, use and maintenance of any Emerson Process

Management product remains solely with the purchaser.

©2003 Emerson Electric Co.

TM

www.FieldQ.com

More magazines by this user
Similar magazines