mark* vie control

GEH-6761G

Mark* VIe ControlFOUNDATION Fieldbus™ InterfaceApplication GuideThese instructions do not purport to cover all details or variations in equipment, nor to provide for every possiblecontingency to be met during installation, operation, and maintenance. The information is supplied for informationalpurposes only, and GE makes no warranty as to the accuracy of the information included herein. Changes, modifications,and/or improvements to equipment and specifications are made periodically and these changes may or may not be reflectedherein. It is understood that GE may make changes, modifications, or improvements to the equipment referenced herein or tothe document itself at any time. This document is intended for trained personnel familiar with the GE products referencedherein.

Public – This document is approved for public disclosure.

GE may have patents or pending patent applications covering subject matter in this document. The furnishing of thisdocument does not provide any license whatsoever to any of these patents.

GE provides the following document and the information included therein as is and without warranty of any kind,expressed or implied, including but not limited to any implied statutory warranty of merchantability or fitness forparticular purpose.

For further assistance or technical information, contact the nearest GE Sales or Service Office, or an authorized GE SalesRepresentative.

Revised: April 2018Issued: Mar 2011

© 2011 - 2018 General Electric Company.___________________________________* Indicates a trademark of General Electric Company and/or its subsidiaries.All other trademarks are the property of their respective owners.

We would appreciate your feedback about our documentation.Please send comments or suggestions to [email protected]

For public disclosure

mailto:[email protected]

Document UpdatesRevision Location Description

G H1Added a Note that PFFA is not rating for Intrinsic Safety (IS) but IS is part of H1 standard, withreference to drawing 238A7779 for details

F

Throughout thedocument

Updated the format to left alignmentReplaced references to the Mark VIe Control FOUNDATION Fieldbus Interface User Guide(GEH-6762) with references to the ToolboxST User Guide for Mark Controls Platform (GEH-6700),the chapter Mark VIe control FOUNDATION Fieldbus Integration.GEH-6762 is obsolete and the contents have been moved to GEH-6700.

Overview

Updated the list of provided functionality and replaced the figure FOUNDATION FieldbusRedundant H1 to HSE Linking Device and Power Converter to reflect the PFFAH1B platform serialcommunication link for redundancy

Linking DevicesAdded a sentence to notify the user that there are two platforms: PFFAH1B and PFFAH1A; butH1A is obsolete so all new orders must use H1B

Glossary of TermsReplaced the term of High-speed Ethernet (HSE) with FOUNDATION HSE and updated thedefinition for accuracy

Related DocumentsDoc # TitleGEI-100757 WorkstationST* Device Manager Gateway Instruction Guide

GEI-100758 Mark VIe Control FOUNDATION Fieldbus Block Library Instruction Guide

GEH-6721_Vol_IIMark VIe and Mark VIeS Control Systems Manual, Volume II, the chapter, PFFA FOUNDATIONFieldbus Function Block Parameters Fieldbus Linking Device

GEH-6808ControlST* Software Suite How-to Guides, the section, How to Qualify a FOUNDATION FieldbusFunction Block Parameters Fieldbus Field Device

GEH-6700ToolboxST* User Guide for Mark* Controls Platforms, the chapter Mark VIe Control FOUNDATIONFieldbus Function Block Parameters Fieldbus Integration

2 GEH-6761G Mark VIe Control FOUNDATION Fieldbus InterfaceFor public disclosure

Contents1 Overview ....................................................................................................................................................41.1 Features ................................................................................................................................................41.2 Concepts ...............................................................................................................................................6

2 Configuration............................................................................................................................................. 112.1 System Limits ...................................................................................................................................... 122.2 Alerts ................................................................................................................................................. 132.3 FOUNDATION Fieldbus Function Blocks ................................................................................................. 132.4 FOUNDATION Fieldbus Transducer Blocks.............................................................................................. 172.5 FOUNDATION Fieldbus Resource Blocks ................................................................................................ 172.6 Connecting Blocks ................................................................................................................................ 182.7 Asynchronous Control ........................................................................................................................... 182.8 FOUNDATION Fieldbus Parameters ........................................................................................................ 192.9 Linking Devices ................................................................................................................................... 202.10 Fieldbus Devices................................................................................................................................. 22

3 HMI Features............................................................................................................................................. 23

Application Guide GEH-6761G 3For public disclosure

1 OverviewThe FOUNDATION fieldbus interface is a fieldbus protocol based on international standards and designed for applications inmanufacturing, process automation, and buildings automation. The guidelines for this fieldbus standard are published by theFieldbus Foundation.

A variety of component types are certified as compatible or standardized with fieldbus technology and can be interchanged fora similar component type, regardless of component manufacturer. This allows customers to use a wider range of equipment inthe control system.

Replacing a certified device from one manufacturer with a certified device from another manufacturer (interoperability) ispossible because the devices and software conform to the same standard. The Fieldbus Foundation tests and registers thedevices to ensure interoperability of registered instruments from multiple vendors. This enables the user to select the bestinstruments for the application, regardless of the host system supplier. GE has performed additional compatibility testing forMark VIe control applications and the ToolboxST application includes the Device Definition (DD). If additional devices arerequired, they can be added to the system.

Fieldbus modules, such as the FOUNDATION fieldbus H1 to high-speed Ethernet (HSE) linking device, communicate on theMark VIe control IONet and are fully compatible with ControlST Software Suite V04.03 or higher, which is a Class 61bRegistered Host. ToolboxST application software is used to configure and monitor fieldbus modules, as well as all devices atthe I/O and supervisory levels.

For reliability, two linking devices can be connected by a serial connector to form one logical linking device (redundant set)in a Primary or Secondary configuration.

Note For compatibility testing guidelines and further details, refer to the ControlST Software Suite How-to Guides(GEH-6808), the section How to Qualify a FOUNDATION Fieldbus Field Device.

1.1 FeaturesFOUNDATIONfieldbus features include:

• 4 H1 ports with galvanic isolation (transformer)• 16 field devices per segment• IECTM 61158 compliant data link layer• Access to device data, function blocks, and configuration from HSE• Data republishing from H1 to HSE or between H1 links• Redundant and non-redundant configuration• Each H1 channel can be a Link Master or Time Manager


RS232

Switches

Serial

Redundant Controllers

IONet - HSE100 MB Ethernet

Redundant Linking Devices

Four H1 Networks per Linking Device at 31.25 kB, twisted pair

Redundant Power Conditioners

Field Devices

FOUNDATION Fieldbus Redundant H1 to HSE Linking Device and Power Converter


1.2 ConceptsFOUNDATION fieldbus technology uses H1 and HSE networks, linking devices, attached segments, and field devices withfunction blocks to provide data for processing and interaction between the field devices and Mark VIe controller. Thefollowing are brief descriptions of some major concepts used in the implementation and operation of FOUNDATION fieldbustechnology with the Mark VIe control.

Note Refer to the Glossary of Terms for a list of related terms.

1.2.1 H1H1 is a fieldbus network operating at 31.25 kbit/s. The H1 network interconnects devices such as pressure or temperaturetransmitters and actuators on a field network. It is designed to operate on existing twisted pair instrument cabling with powerand signal on the same wire. H1 supports intrinsic safety (IS) applications.

Note PFFA is not rated for Intrinsic Safety (IS) but IS is part of the H1 standard. Refer to drawing 238A7779 for guidelines,rules, and technology for using IS with H1.

H1 devices contain a function block application, act as a publisher and subscriber of process variables, transmit alarms andtrends, and provide server functionality for host access and management functions. Devices can act as a scheduler and timemaster for regulating communication on a fieldbus segment. They are also used for bus interfaces in process control systemsor in linking devices. Capable of controlling bus communications and many connections to multiple devices, they supportboth client and server applications.

H1 technology enables field instruments and other devices to perform control functions reducing the load on plant computersand workstations. Since the H1 network is digital, I/O conversion subsystems are eliminated.

1.2.2 HSELike H1, HSE is an international standard (IEC™ 61158). HSE is used as a control backbone. Running at 100 Mbit/s, thetechnology is designed for device, subsystem and enterprise integration. It supports the entire range of fieldbus capabilities,including standard function blocks and device descriptions (DDs), as well as application-specific flexible function blocks(FFBs) for advanced process and discrete/hybrid/batch applications.

HSE supports complex logic functions for data-intensive process devices, such as analyzers and gateways to other networks.HSE enhances access to H1 fieldbus technology by way of linking devices, while providing expanded capabilities forhigh-speed automation devices and hybrid or batch applications.

HSE provides the same benefits as H1, but at the subsystem integration level instead of the field device level. It supportsinteroperability between disparate controllers and gateways in the same way that H1 supports interoperability betweentransmitters and actuators from different suppliers. FFBs in HSE devices can be set up using programming languages such asthose found in the international standard IEC 61131-3.

HSE also supports standard Ethernet wiring, including the use of fiber-optic cable to provide cost-effective electrical isolationbetween plant areas or immunity from distortion through noisy environments.


1.2.3 Linking DeviceThe linking device (PFFA) sends processed data from one H1 link to another H1 link, and sends and receives data from theH1 link to the HSE. It also provides access to the components attached to the H1 links for configuration and identification,including access to the component function blocks. The linking device supports dual redundant operation, it is fanless, and itscompact size allows it to be used in a DIN rail assembly. There are two platforms, H1B and H1A; however, PFFAH1A isobsolete and any new orders must use PFFAH1B.

PFFAH1B Linking Device functionality includes the following:

• Gateway between an Ethernet (HSE) port and four fieldbus (H1) ports• Supports up to 16 field devices per segment• Supports up to four separate H1 links. In each of these links, the Linking Device operates as the Link Master and the

System Management (SM) Time Publisher.• Identification of the devices connected to the H1 links• Configuration of the connected H1 devices by System Management and Network Management through HSE• Access to the function blocks of the connected H1 devices through HSE• Republishing of process data from one H1 link to another• Republishing of process data from H1 to HSE and vice versa

Note Refer to theMark VIe and Mark VIeS Control Systems Manual, Volume II (GEH-6721 Vol II), the chapter PFFAFOUNDATION Fieldbus Linking Device.

1.2.4 BlocksTo ensure device interoperability FOUNDATION fieldbus technology uses a fully specified, standard user layer based on blocksand device descriptions (DDs). The user layer defines a function block application process (FBAP) using resource blocks,function blocks, transducer blocks, system management, network management, and DD technology.

Resource blocks define parameters that pertain to the entire application process (for example, manufacturing ID, device type,and so forth). Function blocks encapsulate control functions (for example, PID controller, analog input, and so forth) andtransducer blocks offer an interface to sensors such as temperature, pressure, and flow, and actuators for valves.

Blocks are incorporated into fieldbus devices to achieve the desired device functionality, as well as to define a wide range offeatures and behaviors that must work in a standard way for devices to interoperate. For example, a simple temperaturetransmitter can contain an analog input (AI) function block. A control valve might contain a proportional/integral/derivative(PID) function block as well as the expected analog output (AO) block. Thus, a complete control loop can be built using onlya simple transmitter and a control valve.


Each block's parameters are represented by object descriptions that define how the parameters are communicated on thefieldbus network. The FBAP represents a very comprehensive application model that, in conjunction with the protocol,provides the technology that allows devices from different manufacturers to interoperate. Refer to Appendix A FOUNDATIONFieldbus Function Block Parameters.

As specified by the FBAP, a fieldbus device must have a resource block and at least one function block with input and/oroutput parameters that link to other function blocks, either in the same device or in separate devices by means of the bus. Thelink object defines the connection. Each input/output parameter passed has a value and a status. The status portion of eachparameter carries information on the quality of each value, of good, uncertain, or bad, with substatus further elaborating onthe state of the control strategy using the parameter.

In addition, the FBAP specifies the handling of control modes, alarms, events, trend reports and views. All of these featuresmust comply with the FOUNDATION fieldbus specification in order for a device to be considered interoperable at the user layer.

Distribution of control to the field device is made possible by synchronization of function block execution andcommunication of function block parameters on the fieldbus. This function, along with publication of the time of day to alldevices, automatic switch over to a redundant time publisher, assignment of device addresses, and searching for parameternames or tags on the fieldbus, are handled by system management (SM) and network management (NM). Control in the fieldmay provide faster control strategy execution but has redundancy implications that must be understood before implementingit.

Blocks that run in field devices and blocks that run in the controller interact as follows:

• FOUNDATION fieldbus blocks appear in the controller in special FOUNDATION fieldbus tasks. FOUNDATION fieldbus tasks inthe controller perform at the macrocycle rate for the slowest macrocycle that contains a block in the task.

• Segment macrocycle is determined by the number of devices on a FOUNDATION fieldbus segment, the number of blocksused in devices on a segment, the interconnections between blocks (in the same or different devices) on a FOUNDATIONfieldbus segment, and minimum macrocycle requirements by device manufacturers.

Note Refer to the ToolboxST User Guide for Mark Controls Platforms (GEH-6700), the chapterMark VIe ControlFOUNDATION Fieldbus Interface, the section Attached Segments for information regarding macrocycle and macrocycletimeline.

• Macrocycle and controller task execution rate are not synchronized. It may take as much as one task execution time plusone macrocycle time to complete the control strategy in a task. Information about the macrocycle timeline can beobtained from the Macrocycle Timeline Viewer as displayed in the following figure.


Macrocycle Timeline Viewer

• Macrocycle is constrained to be a binary multiple of frame rate. The macrocycle contains time reserved for scheduled(synchronous) and unscheduled (asyncronous) tasks. The segment Unscheduled Overhead Percent property (timeallowed for asynchronous communications) can be configured for 30%, 40%, or 50% of the total macrocycle time. Ifmore than the configured time is consumed, the next longest macrocycle is selected by the system.

Note Refer to the ToolboxST User Guide for Mark Controls Platforms (GEH-6700), the chapterMark VIe ControlFOUNDATION Fieldbus Interface, the section Configure an Attached Segment Macrocycle for additional information.


2 ConfigurationAll configuration of fieldbus linking devices and attached segments, fieldbus devices, fieldbus blocks, and related parametersand properties is performed in the ToolboxST* application. The configurations are displayed and edited in the ComponentEditor’s Hardware and Software tabs.

Note Refer to the ToolboxST User Guide for Mark Controls Platforms (GEH-6700), the chapterMark VIe ControlFOUNDATION Fieldbus Interface for information on configuring fieldbus devices.

The addition of fieldbus devices to a H1 segment involves the use of a placeholder. A fieldbus device placeholder is arepresentation of a fieldbus device. They are created inside a Mark VIe controller. Before a placeholder can be tied to aphysical fieldbus device, it must go through the commissioning process. After commissioning, the fieldbus device becomeslive and active in the system and is included in the download process of the controller.

Attention

If you delete an H1 device that has associated blockware, perform a build of thecontroller before you insert a new H1 device on the segment. This build will result inerrors if there are any function blocks on the Software tab that were assigned to theH1 device that was deleted. These function blocks either need to be deleted orunassigned and re-assigned to another H1 device block on that segment before asuccessful build will occur. If these blocks are not unassigned and re-assigned, thenthere is a possibility that an inserted H1 device will generate the PDTags necessary forthe blockware to assume that the original H1 device is present and it will not rebuildthe macrocycle. This could potentially lead to build and download errors.

As part of the commissioning process in the ToolboxST application, a physical H1 device must be matched to a placeholder.In order for the ToolboxST application to know whether the correct H1 device is present, certain parameters that detail whatthe device is and its version are read from the DD files. When configuring a fieldbus device, the device type and revisionnumber must be the same as those in the ToolboxST application or the commissioning of the device produces an error. TheDD file version in the ToolboxST application can be higher (but not lower) than the one in the device.

The ToolboxST application's block palette for a special fieldbus task displays the generic FOUNDATION fieldbus functionblocks in a fieldbus category in addition to the traditional Mark VIe control function block categories. FOUNDATION fieldbusfunction blocks can only be used in the special FOUNDATION fieldbus task. Mark VIe control function blocks are also allowedto operate in this special task in addition to the normal Mark VIe control tasks.


2.1 System LimitsThe following system limits should be observed when configuring Mark VIe controls for FOUNDATION fieldbus applications.Depending on the specific configuration, not all maximum limits may be achievable concurrently:

• A maximum of 16 field devices may be configured per FOUNDATION fieldbus H1 segment.• A maximum of 4096 of each type of FOUNDATION fieldbus alert may be configured per controller (that is analog,

discrete, field diagnostic, or update event).• A maximum of 20 PFFA linking devices may be configured per IONet.• A maximum of four segments may be configured per PFFA linking device.• A maximum of 400 FOUNDATION fieldbus Virtual Communication Relationships (VCRs) may be configured per PFFA

linking device.• A maximum of 2048 VCRs may be configured per controller.

In addition, the following guidelines are useful to consider when configuring large applications or applications containingboth FOUNDATION fieldbus devices and native Mark VIe I/O.

• As FOUNDATION fieldbus segment loading is increased, live data update time may also increase.• A minimum FOUNDATION fieldbus macrocycle of 320 mS is recommended; shorter macrocycles may result in

inconsistent inputs during redundancy fail-overs.• The Mark VIe system can accommodate one alert transition per second without queuing. To improve the likelihood that

alert data is not dropped during periods of burst activity, use native Mark VIe analog alarms instead of FOUNDATIONfieldbus alerts.

• The Mark VIe controller is capable of supporting up to 200 PAIC-equivalent I/O packs per IONet. Each PFFA representsa load of five PAIC equivalent I/O packs to the system.

Configuration Example:

An engineer wants to configure a system with 1100 Motor Operated Valves (MOVs) on FOUNDATION fieldbus and thereforeneeds to understand the minimum amount of Mark VIe hardware required to support it. Each MOV currently requires fourVCRs.

Dividing the total number of devices (1100) by the number supportable per segment (16) yields a minimum of 69 H1segments necessary. Since each PFFA can support four segments, the minimum number of PFFAs required is 69/4, or 18.Further, since a single IONet can support up to 20 PFFAs only one IONet is required for this application. The MOVs willgenerate 4400 VCRs, which spread evenly across 18 PFFAs comes to 244 per linking device. This number of VCRs is wellwithin the limit of 400 for a single PFFA, as well as the limit of 2048 for a single controller. The minimum hardwarenecessary to achieve this configuration is therefore a single Mark VIe controller, using a single IONet, with 18 fully populatedPFFAs. Other specifications may drive the need for additional hardware (for example, application code loading, redundancy,spares, or partitioning for functionality, and so forth).


2.2 AlertsFOUNDATION fieldbus technology supports four types of alerts: analog alerts, discrete alerts, field diagnostic alerts, and updateevents.

Analog Alerts annunciate when an analog input value reaches a configured limit and are available on function blocks thatsupport analog input values. There are four types of analog alerts: HI_ALM, HI_HI_ALM, LO_ALM, and LO_LO_ALM.The HI_ALM and HI_HI_ALM alerts activate when the process value exceeds the corresponding configured limit. The LO_ALM and LO_LO_ALM alerts activate when the process value goes below the corresponding configured limit.

FOUNDATION annunciate when the output matches a configured value in the DISC_LIM parameter.

Field Diagnostic Alerts annunciate when a certain condition exists within the field device. These are usually maintenancerelated issues that the device has detected.

Update Events display when a static parameter has been changed on the device. If a configuration tool writes a value to astatic parameter an alert is issued to notify the user of a change in configuration. For some parameters, the update eventdisplays which parameter changed and in some cases what the value changed to.

2.3 FOUNDATION Fieldbus Function BlocksFunction blocks provide the control system behavior. The input and output parameters of function blocks can be linked overthe fieldbus. The execution of each function block is precisely scheduled. There can be many function blocks in a single userapplication. Only variables from the output of FOUNDATION fieldbus function blocks should be used in control applicationprograms. FOUNDATION fieldbus parameter values from data views should not be used for control purposes because they arenot synchronous or deterministic. The ToolboxST application supports the following fieldbus function blocks in standard andenhanced forms:

Block Label Operational Icon

Analog Alarm FF_AAL

Analog Input FF_AI

Analog Output FF_AO

Arithmetic FF_AR

Bias/Gain Station FF_BG



Custom Control FF_CC

Custom Calculation FF_CCL

Custom Input FF_CI

Custom Output FF_CO

Control Selector FF_CS

Device Control FF_DC

Discrete Input FF_DI

Discrete Output FF_DO

Dead Time FF_DT



Input Selector FF_IS

Integrator FF_IT

Lead Lag FF_LL

Multiple AnalogInput

FF_MAI

Multiple AnalogOutput

FF_MAO

Multiple DiscreteInput

FF_MDI



Multiple DiscreteOutput

FF_MDO

Manual Loader FF_ML

Output Splitter FF_OS

P, PD Controller FF_PD

PID, PI, I Controller FF_PID

Ratio Station FF_RA

Signal Characterizer FF_SC

Setpoint RampGenerator

FF_SPG



Timer FF_TMR

Unassigned Unassigned

Note Refer to the ToolboxST User Guide for Mark Controls Platforms (GEH-6700), the chapterMark VIe ControlFOUNDATION Fieldbus Interface, for information on assigning FOUNDATION fieldbus function blocks.

In the block editing space, unassigned generic FOUNDATION fieldbus function blocks display Unassigned, in black lettering,

where the PD tag would be for an assigned function block. A question mark icon ( ) displays in the upper right-handcorner in place of the operational icon displayed for as assigned function block.

Assigned fieldbus function blocks display the PD tag of the fieldbus device the function block is assigned to in blue lettering.They also display a specific operational icon in the upper right-hand corner that identifies the block’s function. Theoperational icon replaces the question mark icon of the unassigned function block.

Only Mark VIe function blocks are given execution orders because the fieldbus function block execution order in themacrocycle is determined by connection.

2.4 FOUNDATION Fieldbus Transducer BlocksThe transducer blocks are used to configure devices. Transducer blocks decouple function blocks from the local input andoutput functions required to read sensors and command output hardware. They contain information such as calibration dateand sensor type. There is usually one transducer block channel for each input or output of a function block. This type of blockis not attached to any other blocks in the Mark VIe controller.

2.5 FOUNDATION Fieldbus Resource BlocksThe resource block describes characteristics of the fieldbus device such as the device name, manufacturer, and serial number.There is only one resource block in a device and each device is required to have one. This type of block is not attached to anyother blocks in the Mark VIe controller.


2.6 Connecting BlocksFieldbus function blocks and other Mark VIe function blocks can be connected in any way as long as the data types match onboth pins being connected. Use the standard wiring tool in the ToolboxST application. The ToolboxST application can createthe following example connections in a Fieldbus Task:

Straight FOUNDATION Fieldbus Function Block Connection Example

Mixed FOUNDATION Fieldbus Function Block and Mark VIe Function Block Example

2.7 Asynchronous ControlThe execution of fieldbus related blockware in the controller does not depend upon the reception of inputs from the linkingdevice and does not attempt to synchronize with the fieldbus macrocycle. Once the ToolboxST application calculates theminimum macrocycle period necessary based upon the configured logic (the macrocycle period is padded such that it is amultiple of the controller’s frame rate). It then configures each fieldbus related task with a frame multiplier and scheduleoffset corresponding to the macrocycle period.

Since the controller clocks and the fieldbus link times are not synchronized, skew can occur and the controller may beexecuting on inputs from the previous macrocycle. While this leads to less responsive control loops since it can takeeffectively two macrocycles to react to changing input stimulus, this approach allows fieldbus tasks to connect blocks fromdevices on multiple segments upon multiple linking devices. If the connected segments are running at different macrocycles,the controller runs at the greater of the macrocycle periods.

Advantages:

• Less complex• Can support task configurations with multiple segments and multiple linking device• Synchronous execution among controllers


2.8 FOUNDATION Fieldbus ParametersFOUNDATION fieldbus blocks contain parameters which can be configured and applied to commissioned online fieldbusdevices. The fieldbus block parameters are edited using the ToolboxST Summary View’s Parameter Editor. The parameters ofFOUNDATION fieldbus transducer, and resource blocks are edited in the Hardware tab while parameters of FOUNDATIONfieldbus function blocks are edited in either the Software or Hardware tabs.

Note Refer to Appendix A FOUNDATION Fieldbus Function Block Parameters for a list of the block parameters and theirdescriptions.

To support homogeneity with the ToolboxST application, fieldbus parameters that are listed on a function block’s View 1parameter list can be placed on EGD. Parameters on EGD display the following properties in the Hardware tab parametergrid:

• ToolboxST application Description• ToolboxST application Second Language Description• ToolboxST application Alias• ToolboxST application EGD Page

Fieldbus alarm parameters, meaning parameters ending with _ALM, display the following additional properties in theHardware and Software tab parameter grids:

• ToolboxST application Alarm Class• ToolboxST application Priority• ToolboxST application Alarm Inhibit Group• ToolboxST application Active Severity• ToolboxST application Normal Severity• ToolboxST application Plant Area


2.9 Linking DevicesThe ToolboxST Hardware tab Summary View displays information about linking devices. When the system is online, theHardware tab displays the following:

• Indication in the linking device Summary View if the linking device is online− If the linking device is not in the Live List, the linking device is not online− If no Live List is emitting from the linking device, the linking device is not online

Note Refer to theMark VIe and Mark VIeS Control Systems Manual, Volume II (GEH-6721 Vol II), the chapter PFFAFOUNDATION Fieldbus Linking Device.


• Indication if the linking device is emitting a device alert or process alarm

Error, warning, and informational symbols display on the linking device in the Hardware tab Summary View. Thisinformation is provided by the alarm and diagnostic subsystems inside the Mark VIe controller.


2.10 Fieldbus DevicesThe ToolboxST Hardware tab displays information about fieldbus devices. When the system is online, the Hardware tabdisplays the following:

• Indication if a fieldbus device is on the Live List in the Summary View

– If the fieldbus device is not in the Live List, a red X ( ) displays, the fieldbusdevice is not online

• Indication if a fieldbus device is emitting a device alert or process alarm ( )• Current fieldbus device state using the fieldbus device state overlay symbols

Note When a fieldbus device is added to a system, it acts as a placeholder until it is commissioned. The commissioningprocess makes the fieldbus device live and active in the system.

The ToolboxST application classifies a fieldbus device in one of the following states:

• Uninitialized State− Fieldbus device does not have a PD_TAG− Fieldbus device does not have a permanent node address

– Overlay symbol:

• Initialized State− Fieldbus device has a PD_TAG− Fieldbus device does not have a permanent node address− Fieldbus device revisions match placeholder revisions

– Overlay symbol:

• Commissioned State− Fieldbus device has a PD_TAG− Fieldbus device has a permanent node address

– Overlay symbol:

• Mismatch State− Fieldbus device revisions have not been obtained. Check for a communications failure diagnostic to determine if

there is a problem or if it is just taking a while to update.− Fieldbus device revisions do not match the placeholder revisions. Re-add the placeholder using a DD file matching

the revisions.− Fieldbus device has a node address collision with a fieldbus device placeholder of a different type− Fieldbus device has a node address that does not exist in the ToolboxST configuration− No DD files are available for the fieldbus device in the ToolboxST DD file database

– Overlay symbol:


3 HMI FeaturesThe ToolboxST application enables you to view and interact with fieldbus process alarms and device alerts through theWorkstationSTAlarm Viewer, OPC® AE Server, and GSM Server.

The ToolboxST and CIMPLICITYapplications work together to provide a variety of functions and information to the systemand user. Part of this is the CIMPLICITY smart object. A CIMPLICITY smart object can:

• Indicate the PD tag of the device to which the FOUNDATION fieldbus function block is assigned.• Display the description of the assigned FOUNDATION fieldbus function block.• Display the assigned FOUNDATION fieldbus function block’s View 1 parameters from EGD.• Write to those parameters where the actual mode of the target block allows write access.• Perform the Goto logic function to enable opening the special fieldbus task that references the assigned FOUNDATION

fieldbus function block.

The following FOUNDATION fieldbus blocks have a smart object configured:

• FF_AI• FF_AO• FF_DI• FF_DO• FF_PID

The ToolboxST application only supports the drag-and-drop of assigned fieldbus function blocks, configured to put View 1 onEGD, onto a CIMPLICITY HMI screen. The ToolboxST application populates the clipboard with the proper data to enablethe CIMPLICITY smart object to function properly.

Note The drag-and-drop of other blocks is not prevented, but they will not function.


Notes


FOUNDATION Fieldbus Function Block ParametersThis appendix contains a list of the FOUNDATION Fieldbus Function Block Parameters fieldbus function block parameters andtheir descriptions. Also included is a listing of the blocks and the parameters associated with that block.

ParametersThe following is a description of each block parameter and its intended use.

ACK_OPTION Selection of whether alarms associated with the block is automatically acknowledged.

ALARM_HYS Amount the PV must return within the alarm limits before the alarm condition clears. Alarm Hysteresis isexpressed as a percent of the PV span.

ALARM_SUM The current alert status, unacknowledged states, unreported states, and disabled states of the alarmsassociated with the function block.

ALERT_KEY The identification number of the plant unit. This information may be used in the host for sorting alarms, etc.

BAL_TIME The difference value used in the block calculation for bumpless transfer should ramp to zero in the timespecified by BAL_TIME.

BIAS The bias value used in computing the function block output, expressed in engineering units.

BKCAL_HYS The amount that the output must change away from its output limit before the limit status is turned off,expressed as a percent of the span of the output.

BKCAL_IN The value and status from a lower block's BKCAL_OUT that is used to prevent reset windup and to initializethe control loop.

BKCAL_OUT The value and status required by an upper block’s BKCAL_IN so that the upper block may prevent resetwindup and provide bumpless transfer to closed loop control.

BKCAL_OUT_D The output value and status provided to an upstream discrete block. This information is used to providebumpless transfer to closed loop control.

BKCAL_SEL_1 Control elector output value and status associated with SEL_1 input which is provided to BKCAL_IN ofthe block connected to SEL_1 to prevent reset windup.

BKCAL_SEL_2 Control selector output value and status associated with SEL_2 input which is provided to BKCAL_INof the block connected to SEL_2 to prevent reset windup.

GEH-6761G Application Guide 25For public disclosure

BKCAL_SEL_3 Control selector output value and status associated with SEL_3 input which is provided to BKCAL_INof the block connected to SEL_3 to prevent reset windup.

BLOCK_ALM The block alarm is used for all configuration, hardware, connection failure, or system problems in theblock. The cause of the alert is entered in the subcode field. The first alert to become active sets the Active status in the Statusattribute. As soon as the Unreported status is cleared by the alert reporting task, another block alert may be reported withoutclearing the Active status, if the subcode has changed.

BLOCK_ERR This parameter reflects the error status associated with the hardware or software components associatedwith a block. It is a bit string, so that multiple errors may be displayed.

BYPASS The normal control algorithm may be bypassed through this parameter. When bypass is set, the setpoint value (inpercent) is directly transferred to the output. To prevent a bump on transfer to/from bypass, the setpoint is automaticallyinitialized to the output value or process variable, respectively, and the path broken flag is set for one execution.

CAS_IN This parameter is the remote setpoint value, which must come from another Fieldbus block, or a DCS blockthrough a defined link.

CAS_IN_D This parameter is the remote setpoint value of a discrete block, which must come from another Fieldbus block,or a DCS block through a defined link.

CHANNEL The number of the logical hardware channel that is connected to this I/O block. This information defines thetransducer to be used going to or from the physical world.

CLR_FSTATE Writing a Clear to this parameter clears the device fault state if the field condition, if any, has cleared.

CONFIRM_TIME The time the resource waits for confirmation of receipt of a report before trying again. Retry shall nothappen when CONFIRM_TIME = 0.

CONTROL_OPTS Options which the user may select to alter the calculations done in a control block.

CYCLE_SEL Used to select the block execution method for this resource.

CYCLE_TYPE Identifies the block execution methods available for this resource.

DD_RESOURCE String identifying the tag of the resource which contains the Device Description for this resource.

DD_REV Revision of the DD associated with the resource - used by an interface device to locate the DD file for theresource.

DEV_REV Manufacturer revision number associated with the resource - used by an interface device to locate the DD filefor the resource.


DEV_TYPE Manufacturer’s model number associated with the resource - used by interface devices to locate the DD filefor the resource.

DISC_ALM The status and time stamp associated with the discrete alarm.

DISC_LIM State of discrete input which generates an alarm.

DISC_PRI Priority of the discrete alarm.

DV_HI_ALM The status and time stamp associated with the high deviation alarm.

DV_HI_LIM The setting of the high deviation alarm limit in engineering units.

DV_HI_PRI Priority of the high deviation alarm.

DV_LO_ALM The status and time stamp associated with the low deviation alarm.

DV_LO_LIM The setting of the low deviation alarm limit in engineering units.

DV_LO_PRI Priority of the low deviation alarm.

FAULT_STATE Condition set by loss of communication to an output block, fault promoted to an output block or aphysical contact. When Fault State condition is set, Then output function blocks perform their FSTATE actions.

FEATURE_SEL Used to select resource block options.

FEATURES Used to display supported resource block options.

FF_GAIN The gain that the feed forward input is multiplied by before it is added to the calculated control output.

FF_SCALE The feedforward input high and low scale values, engineering units code, and number of digits to the right ofthe decimal point.

FF_VAL The feed forward value and status.

FIELD_VAL Raw value of the field device in percent of thePV range, with a status reflecting the Transducer condition,before signal characterization (L_TYPE) or filtering (PV_FTIME).

FIELD_VAL_D Raw value of the field device discrete input, with a status reflecting the Transducer condition.

FREE_SPACE Percent of memory available for further configuration. Zero in a preconfigured resource.

FREE_TIME Percent of the block processing time that is free to process additional blocks.

FSTATE_TIME The time in seconds from detection of fault of the output block remote setpoint to the output action of theblock output if the condition still exists.


FSTATE_VAL The preset analog SP value to use when fault occurs. This value is used if the I/O option Fault State tovalue is selected.

FSTATE_VAL_D The preset discrete SP_D value to use when fault occurs. This value is used if the I/O option Fault Stateto value is selected.

GAIN Dimensionless value used by the block algorithm in calculating the block output.

GRANT_DENY Options for controlling access of host computer and local control panels to operating, tuning and alarmparameters of the block.

HARD_TYPES The types of hardware available as channel numbers.

HI_ALM The status for high alarm and its associated time stamp.

HI_HI_ALM The status for high high alarm and its associated time stamp.

HI_HI_LIM The setting for high high alarm in engineering units.

HI_HI_PRI Priority of the high high alarm.

HI_LIM The setting for high alarm in engineering units.

HI_PRI Priority of the high alarm.

IO_OPTS Options which the user may select to alter input and output block processing.

IN The primary input value of the block, required for blocks that filter the input to get the PV.

IN_1 Auxiliary input value to the block, used for other values than the PV.

ITK_VER Major revision number of the interoperability test case used in certifying this device as interoperable. Theformat and range of the version number is defined and controlled by the Fieldbus Foundation. Note: The value of thisparameter is zero (o) if the device has not been registered as interoperable by the FF.

LIM_NOTIFY Maximum number of unconfirmed alert notify messages allowed.

L_TYPE Determines if the values passed by the transducer block to the AI block may be used directly (Direct) or if thevalue is in different units and must be converted linearly (Indirect), or with square root (Ind Sqr Root), using the input rangedefined by the transducer and the associated output range.

LO_ALM The status of the low alarm and its associated time stamp.

LO_LIM The setting for the low alarm in engineering units.


LO_LO_ALM The status of the low low alarm and its associated time stamp.

LO_LO_LIM The setting of the low low alarm in engineering units.

LO_LO_PRI Priority of the low low alarm.

LO_PRI Priority of the low alarm.

LOW_CUT Limit used in square root processing. A value of zero percent of scale is used in block processing if thetransducer value falls below this limit. This feature may be used to eliminate noise near zero for a flow sensor.

MANUFAC_ID Manufacturer identification number - used by an interface device to locate the DD file for the resource.

MAX_NOTIFY Maximum number of unconfirmed notify messages possible.

MEMORY_SIZE Available configuration memory in the empty resource. To be checked before attempting a download.

MIN_CYCLE_T Time duration of the shortest cycle interval of which the resource is capable.

MODE_BLK The actual, target, permitted, and normal modes of the block.

NV_CYCLE_T Minimum time interval specified by the manufacturer for writing copies of NV parameters to non-volatilememory. Zero means it is never automatically copied. At the end of NV_CYCLE_TIME, only those parameters which havechanged (as defined by the manufacturer) need to be updated in NVRAM.

OUT The primary analog value calculated as a result of executing the function.

OUT_D The primary discrete value calculated as a result of executing the function.

OUT_HI_LIM Limits the maximum output value.

OUT_LO_LIM Limits the minimum output value.

OUT_SCALE The high and low scale values, engineering units code, and number of digits to the right of the decimalpoint to be used in displaying the OUT parameter and parameters which have the same scaling as OUT.

OUT_STATE Index to the text describing the states of a discrete output.

PV Either the primary analog value for use in executing the function, or a process value associated with it. May also becalculated from the READBACK value of an AO block.

PV_D Either the primary discrete value for use in executing the function, or a process value associated with it. May also becalculated from the READBACK_D value of a DO block.


PV_FTIME Time constant of a single exponential filter for the PV, in seconds.

PV_SCALE The high and low scale values, engineering units code, and number of digits to the right of the decimal pointto be used in displaying the PV parameter and parameters which have the same scaling as PV.

PV_STATE Index to the text describing the states of a discrete PV.

RA_FTIME Time constant of a single exponential filter for the value to be ratioed, in seconds.

RATE Defines the derivative time constant, in seconds.

RCAS_IN Target setpoint and status provided by a supervisory Host to a analog control or output block.

RCAS_IN_D Target setpoint and status provided by a supervisory Host to a discrete control or output block.

RCAS_OUT Block setpoint and status after ramping - provided to a supervisory Host for back calculation and to allowaction to be taken under limiting conditions or mode change.

RCAS_OUT_D Block setpoint and status provided to a supervisory Host for back calculation and to allow action to betaken under limiting conditions or mode change.

READBACK This indicates the readback of the actual continuous valve or other actuator position, in transducer units.

READBACK_D This indicates the readback of the actual discrete valve or other actuator position, in the transducer state.

RESET The integral time constant, in seconds per repeat.

RESTART Allows a manual restart to be initiated. Several degrees of restart are possible. They are 1: Run, 2: Restartresource, 3: Restart with defaults, and 4: Restart processor.

ROUT_IN Target output and status provided by a Host to the control block for use as the output (ROut mode).

ROUT_OUT Block output and status - provided to a Host for back calculation in ROut mode and to allow action to betaken under limited conditions or mode change.

RS_STATE State of the function block application state machine.

SEL_1 First input value to the selector.

SEL_2 Second input value to the selector.

SEL_3 Third input value to the selector.


SEL_TYPE This parameter specifies the type of selector action, from choices of High, Medium, and Low.

SET_FSTATE Allows the Fault State condition to be manually initiated by selecting Set.

SHED_OPT Defines action to be taken on remote control device timeout.

SHED_RCAS Time duration at which to give up on computer writes to function block RCas locations. Shed from RCasshall never happen when SHED_RCAS = 0.

SHED_ROUT Time duration at which to give up on computer writes to function block ROut locations. Shed from Routshall never happen when SHED_ROUT = 0.

SIMULATE Allows the transducer analog input or output to the block to be manually supplied when simulate is enabled.When simulation is disabled, the simulate value and status track the actual value and status.

SIMULATE_D Allows the transducer discrete input or output to the block to be manually supplied when simulate isenabled. When simulation is disabled, the simulate value and status track the actual value and status.

SP The analog setpoint of this block.

SP_D The discrete setpoint of this block.

SP_HI_LIM The setpoint high limit is the highest setpoint operator entry that can be used for the block.

SP_LO_LIM The setpoint low limit is the lowest setpoint operator entry that can be used for the block.

SP_RATE_DN Ramp rate at which downward setpoint changes are acted on in Auto mode, in PV units per second. If theramp rate is set to zero, then the setpoint is used immediately. For control blocks, rate limiting applies only in Auto. Foroutput blocks, rate limiting applys in Auto, Cas, and RCas modes.

SP_RATE_UP Ramp rate at which upward setpoint changes are acted on in Auto mode, in PV units per second. If theramp rate is set to zero, then the setpoint is used immediately. For control blocks, rate limiting applies only in Auto. Foroutput blocks, rate limiting applies in Auto, Cas, and RCas modes.

ST_REV The revision level of the static data associated with the function block. To support tracking changes in staticparameter attributes, the associated block’s static revision parameter is incremented each time a static parameter attributevalue is changed. Also, the associated block’s static revision parameter may be incremented if a static parameter attribute iswritten but the value is not changed.


STATUS_OPTS Options which the user may select in the block processing of status.

STRATEGY The strategy field can be used to identify grouping of blocks.. This data is not checked or processed by theblock.

TAG_DESC The user description of the intended application of the block.

TEST_RW Read/write test parameter - used only for conformance testing.

TRK_IN_D This discrete input is used to initiate external tracking of the block output to the value specified by TRK_VAL.

TRK_SCALE The high and low scale values, engineering units code, and number of digits to the right of the decimalpoint, associated with TRK_VAL.

TRK_VAL This input is used as the track value when external tracking is enabled by TRK_IN_D.

UPDATE_EVT This alert is generated by any change to the static data.

WRITE_ALM This alert is generated if the write lock parameter is cleared.

WRITE_LOCK If set, no writes from anywhere are allowed, except to clear WRITE_LOCK. Block inputs continue to beupdated.

WRITE_PRI Priority of the alarm generated by clearing the write lock.

XD_SCALE The high and low scale values, engineering units code, and number of digits to the right of the decimal pointused with the value obtained from the transducer for a specified channel.

XD_STATE Index to the text describing the states of a discrete for the value obtained from the transducer.


BlocksThe following is a list of FOUNDATION fieldbus blocks and their associated parameters.

Analog Alarm (FF_AAL)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 26 EXPAND_UP

2 TAG_DESC 27 EXPAND_DN

3 STRATEGY 28 IGNORE_TIME

4 ALERT_KEY 29 UPDATE_EVT

5 MODE_BLK 30 BLOCK_ALM

6 BLOCK_ERR 31 ALARM_SUM

7 PV 32 ACK_OPTION

8 OUT 33 ALARM_HYS

9 OUT_RANGE 34 HI_HI_PRI

10 GRANT_DENY 35 HI_HI_LIM

11 STATUS_OPTS 36 HI_HI_LIMX

12 PV_FTIME 37 HI_PRI

13 IN 38 HI_ LIM

14 PSP 39 HI_ LIMX

15 HI_GAIN 40 LO_PRI

16 LO_GAIN 41 LO_ LIM

17 HI_HI_BIAS 42 LO_ LIMX

18 HI_BIAS 43 LO_LO_PRI

19 LO_BIAS 44 LO_LO_LIM

20 LO_LO_BIAS 45 LO_LO_LIMX

21 PRE_OUT_ALM 46 HI_HI_ALM

22 OUT_ALM 47 HI_ ALM

23 OUT_ALM_SUM 48 LO_ALM

24 ALM_RATE_UP 49 LO_LO_ALM

25 ALM_RATE_DN


Analog Input (FF_AI)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 19 FIELD_VAL

2 TAG_DESC 20 UPDATE_EVT

3 STRATEGY 21 BLOCK_ALM

4 ALERT_KEY 22 ALARM_SUM

5 MODE_BLK 23 ACK_OPTION

6 BLOCK_ERR 24 ALARM_HYS

7 PV 25 HI_HI_PRI

8 OUT 26 HI_HI_LIM

9 SIMULATE 27 HI_PRI

10 XD_SCALE 27 HI_LIM

11 OUT_SCALE 29 LO_PRI

12 GRANT_DENY 30 LO_LIM

13 IO_OPTS 31 LO_LO_PRI

14 STATUS_OPTS 32 LO_LO_LIM

15 CHANNEL 33 HI_HI_ALM

16 L_TYPE 34 HI_ALM

17 LOW_CUT 35 LO_ALM

18 PV_FTIME 36 LO_LO_ALM


Analog Output (FF_AO)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 16 READBACK

2 TAG_DESC 17 CAS_IN

3 STRATEGY 18 SP_RATE_DN

4 ALERT_KEY 19 SP_RATE_UP

5 MODE_BLK 20 SP_HI_LIM

6 BLOCK_ERR 21 SP_LO_LIM

7 PV 22 CHANNEL

8 SP 23 FSTATE_TIME

9 OUT 24 FSTATE_TIME

10 SIMULATE 25 BKCAL_OUT

11 PV_SCALE 26 RCAS_IN

12 XD_SCALE 27 SHED_OPT

13 GRANT_DENY 28 RCAS_OUT

14 IO_OPTS 29 UPDATE_EVT

15 STATUS_OPTS 30 BLOCK_ALM


Arithmetic (FF_AR)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 19 RANGE_HI

2 TAG_DESC 20 RANGE_LO

3 STRATEG 21 BIAS_IN_1

4 ALERT_KEY 22 GAIN_IN_1

5 MODE_BLK 23 BIAS_IN_2

6 BLOCK_ERR 24 GAIN_IN_2

7 PV 25 BIAS_IN_3

8 OUT 26 GAIN_IN_3

9 PRE_OUT 27 COMP_HI_LIM

10 PV_SCALE 28 COMP_LO_LIM

11 OUT_RANGE 29 ARITH_TYPE

12 GRANT_DENY 30 BAL_TIME

13 INPUTS_OPTS 31 BIAS

14 IN 32 GAIN

15 IN_LO 33 OUT_HI_LIM

16 IN_1 34 OUT_LO_LIM

17 IN_2 35 UPDATE_EVT

18 IN_3 36 BLOCK_ALM


Bias/Gain Station (FF_BG)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 17 SP_HI_LIM

2 TAG_DESC 18 SP_LO_LIM

3 STRATEGY 19 GAIN

4 ALERT_KEY 20 BAL_TIME

5 MODE_BLK 21 BKCAL_IN

6 BLOCK_ERR 22 OUT_HI_LIM

7 SP 23 OUT_LO_LIM

8 OUT 24 BKCAL_OUT

9 OUT_SCALE 25 RCAS_IN

10 GRANT_DENY 26 SHED_OPT

11 CONTROL_OPTS 27 RCAS_OUT

12 STATUS_OPTS 28 TRK_SCALE

13 IN_1 29 TRK_IN_D

14 CAS_IN 30 TRK_VAL

15 SP_RATE_DN 31 UPDATE_EVT

16 SP_RATE_UP 32 BLOCK_ALM

Custom Control (FF_CC)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 10 IN

2 TAG_DESC 11 OUT_D

3 STRATEGY 12 BKCAL_IN_D

4 ALERT_KEY 13 PV_D

5 MODE_BLK 14 IN_D

6 BLOCK_ERR 15 BLOCK_ALM

7 OUT 16 R_DS256

8 BKCAL_IN 17 R_DS257

9 PV


Custom Calculation (FF_CCL)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 9 IN

2 TAG_DESC 10 OUT_D

3 STRATEGY 11 PV_D

4 ALERT_KEY 12 IN_D

5 MODE_BLK 13 BLOCK_ALM

6 BLOCK_ERR 14 R_DS256

7 OUT 15 R_DS257

8 PV

Custom Input (FF_CI)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 20 UPDATE_EVT

2 TAG_DESC 21 BLOCK_ALM

3 STRATEGY 22 ALARM_SUM

4 ALERT_KEY 23 ACK_OPTION

5 MODE_BLK 24 ALARM_HYS

6 BLOCK_ERR 25 HI_HI_PRI

7 PV 26 HI_HI_LIM

8 OUT 27 HI_PRI

9 SIMULATE 28 HI_LIM

10 XD_SCALE 29 LO_PRI

11 OUT_SCALE 30 LO_LIM

12 GRANT_DENY 31 LO_LO_PRI

13 IO_OPTS 32 LO_LO_LIM

14 STATUS_OPTS 33 HI_HI_ALM

15 CHANNEL 34 HI_ALM

16 L_TYPE 35 LO_ALM

17 LOW_CUT 36 LO_LO_ALM

18 PV_FTIME 37 R_DS256

19 FIELD_VAL 38 R_DS257


Custom Output (FF_CO)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 17 CAS_IN

2 TAG_DESC 18 SP_RATE_DN

3 STRATEGY 19 SP_RATE_UP

4 ALERT_KEY 20 SP_HI_LIM

5 MODE_BLK 21 SP_LO_LIM

6 BLOCK_ERR 22 CHANNEL

7 PV 23 FSTATE_TIME

8 SP 24 FSTATE_VAL

9 OUT 25 BKCAL_OUT

10 SIMULATE 26 RCAS_IN

11 PV_SCALE 27 SHED_OPT

12 XD_SCALE 28 RCAS_OUT

13 GRANT_DENY 29 UPDATE_EVT

14 IO_OPTS 30 BLOCK_ALM

15 STATUS_OPTS 31 R_DS256

16 READBACK 32 R_DS257

Control Selector (FF_CS)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 12 SEL_2

2 TAG_DESC 13 SEL_3

3 STRATEGY 14 SEL_TYPE

4 ALERT_KEY 15 BKCAL_IN

5 MODE_BLK 16 OUT_HI_LIM

6 BLOCK_ERR 17 OUT_LO_LIM

7 OUT 18 BKCAL_SEL_1

8 OUT_SCALE 19 BKCAL_SEL_2

9 GRANT_DENY 20 BKCAL_SEL_3

10 STATUS_OPTS 21 UPDATE_EVT

11 SEL_1 22 BLOCK_ALM


Device Control (FF_DC)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 26 PERMISSIVE_D

2 TAG_DESC 27 RESET_D

3 STRATEGY 28 ACCEPT_D

4 ALERT_KEY 29 DC_STATE

5 MODE_BLK 30 TRAVEL_TIMER

6 BLOCK_ERR 31 CFM_PASS_TIME

7 PV_D 32 CFM_ACT1_TIME

8 SP_D 33 TRIP_TIME

9 OUT_D 34 IGNORE

10 OUT_STATE 35 FAIL

11 GRANT_DENY 36 ALARM_SUM

12 DEVICE_OPTS 37 BKCAL_IN_D

13 STATUS_OPTS 38 TRK_IN_D

14 IN_D 39 CAS_IN_D

15 ACK_OPTION 40 BKCAL_OUT_D

16 FAIL_PRI 41 RCAS_IN_D

17 ACCEPT_PRI 42 RCAS_OUT_D

18 IGNORE_PRI 43 SHED_OPT

19 UPDATE_EVT 44 CRACK_TIMER

20 BLOCK_ALM 45 DELAY_TIMER

21 FAIL_ALM 46 CFM_ACT2_TIME

22 ACCEPT_ALM 47 CRACK_TIME

23 IGNORE_ALM 48 DELAY_TIME

24 SHUTDOWN_D 49 RESTART_TIME

25 INTERLOCK_D


Discrete Input (FF_DI)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 13 IO_OPTS

2 TAG_DESC 14 STATUS_OPTS

3 STRATEGY 15 CHANNEL

4 ALERT_KEY 16 PV_FTIME

5 MODE_BLK 17 FIELD_VAL_D

6 BLOCK_ERR 18 UPDATE_EVT

7 PV_D 19 BLOCK_ALM

8 OUT_D 20 ALARM_SUM

9 SIMULATE_D 21 ACK_OPTION

10 XD_STATE 22 DISC_PRI

11 OUT_STATE 23 DISC_LIM

12 GRANT_DENY 24 DISC_ALM

Discrete Output (FF_DO)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 13 IO_OPTS

2 TAG_DESC 14 STATUS_OPTS

3 STRATEGY 15 READBACK_D

4 ALERT_KEY 16 CAS_IN_D

5 MODE_BLK 17 CHANNEL

6 BLOCK_ERR 18 FSTATE_TIME

7 PV_D 19 FSTATE_VAL_D

8 SP_D 20 BKCAL_OUT_D

9 OUT_D 21 RCAS_IN_D

10 SIMULATE_D 22 SHED_OPT

11 PV_STATE 23 RCAS_OUT_D

12 XD_STATE 24 UPDATE_EVT

13 GRANT_DENY 25 BLOCK_ALM


Dead Time (FF_DT)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 10 STATUS_OPTS

2 TAG_DESC 11 IN

3 STRATEGY 12 FOLLOW

4 ALERT_KEY 13 DEAD_TIME

5 MODE_BLK 14 BAL_TIME

6 BLOCK_ERR 15 OUTAGE_LIM

7 OUT 16 UPDATE_EVT

8 OUT_Range 17 BLOCK_ALM

9 GRANT_DENY

Input Selector (FF_IS)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 13 IN_3

2 TAG_DESC 14 IN_4

3 STRATEGY 15 DISABLE_1

4 ALERT_KEY 16 DISABLE_2

5 MODE_BLK 17 DISABLE_3

6 BLOCK_ERR 18 DISABLE_4

7 OUT 19 SELECT_TYPE

8 OUT_RANGE 20 MIN_GOOD

9 GRANT_DENY 21 SELECTED

10 STATUS_OPTS 22 OP_SELECT




Integrator (Totalizer) (FF_IT)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 21 REV_FLOW1

2 TAG_DESC 22 REV_FLOW2

3 STRATEGY 23 RESET_IN

4 ALERT_KEY 24 STOTAL

5 MODE_BLK 25 RTOTAL

6 BLOCK_ERR 26 SRTOTAL

7 TOTAL_SP 27 SSP

8 OUT 28 INTEG_TYPE

9 OUT_RANGE 29 INTEG_OPTS

10 GRANT_DENY 30 CLOCK_PER

11 STATUS_OPTS 31 PRE_TRIP

12 IN_1 32 N_RESET

13 IN_2 33 PCT_INCL

14 IN 34 GOOD_LIM

15 OUT_TRIP 35 UNCERT_LIM

16 TIME_UNIT1 36 OP_CMD_INT

17 TIME_UNIT2 37 OUTAGE_LIM

18 UNIT_CONV 38 RESET_CONFIRM

19 PULSE_VAL1 39 UPDATE_EVT

20 PULSE_VAL2 40 BLOCK_ALM

Lead Lag (FF_LL)


2 TAG_DESC 11 IN

3 STRATEGY 12 FOLLOW

4 ALERT_KEY 13 LAG_TIME

5 MODE_BLK 14 LEAD_TIME

6 BLOCK_ERR 15 BAL_TIME

7 OUT 16 OUTAGE_LIM

8 OUT_RANGE 17 UPDATE_EVT



Multiple Analog Input (FF_MAI)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 10 OUT_3

2 TAG_DESC 11 OUT_4

3 STRATEGY 12 OUT_5

4 ALERT_KEY 13 OUT_6

5 MODE_BLK 14 OUT_7

6 BLOCK_ERR 15 OUT_8

7 CHANNEL 16 UPDATE_EVT

8 OUT_1 17 BLOCL_ALM

9 OUT_2

Multiple Analog Output (FF_MAO)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 15 IN_8

2 TAG_DESC 16 MO_OPTS

3 STRATEGY 17 FSTATE_TIME

4 ALERT_KEY 18 FSTATE_VAL1

5 MODE_BLK 19 FSTATE_VAL2

6 BLOCK_ERR 20 FSTATE_VAL3

7 CHANNEL 21 FSTATE_VAL4

8 IN_1 22 FSTATE_VAL5




12 IN_5 26 FSTATE_STATUS




Multiple Discrete Input (FF_MDI)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 10 OUT_D3

2 TAG_DESC 11 OUT_D4

3 STRATEGY 12 OUT_D5

4 ALERT_KEY 13 OUT_D6

5 MODE_BLK 14 OUT_D7

6 BLOCK_ERR 15 OUT_D8

7 CHANNEL 16 UPDATE_EVT

8 OUT_D1 17 BLOCL_ALM

9 OUT_D2

Multiple Discrete Output (FF_MDO)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 15 IN_D8

2 TAG_DESC 16 MO_OPTS

3 STRATEGY 17 FSTATE_TIME

4 ALERT_KEY 18 FSTATE_VAL_D1

5 MODE_BLK 19 FSTATE_VAL_D2

6 BLOCK_ERR 20 FSTATE_VAL_D3

7 CHANNEL 21 FSTATE_VAL_D4

8 IN_D1 22 FSTATE_VAL_D5




12 IN_D5 26 FSTATE_STATUS

13 IN_D6 27 UPDATE_EVT

14 IN_D7 28 BLOCK_ALM


Manual Loader (FF_ML)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 22 TRK_SCALE

2 TAG_DESC 23 TRK_IN_D

3 STRATEGY 24 TRK_VAL

4 ALERT_KEY 25 UPDATE_EVT

5 MODE_BLK 26 BLOCK_AM

6 BLOCK_ERR 27 ALARM_SUM

7 PV 28 ACK_OPTION

8 OUT 29 ALARM_HYS

9 PV_SCALE 30 HI_HI_PRI

10 OUT_SCALE 31 HI_HI_LIM

11 GRANT_DENY 32 HI_PRI

12 CONTROL_OPTS 33 HI_LIM

13 STATUS_OPTS 34 LO_PRI

14 IN 35 LO_LIM

15 PV_FTIME 36 LO_LO_PRI

16 BKCAL_IN 37 LO_LO_LIM

17 OUT_HI_LIM 38 HI_HI_ALM

18 OUT_LO_LIM 39 HI_ALM

19 ROUT_IN 40 LO_ALM

20 SHED_OPT 41 LO_LO_ALM

21 ROUT_OUT


Output Splitter (FF_OS)


2 TAG_DESC 14 CAS_IN

3 STRATEGY 15 BKCAL_OUT

4 ALERT_KEY 16 IN_ARRAY

5 MODE_BLK 17 OUT_ARRAY

6 BLOCK_ERR 18 LOCKVAL

7 SP 19 BKCAL_IN_1

8 OUT_1 20 BKCAL_IN_2

9 OUT_2 21 BAL_TIME

10 OUT_1_RANGE 22 HYSTVAL

11 OUT_2_RANGE 23 UPDATE_EVT



P, PD Controller (FF_PD)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 34 SHED_OPT

2 TAG_DESC 35 RCAS_OUT

3 STRATEGY 36 ROUT_OUT

4 ALERT_KEY 37 TRK_SCALE

5 MODE_BLK 38 TRK_IN_D

6 BLOCK_ERR 39 TRK_VAL

7 PV 40 FF_VAL

8 SP 41 FF_SCALE

9 OUT 42 FF_GAIN

10 PV_SCALE 43 UPDATE_EVT

11 OUT_SCALE 44 BLOCK_ALM


13 CONTROL_OPTS 46 ACK_OPTION

14 STATUS_OPTS 47 ALARM_HYS

15 IN 48 HI_HI_PRI

16 PV_FTIME 49 HI_HI_LIM

17 BYPASS 50 HI_PRI

18 CAS_IN 51 HI_LIM

19 SP_RATE_DN 52 LO_PRI

20 SP_RATE_UP 53 LO_LIM

21 SP_HI_LIM 54 LO_LO_PRI

22 SP_LO_LIM 55 LO_LO_LIM

23 GAIN 56 DV_HI_PRI

24 BIAS 57 DV_HI_LIM

25 BAL_TIME 58 DV_LO_PRI

26 RATE 59 DV_LO_LIM

27 BKCAL_IN 60 HI_HI_ALM

28 OUT_HI_LIM 61 HI_ALM

29 OUT_LO_LIM 62 LO_ALM

30 BKCAL_HYS 63 LO_LO_ALM

31 BKCAL_OUT 64 DV_HI_ALM

32 RCAS_IN 65 DV_LO_ALM

33 ROUT_IN


PID, PI, I Controller (FF_PID)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 34 SHED_OPT

2 TAG_DESC 35 RCAS_OUT

3 STRATEGY 36 ROUT_OUT




7 PV 40 FF_VAL

8 SP 41 FF_SCALE

9 OUT 42 FF_GAIN

10 PV_SCALE 43 UPDATE_EVT

11 OUT_SCALE 44 BLOCK_ALM


13 CONTROL_OPTS 46 ACK_OPTION

14 STATUS_OPTS 47 ALARM_HYS

15 IN 48 HI_HI_PRI

16 PV_FTIME 49 HI_HI_LIM

17 BYPASS 50 HI_PRI

18 CAS_IN 51 HI_LIM

19 SP_RATE_DN 52 LO_PRI

20 SP_RATE_UP 53 LO_LIM

21 SP_HI_LIM 54 LO_LO_PRI

22 SP_LO_LIM 55 LO_LO_LIM

23 GAIN 56 DV_HI_PRI

24 RESET 57 DV_HI_LIM

25 BAL_TIME 58 DV_LO_PRI

26 RATE 59 DV_LO_LIM

27 BKCAL_IN 60 HI_HI_ALM

28 OUT_HI_LIM 61 HI_ALM

29 OUT_LO_LIM 62 LO_ALM

30 BKCAL_HYS 63 LO_LO_ALM


32 RCAS_IN 65 DV_LO_ALM

33 ROUT_IN


Ratio Station (FF_RA)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 30 RCAS_IN

2 TAG_DESC 31 SHED_OPT

3 STRATEGY 32 RCAS_OUT




7 PV 36 UPDATE_EVT

8 SP 37 BLOCK_ALM

9 OUT 38 ALARM_SUM

10 PV_SCALE 39 ACK_OPTION

11 OUT_SCALE 40 ALARM_HYS

12 GRANT_DENY 41 HI_HI_PRI

13 CONTROL_OPTS 42 HI_HI_LIM

14 STATUS_OPTS 43 HI_PRI

15 IN 44 HI_LIM

16 PV_FTIME 45 LO_PRI

17 IN_1 46 LO_LIM

18 RA_FTIME 47 LO_LO_PRI

19 CAS_IN 48 LO_LO_LIM

20 SP_RATE_DN 49 DV_HI_PRI

21 SP_RATE_UP 50 DV_HI_LIM

22 SP_HI_LIM 51 DV_LO_PRI

23 SP_LO_LIM 52 DV_LO_LIM

24 GAIN 53 HI_HI_ALM

25 BKCAL_IN 54 HI_ALM

26 OUT_HI_LIM 55 LO_ALM

27 OUT_LO_LIM 56 LO_LO_ALM


29 BAL_TIME 58 DV_LO_ALM


Signal Characterizer (FF_SC)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 10 Y_RANGE

2 TAG_DESC 11 GRANT_DENY

3 STRATEGY 12 IN_1

4 ALERT_KEY 13 IN_2

5 MODE_BLK 14 SWAP_2

6 BLOCK_ERR 15 CURVE_X

7 OUT_1 16 CURVE_Y

8 OUT_2 17 UPDATE_EVT

9 X_RANGE 18 BLOCK_ALM

Setpoint Ramp Generator (FF_SPG)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 21 TIME_POSN

2 TAG_DESC 22 TIME_POSN_T

3 STRATEGY 23 OP_CMD_SPG

4 ALERT_KEY 24 SPG_STATE

5 MODE_BLK 25 PRE_OUT

6 BLOCK_ERR 26 RESET_IN

7 OUT 27 BAL_TIME

8 OUT_RANGE 28 OUTAGE_LIM

9 GRANT_DENY 29 UPDATE_EVT


11 START_VAL 31 ALARM_SUM

12 DURATION 32 ACK_OPTION

13 TIME_UNITS 33 ALARM_HYS

14 BKCAL_IN 34 DV_HI_PRI

15 START 35 DV_HI_LIM

16 START_TYPE 36 DV_LO_PRI

17 PAUSE 37 DV_LO_LIM

18 PAUSE_CAUSE 38 DV_HI_ALM

19 AUTO_CYCLE 39 DV_LO_ALM

20 STEP_POSN


Timer (FF_TMR)

Index Parameter Mnemonic Index Parameter Mnemonic1 ST_REV 16 IN_D2

2 TAG_DESC 17 IN_D3

3 STRATEGY 18 IN_D4

4 ALERT_KEY 19 COMB_TYPE

5 MODE_BLK 20 TIMER_TYPE

6 BLOCK_ERR 21 PRE_OUT_D

7 PV_D 22 N_START

8 OUT_D 23 OUT_EXP

9 TIMER_SP 24 OUT_REM

10 PV_STATE 25 RESET_IN

11 OUT_STATE 26 QUIES_OPT

12 GRANT_DENY 27 TIME_UNITS

13 INVERT_OPTS 28 UPDATE_EVT


15 IN_D1


Glossary of Terms

Bus is an H1 fieldbus cable between a host and field devices connected to multiple segments, sometimes through the use ofrepeaters.

Communications Stack is a layered software supporting communication between devices. It is the device communicationssoftware which provides encoding and decoding of User Layer messages, deterministic control of message transmission, andmessage transfer.

Control Loop is a group of function blocks (FBs) that perform at a specified rate within a fieldbus device or distributedacross the fieldbus network.

Data Link Layer (DLL) controls transmission of messages onto the fieldbus, and manages access to the fieldbus through theLink Active Scheduler (LAS).

Deterministic is the ability to measure the maximum worst-case delay in delivery of a message between any two nodes in anetwork. Any network protocol that depends on random delays to resolve mastership is nondeterministic.

Device Alerts are produced by fieldbus devices to provide status information to the ToolboxST application and AlarmViewer.

Device Description (DD) provides an extended description of each object in the virtual field device (VFD), and includesinformation needed for a control system or host to understand the meaning of data in the VFD.

Discrete Input (DI) means the signal is from the field device to the host system.

Discrete Output (DO) means the signal is generated by the host system and transmitted to a field device.

Fieldbus is a digital, two-way, multi-drop communication link among intelligent measurement and control devices. It servesas a local area network (LAN) for advanced process control, remote input/output and high-speed factory automationapplications.

Fieldbus Access Sublayer (FAS) maps the fieldbus message specification (FMS) onto the data link layer (DLL).

Flexible Function Block (FFB) is similar to a standard FB, except that an application specific algorithm created by aprogramming tool determines the function of the block, the order and definition of the block parameters, and the time requiredto perform the block. FFBs are typically used for control of discrete processes and for hybrid (batch) processes. A PLC can bemodeled as a flexible function block device.

Gateway is a computer that translates another fieldbus-related protocol to FOUNDATION Fieldbus Function Block Parametersfieldbus protocol, for example, HART® or Modbus® to FOUNDATION Fieldbus Function Block Parameters fieldbus protocol.

H1 is a term used to describe a fieldbus network operating at 31.25 kbit/s. They have control functions in the form ofconfigurable blocks (scaling, filtering, PID, and so forth) that are integrated with the rest of the control logic in the Mark VIecontroller.

H1 Field Device is a fieldbus device connected directly to an H1 fieldbus. Typical H1 field devices are valves andtransmitters.

H1 Repeater is an active, bus-powered or non-bus-powered device used to extend the range over which signals can becorrectly transmitted and received for a given medium. A maximum of four repeaters and/or active couplers can be usedbetween any two devices on a H1 fieldbus network. Repeaters connect segments together to form larger networks.

FOUNDATION HSE is the FOUNDATION Fieldbus Function Block Parameters fieldbus backbone network running Ethernet andIP.

HSE Field Device is a fieldbus device connected directly to a HSE fieldbus. Typical HSE field devices are HSE linkingdevices, HSE field devices running function blocks (FBs), and host computers.

HSE Linking Device (PFFA) is a device used to interconnect H1 fieldbus networks and segments to HSE to create a largersystem. A system can have no more than 20 linking devices. Each linking device can have up to 4 links, with no more than 16fieldbus devices per link.

GEH-6761G Glossary of Terms 53For public disclosure

Input/Output (I/O) Subsystem Interface is a device used to connect other types of communications protocols to afieldbus Segment(s).

Interoperability is the capability for a device from one manufacturer to interact with that of another manufacturer on afieldbus network without loss of functionality.

Interoperability Test Kit (ITK) is used by the foundation to register devices and confirm compliance with the relevantFOUNDATION Fieldbus Function Block Parameters standards. This is a pass/fail test. Only devices passing the full suite oftests receive the FOUNDATION Fieldbus Function Block Parameters’s official registration mark.

IS Intrinsic Safety (IS) is an explosion protection method according to IEC 60079-7 and 11, which allows the flammableatmosphere to come in contact with the electrical equipment without introducing a potential hazard.

Link is the logical medium by which H1 fieldbus devices are interconnected. It is composed of one or more physicalsegments interconnected by bus repeaters or couplers. All of the devices on a link share a common schedule which isadministered by that link's current link active scheduler (LAS). Each H1 link can support up to 16 field devices. However, thelarger the number of devices on a link, the slower the performance of the system is. The number of field devices and functionblocks communicating on a link can significantly affect the performance of the system.

Link Object contains information to link FB I/O parameters in the same device and between different devices. The linkobject links directly to a virtual communications relationship (VCR).

MAC Address is a unique hardware address given to each Ethernet interface chip.

Macrocycle is a single iteration of a schedule within a device. The unscheduled (free asynchronous) time can be configuredas 30%, 40%, or 50% of the macrocycle time through the segment Unshceduled Overhead Percent property. The unscheduledtime calculation allows for the spare capacity requirements (such as alarm transmission, setpoint changes, and so forth). Themacrocycle time typically ranges from 250 ms to several seconds (depending on the nature of the device used) and isconfigured for each fieldbus network/segment. Loops can be moved to another segment or macrocycles can be slowed if asegment has insufficient unscheduled time.

Macrocycle Timeline Viewer is used to:

• View which assigned fieldbus function blocks perform at what time during the macrocycle.• View time allotted during the unscheduled portion of the macrocycle for the reading of views of assigned fieldbus

function blocks configured for placement on EGD.• Refresh the macrocycle timeline view by invoking a method which recalculates the macrocycle timeline calculation

algorithm.• Switch to view a different segment’s macrocycle timeline.• Print the displayed macrocycle view.

Methods are optional (but highly desirable) additions to DDs. Methods are used to define and automate procedures (such ascalibration) for operation of field devices.

Network Management (NM) permits FOUNDATION network manager (NMgr) entities to conduct management operationsover the network by using network management agents (NMAs). Each NMA is responsible for managing the communicationswithin a device. The NMgr and NMA communicate through use of the fieldbus messaging specification (FMS) and VCR.

Object Dictionary (OD) contains all FB, resource block (RB) and transducer block (TB) parameters used in a device.Through these parameters, the blocks can be accessed over the fieldbus network.

Physical Layer receives messages from the communications stack and converts the messages into physical signals on thefieldbus transmission medium, and vice-versa.

Resource Block (RB) schedules define when FBs perform and when data and status is published on the bus.

Segment is a section of an H1 fieldbus that is terminated in its characteristic impedance. Segments can be linked byrepeaters to form a longer H1 fieldbus. Each segment can include up to 32 H1 devices.

54 Mark VIe Control FOUNDATION Fieldbus InterfaceFor public disclosure

Standard Function Block (FB) is built into fieldbus devices as needed to achieve the desired control functionality.Automation functions provided by standard FBs include analog input (AI), analog output (AO) andproportional/integral/derivative (PID) control. The Fieldbus Foundation has released specifications for 21 types of standardFBs. There can be many types of FBs in a device. The order and definition of standard FB parameters are fixed and definedby the specifications.

Synchronous Macrocycle Communications is the scheduled, time dependent portion of the macrocyclecommunications. Block logic is transmitted during this time.

System Management (SM) synchronizes execution of FBs, the communication of FB parameters on the fieldbus, handlespublication of the time of day to all devices, automatic assignment of device addresses, and searching for parameter names(tags) on the fieldbus.

Tag is a collection of attributes that specify a control loop or a process variable, a measured input, a calculated value, or somecombination of these, and all associated control and output algorithms. Each tag is unique.

Tag ID is the unique alphanumeric code assigned to inputs, outputs, equipment items, and control blocks. The tag ID caninclude a plant area identifier.

User Application is based on blocks, including RBs, FBs and TBs, which represent different types of application functions.

User Layer provides scheduling of FBs, as well as DDs which allow the host system to communicate with devices withoutthe need for custom programming.

Virtual Communication Relationship (VCR) is the configured application layer channels that provide for the transfer ofdata between applications. FOUNDATION fieldbus technology describes three types of VCRs: Publisher/Subscriber,Client/Server, and Source/Sink.

Virtual Field Device (VFD) is used to remotely view local device data described in the object dictionary. A typical devicehas at least two VFDs.

For public disclosure