Mark* VIe Control FOUNDATION Fieldbus Interface Application Guide

Transcription

1 GEH-6761C Mark* VIe Control FOUNDATION Fieldbus Interface Application Guide

2 These instructions do not purport to cover all details or variations in equipment, nor to provide for every possible contingency to be met during installation, operation, and maintenance. The information is supplied for informational purposes 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 reflected herein. It is understood that GE may make changes, modifications, or improvements to the equipment referenced herein or to the document itself at any time. This document is intended for trained personnel familiar with the GE products referenced herein. This document is approved for public disclosure. GE may have patents or pending patent applications covering subject matter in this document. The furnishing of this document 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 for particular purpose. For further assistance or technical information, contact the nearest GE Sales or Service Office, or an authorized GE Sales Representative. Revised: Dec 2014 Issued: Mar 2011 Copyright General Electric Company, All rights reserved. * 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 controls.doc@ge.com

3 Document Updates Location Chapter, Overview Description Updates to provide additional functional description for customer communications protocol, as well as a diagram displaying redundancy Related Documents GEI , Mark VIe Control FOUNDATION Fieldbus Linking Device (PFFA) Instruction Guide GEI , WorkstationST* Device Manager Gateway Instruction Guide GEI , Mark VIe Control FOUNDATION Fieldbus Block Library Instruction Guide GEH-6762, Mark VIe Control FOUNDATION Fieldbus Interface User Guide GHT , How to Qualify a FOUNDATION Fieldbus Field Device Application Guide GEH-6761C 3

4 Contents 1 Overview Concepts Configuration System Limits Alerts Foundation Fieldbus Function Blocks Foundation Fieldbus Transducer Blocks Foundation Fieldbus Resource Blocks Connecting Blocks Asynchronous Control Foundation Fieldbus s Linking Devices Fieldbus Devices HMI Features GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

5 1 Overview The FOUNDATION Fieldbus interface is a fieldbus protocol based on international standards and designed for applications in manufacturing, process automation, and buildings automation. The guidelines for this fieldbus standard are published by the Fieldbus Foundation. For compatibility testing guidelines and further details, refer to GEH-6808, ControlST Software Suite How-to Guides, the section, How to Qualify a FOUNDATION Fieldbus Field Device. A variety of component types are certified as compatible or standardized with fieldbus technology and can be interchanged for a similar component type, regardless of component manufacturer. This allows customers to use a wider range of equipment in the control system. Replacing a certified device from one manufacturer with a certified device from another manufacturer (interoperability) is possible because the devices and software conform to the same standard. The Fieldbus Foundation tests and registers the devices to ensure interoperability of registered instruments from multiple vendors. This enables the user to select the best instruments for the application, regardless of the host system supplier. GE has performed additional compatibility testing for Mark VIe control applications and the ToolboxST application includes the Device Definition (DD). If additional devices are required, they can be added to the system. Fieldbus modules, such as the FOUNDATION Fieldbus H1 to HSE Linking Device, communicate on the Mark VIe control IONet and are fully compatible with ControlST Software Suite V04.03 or higher, which is a Class 61b Registered Host. ToolboxST application software is used to configure and monitor fieldbus modules, as well as all devices at the I/O and supervisory levels. For reliability, two linking devices can be connected with a RS-232C null modem cable to form one logical linking device (a redundant set) in a primary or secondary configuration. FOUNDATION Fieldbus features include: 4 H1 ports with galvanic isolation (transformer) 16 field devices per segment IECTM 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 Application Guide GEH-6761C 5

6 Redundant Controllers Switches IONet HSE 100 MB Ethernet Redundant Linking Devices H1 Networks per Linking Device at KB (twisted-pair) Redundant Power Conditioners Field Devices FOUNDATION Fieldbus Redundant H1 to HSE Linking Device and Power Converter 1.1 Concepts Refer to the Glossary of Terms for a list of related terms. FOUNDATION fieldbus technology uses H1 and HSE networks, linking devices, attached segments, and field devices with function blocks to provide data for processing and interaction between the field devices and Mark VIe controller. The following are brief descriptions of some major concepts used in the implementation and operation of FOUNDATION fieldbus technology with the Mark VIe control H1 H1 is a fieldbus network operating at kbit/s. The H1 network interconnects devices such as pressure or temperature transmitters and actuators on a field network. It is designed to operate on existing twisted pair instrument cabling with power and signal on the same wire. H1 supports intrinsic safety (IS) applications. H1 devices contain a function block application, act as a publisher and subscriber of process variables, transmit alarms and trends, and provide server functionality for host access and management functions. Devices can act as a scheduler and time master for regulating communication on a fieldbus segment. They are also used for bus interfaces in process control systems or in linking devices. Capable of controlling bus communications and many connections to multiple devices, they support both client and server applications. H1 technology enables field instruments and other devices to perform control functions reducing the load on plant computers and workstations. Since the H1 network is digital, I/O conversion subsystems are eliminated. 6 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

7 1.1.2 HSE Like H1, HSE is an international standard (IEC 61158). HSE is used as a control backbone. Running at 100 Mbit/s, the technology 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 for high-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 supports interoperability between disparate controllers and gateways in the same way that H1 supports interoperability between transmitters and actuators from different suppliers. FFBs in HSE devices can be set up using programming languages such as those found in the international standard IEC HSE also supports standard Ethernet wiring, including the use of fiber-optic cable to provide cost-effective electrical isolation between plant areas or immunity from distortion through noisy environments. Application Guide GEH-6761C 7

8 1.1.3 Linking Device Refer to GEI , Mark VIe Control FOUNDATION Fieldbus Linking Device. The linking device sends processed data from one H1 link to another H1 link, and sends and receives data from the H1 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 its compact size allows it to be used in a DIN rail assembly. It provides the following functions: It supports up to four separate H1 links. In each of these links, the linking device operates as the Link Master as well as the 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 the 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 Blocks Refer to the Glossary of Terms for a list of related terms. To ensure device interoperability FOUNDATION fieldbus technology uses a fully specified, standard user layer based on blocks and 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) and transducer blocks offer an interface to sensors such as temperature, pressure, and flow, and actuators for valves. 8 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

9 Blocks are incorporated into fieldbus devices to achieve the desired device functionality, as well as to define a wide range of features and behaviors that must work in a standard way for devices to interoperate. For example, a simple temperature transmitter 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 only a simple transmitter and a control valve. Refer to Appendix A FOUNDATION Fieldbus Function Block s. Each block's parameters are represented by object descriptions that define how the parameters are communicated on the fieldbus 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. As specified by the FBAP, a fieldbus device must have a resource block and at least one function block with input and/or output parameters that link to other function blocks, either in the same device or in separate devices by means of the bus. The link object defines the connection. Each input/output parameter passed has a value and a status. The status portion of each parameter carries information on the quality of each value, of good, uncertain, or bad, with substatus further elaborating on the 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 features must 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 and communication of function block parameters on the fieldbus. This function, along with publication of the time of day to all devices, automatic switch over to a redundant time publisher, assignment of device addresses, and searching for parameter names or tags on the fieldbus, are handled by system management (SM) and network management (NM). Control in the field may provide faster control strategy execution but has redundancy implications that must be understood before implementing it. Application Guide GEH-6761C 9

10 Refer to GEH-6762, Mark VIe Control FOUNDATION Fieldbus Interface User Guide, the section Attached Segments, for information regarding macrocycle and macrocycle timeline. 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 in the 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 blocks used in devices on a segment, the interconnections between blocks (in the same or different devices) on a FOUNDATION fieldbus segment, and minimum macrocycle requirements by device manufacturers. Macrocycle and controller task execution rate are not synchronized. It may take as much as one task execution time plus one macrocycle time to complete the control strategy in a task. Information about the macrocycle timeline can be obtained from the Macrocycle Timeline Viewer as displayed in the following figure. Macrocycle Timeline Viewer Refer to GEH-6762, Mark VIe Control FOUNDATION Fieldbus Interface User Guide, the section Configure an Attached Segment Macrocycle. 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 (time allowed for asynchronous communications) can be configured for 30%, 40%, or 50% of the total macrocycle time. If more than the configured time is consumed, the next longest macrocycle is selected by the system. 10 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

11 2 Configuration Refer to GEH-6762, Mark VIe Control FOUNDATION Fieldbus Interface User Guide for information on configuring fieldbus devices. All configuration of fieldbus linking devices and attached segments, fieldbus devices, fieldbus blocks, and related parameters and properties is performed in the ToolboxST* application. The configurations are displayed and edited in the Component Editor s Hardware and Software tabs. The addition of fieldbus devices to a H1 segment involves the use of a placeholder. A fieldbus device placeholder is a representation of a fieldbus device. They are created inside a Mark VIe controller. Before a placeholder can be tied to a physical fieldbus device, it must go through the commissioning process. After commissioning, the fieldbus device becomes live and active in the system and is included in the download process of the controller. 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 what the device is and its version are read from the DD files. When configuring a fieldbus device, the device type and revision number must be the same as those in the ToolboxST application or the commissioning of the device produces an error. The DD 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 function blocks in a fieldbus category in addition to the traditional Mark VIe control function block categories. FOUNDATION fieldbus function blocks can only be used in the special FOUNDATION fieldbus task. Mark VIe control function blocks are also allowed to operate in this special task in addition to the normal Mark VIe control tasks. 2.1 System Limits The 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. Application Guide GEH-6761C 11

12 In addition, the following guidelines are useful to consider when configuring large applications or applications containing both 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 FOUNDATION Fieldbus alerts. The Mark VIe controller is capable of supporting up to 200 PAIC-equivalent I/O packs per IONet. Each PFFA represents a 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 therefore needs to understand the minimum amount of Mark VIe hardware required to support it. Each MOV currently requires four VCRs. Dividing the total number of devices (1100) by the number supportable per segment (16) yields a minimum of 69 H1 segments 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 will generate 4400 VCRs, which spread evenly across 18 PFFAs comes to 244 per linking device. This number of VCRs is well within the limit of 400 for a single PFFA, as well as the limit of 2048 for a single controller. The minimum hardware necessary to achieve this configuration is therefore a single Mark VIe controller, using a single IONet, with 18 fully populated PFFAs. 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 Alerts FOUNDATION Fieldbus technology supports four types of alerts: analog alerts, discrete alerts, field diagnostic alerts, and update events. Analog Alerts annunciate when an analog input value reaches a configured limit and are available on function blocks that support 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. Discrete Alerts 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 maintenance related 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 a static parameter an alert is issued to notify the user of a change in configuration. For some parameters, the update event displays which parameter changed and in some cases what the value changed to. 12 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

13 2.3 FOUNDATION Fieldbus Function Blocks Function blocks provide the control system behavior. The input and output parameters of function blocks can be linked over the fieldbus. The execution of each function block is precisely scheduled. There can be many function blocks in a single user application. Only variables from the output of FOUNDATION fieldbus function blocks should be used in control application programs. FOUNDATION fieldbus parameter values from data views should not be used for control purposes because they are not synchronous or deterministic. The ToolboxST application supports the following fieldbus function blocks in standard and enhanced 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 Application Guide GEH-6761C 13

14 Block Label Operational Icon 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 14 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

15 Block Label Operational Icon Multiple Analog Input FF_MAI Multiple Analog Output FF_MAO Multiple Discrete Input FF_MDI Multiple Discrete Output FF_MDO Manual Loader FF_ML Output Splitter FF_OS P, PD Controller FF_PD Application Guide GEH-6761C 15

16 Block Label Operational Icon PID, PI, I Controller FF_PID Ratio Station FF_RA Signal Characterizer FF_SC Setpoint Ramp Generator FF_SPG Timer FF_TMR Unassigned Unassigned Refer to GEH-6762, Mark VIe Control FOUNDATION Fieldbus Interface User Guide 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-hand corner 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. The operational 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 the macrocycle is determined by connection. 2.4 FOUNDATION Fieldbus Transducer Blocks The transducer blocks are used to configure devices. Transducer blocks decouple function blocks from the local input and output functions required to read sensors and command output hardware. They contain information such as calibration date and sensor type. There is usually one transducer block channel for each input or output of a function block. This type of block is not attached to any other blocks in the Mark VIe controller. 16 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

17 2.5 FOUNDATION Fieldbus Resource Blocks The 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 any other blocks in the Mark VIe controller. 2.6 Connecting Blocks Fieldbus function blocks and other Mark VIe function blocks can be connected in any way as long as the data types match on both pins being connected. Use the standard wiring tool in the ToolboxST application. The ToolboxST application can create the 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 Control The execution of fieldbus related blockware in the controller does not depend upon the reception of inputs from the linking device and does not attempt to synchronize with the fieldbus macrocycle. Once the ToolboxST application calculates the minimum macrocycle period necessary based upon the configured logic (the macrocycle period is padded such that it is a multiple of the controller s frame rate). It then configures each fieldbus related task with a frame multiplier and schedule offset corresponding to the macrocycle period. Since the controller clocks and the fieldbus link times are not synchronized, skew can occur and the controller may be executing on inputs from the previous macrocycle. While this leads to less responsive control loops since it can take effectively two macrocycles to react to changing input stimulus, this approach allows fieldbus tasks to connect blocks from devices 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 Application Guide GEH-6761C 17

18 2.8 FOUNDATION Fieldbus s Refer to Appendix A FOUNDATION Fieldbus Function Block s for a list of the block parameters and their descriptions. FOUNDATION fieldbus blocks contain parameters which can be configured and applied to commissioned online fieldbus devices. The fieldbus block parameters are edited using the ToolboxST Summary View s Editor. The parameters of FOUNDATION fieldbus transducer, and resource blocks are edited in the Hardware tab while parameters of FOUNDATION fieldbus function blocks are edited in either the Software or Hardware tabs. To support homogeneity with the ToolboxST application, fieldbus parameters that are listed on a function block s View 1 parameter list can be placed on EGD. s on EGD display the following properties in the Hardware tab parameter grid: 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 the Hardware 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 18 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

19 Refer to GEI , Mark VIe Control FOUNDATION Fieldbus Linking Device. 2.9 Linking Devices The ToolboxST Hardware tab Summary View displays information about linking devices. When the system is online, the Hardware 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 Application Guide GEH-6761C 19

20 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. This information is provided by the alarm and diagnostic subsystems inside the Mark VIe controller. 20 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

21 When a fieldbus device is added to a system, it acts as a placeholder until it is commissioned. The commissioning process makes the fieldbus device live and active in the system Fieldbus Devices The ToolboxST Hardware tab displays information about fieldbus devices. When the system is online, the Hardware tab displays 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 fieldbus device 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 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: Application Guide GEH-6761C 21

22 3 HMI Features The ToolboxST application enables you to view and interact with fieldbus process alarms and device alerts through the WorkstationST Alarm Viewer, OPC AE Server, and GSM Server. The ToolboxST and CIMPLICITY applications work together to provide a variety of functions and information to the system and 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 drag-and-drop of other blocks is not prevented, but they will not function. The ToolboxST application only supports the drag-and-drop of assigned fieldbus function blocks, configured to put View 1 on EGD, onto a CIMPLICITY HMI screen. The ToolboxST application populates the clipboard with the proper data to enable the CIMPLICITY smart object to function properly. 22 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

23 Appendix A FOUNDATION Fieldbus Function Block s This appendix contains a list of the FOUNDATION fieldbus function block parameters and their descriptions. Also included is a listing of the blocks and the parameters associated with that block. s The following is a description of each block parameter and its intended use. ACK_OPTION acknowledged. Selection of whether alarms associated with the block is automatically ALARM_HYS Amount the PV must return within the alarm limits before the alarm condition clears. Alarm Hysteresis is expressed as a percent of the PV span. ALARM_SUM The current alert status, unacknowledged states, unreported states, and disabled states of the alarms associated 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 time specified 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 initialize the control loop. BKCAL_OUT The value and status required by an upper block s BKCAL_IN so that the upper block may prevent reset windup 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 provide bumpless 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 of the 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_IN of the block connected to SEL_2 to prevent reset windup. GEH-6761C Application Guide 23

24 BKCAL_SEL_3 Control selector output value and status associated with SEL_3 input which is provided to BKCAL_IN of 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 the block. The cause of the alert is entered in the subcode field. The first alert to become active sets the Active status in the Status attribute. As soon as the Unreported status is cleared by the alert reporting task, another block alert may be reported without clearing the Active status, if the subcode has changed. BLOCK_ERR 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 diplayed. BYPASS The normal control algorithm may be bypassed through this parameter. When bypass is set, the setpoint value (in percent) is directly transferred to the output. To prevent a bump on transfer to/from bypass, the setpoint is automatically initialized 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 block through 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 the transducer 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 not happen when CONFIRM_TIME = 0. CONTROL_OPTS a control block. Options which the user may select to alter the calculations done in CYCLE_SEL CYCLE_TYPE Used to select the block execution method for this resource. 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 the resource. DEV_REV Manufacturer revision number associated with the resource - used by an interface device to locate the DD file for the resource. 24 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

25 DEV_TYPE Manufacturer s model number associated with the resource - used by interface devices to locate the DD file for the resource. DISC_ALM DISC_LIM DISC_PRI DV_HI_ALM DV_HI_LIM DV_HI_PRI The status and time stamp associated with the discrete alarm. State of discrete input which generates an alarm. Priority of the discrete alarm. The status and time stamp associated with the high deviation alarm. The setting of the high deviation alarm limit in engineering units. Priority of the high deviation alarm. DV_LO_ALM DV_LO_LIM DV_LO_PRI The status and time stamp associated with the low deviation alarm. The setting of the low deviation alarm limit in engineering units. 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 a physical 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 of the 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 blocks. Percent of the block processing time that is free to process additional FSTATE_TIME The time in seconds from detection of fault of the output block remote setpoint to the output action of the block output if the condition still exists. GEH-6761C Application Guide 25

26 FSTATE_VAL The preset analog SP value to use when fault occurs. This value is used if the I/O option Fault State to value 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 State to 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 alarm parameters 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 HI_HI_LIM HI_HI_PRI The status for high high alarm and its associated time stamp. The setting for high high alarm in engineering units. Priority of the high high alarm. HI_LIM HI_PRI The setting for high alarm in engineering units. Priority of the high alarm. IO_OPTS processing. Options which the user may select to alter input and output block 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. The format and range of the version number is defined and controlled by the Fieldbus Foundation. Note: The value of this parameter 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 the value is in different units and must be converted linearly (Indirect), or with square root (Ind Sqr Root), using the input range defined by the transducer and the associated output range. LO_ALM LO_LIM The status of the low alarm and its associated time stamp. The setting for the low alarm in engineering units. 26 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

27 LO_LO_ALM LO_LO_LIM LO_LO_PRI The status of the low low alarm and its associated time stamp. The setting of the low low alarm in engineering units. 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 the transducer 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 capable. Time duration of the shortest cycle interval of which the resource is 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-volatile memory. Zero means it is never automatically copied. At the end of NV_CYCLE_TIME, only those parameters which have changed (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 OUT_LO_LIM Limits the maximum output value. 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 decimal point to be used in displaying the OUT parameter and parameters which have the same scaling as OUT. OUT_STATE 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 be calculated 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 be calculated from the READBACK_D value of a DO block. GEH-6761C Application Guide 27

28 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 point to be used in displaying the PV parameter and parameters which have the same scaling as PV. PV_STATE RA_FTIME seconds. to the text describing the states of a discrete PV. Time constant of a single exponential filter for the value to be ratioed, in 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 allow action 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 be taken 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: Restart resource, 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 be taken under limited conditions or mode change. RS_STATE State of the function block application state machine. SEL_1 SEL_2 SEL_3 First input value to the selector. Second input value to the selector. Third input value to the selector. 28 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

29 SEL_TYPE This parameter specifies the type of selector action, from choices of High, Medium, and Low. SET_FSTATE Set. SHED_OPT Allows the Fault State condition to be manually initiated by selecting 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 RCas shall 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 Rout shall 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 is enabled. 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 the ramp rate is set to zero, then the setpoint is used immediately. For control blocks, rate limiting applies only in Auto. For output 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 the ramp rate is set to zero, then the setpoint is used immediately. For control blocks, rate limiting applies only in Auto. For output 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 static parameter attributes, the associated block s static revision parameter is incremented each time a static parameter attribute value is changed. Also, the associated block s static revision parameter may be incremented if a static parameter attribute is written but the value is not changed. GEH-6761C Application Guide 29

30 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 the block. TAG_DESC TEST_RW The user description of the intended application of the block. 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 decimal point, associated with TRK_VAL. TRK_VAL TRK_IN_D. This input is used as the track value when external tracking is enabled by UPDATE_EVT WRITE_ALM This alert is generated by any change to the static data. 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 be updated. 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 point used with the value obtained from the transducer for a specified channel. XD_STATE to the text describing the states of a discrete for the value obtained from the transducer. 30 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

31 Blocks The following is a list of FOUNDATION fieldbus blocks and their associated parameters. Analog Alarm (FF_AAL) 1 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 GEH-6761C Application Guide 31

32 Analog Input (FF_AI) 1 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 32 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

33 Analog Output (FF_AO) 1 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 GEH-6761C Application Guide 33

34 Arithmetic (FF_AR) 1 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 34 GEH-6761C Mark VIe Control FOUNDATION Fieldbus Interface

35 Bias/Gain Station (FF_BG) 1 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) 1 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 GEH-6761C Application Guide 35