Honeywell ST700 - Configuration; Parameter List; Table 11: Flow Transducer Block Parameters

Page 44 FOUNDATION Fieldbus ST 700 Pressure Transmitter User's Guide Revision 2.0
The assumptions for using this equation are:
1. The density of the fluid is close to design, or error in the flow measurement due to
density changes are within acceptable limits.
2. The orifice is designed for service, and transmitter calibration is done for the design
rated flow.
3. The orifice is operated close to the rated flow or in the region where discharge
coefficient is fairly constant, and does not vary with the changes in velocity.
ATTENTION
Note that FTB goes out of service when PRESS_BASIC is OOS, as flow rate
is calculated from Differential Pressure.
Configuration
Configuration of the FTB involves entering values for Flow type, Rated Flow at URV, and
flow units. When flow type is changed, the flow units are set internally to default units for
the corresponding flow type, and rated flow set to NaN (Not a Number). When units are
changed, they are validated against the flow type and ‘Parameter check error’ is raised on
failure. The block supports only unidirectional flow. LRV of Differential Pressure must be
0 and URV a finite positive value for correct operation.
Parameter List
Table 11: Flow Transducer block parameters
Parameter Description
ST_REV The revision level of the static data associated with the function
block.
TAG_DESC The user description of the application of the block.
STRATEGY Used to identify grouping of blocks.
ALERT_KEY The identification number of the plant unit.
MODE The actual, target, permitted, and normal modes of the block.
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 shown.
UPDATE_EVT This alert is generated by any change to the static data.
BLOCK_ALM The BLOCK_ALM is used for all configuration, hardware, and
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.