108
2600T SERIES |  PRESSURE TRANSMITTERS |  OI/266/FF-EN REV. E
Block Mapping
Idx Parameter Description / Range / Selections / Note
 BLOCK_OBJ
In the Block Object data structure, there are different items describing the block characteristics. Execution period, 
Number of parameters in the block, the DD Revision, Profile Revision, View Objects characteristics and so on  
 ST_REV
The revision level of the Static data associated with the Function Block. The revision level is incremented each time a static 
parameter value (S – under Storage) in the block is changed. 
 TAG_DESC The user description of the intended application of the block
 STRATEGY The strategy field can be used to identify grouping of blocks. This data is not checked or processed by the block.
 ALERT_KEY The identification number of the plant unit. This information may be used in the host for sorting alarms, etc.
 MODE_BLK
TARGET AUTO / MAN / OOS The selectable modes by the operator.
ACTUAL The mode the block is currently in. 
PERMITTED AUTO / MAN / OOS  Allowed modes that the target may take on
NORMAL AUTO The common mode for the Actual.
 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. 
 
as a result of the block execution, 
Writeable only if MODE_BLK.ACTUAL = MAN
 
as a result of the block execution, 
 X_RANGE
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 variables corresponding to the x-axis for display. It has no effect on the block
 Y_RANGE
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 variables corresponding to the y-axis for display. It has no effect on the block.
 GRANT_DENY
  
  
 
No Swap
Swap
 CURVE_X 
 CURVE_Y 
 UPDATE_ EVT This alert is generated by any change to the static data
 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 will set the Active Status in the status parameter. 
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.