Supplementary Documentation
Page 13 of 44
IFC090, IFC090 i with FF
IFC090-FF Block Description
IFC090 FF 01/2005
KROHNE Messtechnik GmbH & Co. KG · Ludwig-Krohne-Str. 5
D-47058 Duisburg
Tel.: 0203-301 309
Fax: 0203-301389 · E-mail: [email protected]
Parameter
Access
Description
SHED_ROUT R/W
Time duration for the monitoring-cycle in which a function block in mode Rout has to
answer on control system requests.
NOTE:
Since the IFC090-FF has no function block capable of switching to mode Rout, this
parameter is not supported.
STRATEGY R/W
Parameter used to group a set of blocks. This is done by assigning the same
STRATEGY numerical value to all blocks belonging to one group.
NOTE:
This parameter is neither checked nor used by the function block application! It can be
used by control system to group blocks!
ST_REV R
Static data revision counter. ST_REV will be incremented if a static Resource Block
parameter has changed. By checking this parameter, control systems are able to
realize if a static parameter has changed its value without checking all static
parameters all the time.
TAG_DESC R/W
User description of the intended application of the block. The user is free in setting this
value. The only limitation is the length of 32 characters at maximum. It is not checked
by the application, but has informational character only.
TEST_RW R/W
Read/write test parameter. It is only used during Fieldbus Foundation interoperability
testing and has no meaning for normal operation!
UPDATE_EVT R
Alert generated by a change to static data. The subfields of this parameter give
detailed information about the changed static parameter, time of change and state of
the update event.
WRITE_ALM R
Alarm generated, if the parameter write lock is cleared.
see also:
ACK_OPTION, WRITE_LOCK, WRITE_PRI
WRITE_LOCK R/W
If this parameter is set to ‘Locked’ (2) all writable parameters in all blocks are write
protected, with the exception of WRITE_LOCK itself. Dynamic data will continue to be
updated.
To disable the write protection, set this parameter to ‘Not Locked’ (1).
see also:
ACK_OPTION, WRITE_ALM, WRITE_PRI
WRITE_PRI R/W
Priority of the alarm generated by clearing the WRITE_LOCK:
0
alarm isn't be evaluated
1
no notification to the control system in case of an write protection alarm
2
reserved for block alarms
3-7
write protection is send as user/operator note to the control system,
according to the given priority (3 = low and 7 = high)
8-15
write protection alarm is sent with the appropriate priority
(15 = high and 8 = low).
Table 1: Resource Block parameters
