Supplementary Documentation
Page 28 of 44
IFC090, IFC090 i with FF
IFC090-FF Configuration
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]
5 IFC090-FF Configuration
5.1 Resource
Block
Configuration
This block contains the data associated with the underlying resource, i.e. data that are specific to the hardware.
It describes characteristics of the fieldbus device (e.g. device name, serial number, etc.) and is not included in
the functional tasks of the IFC090-FF. Thus, it consists of contained parameter3 only. As a rule, the configurable
items of the Resource Block are not used to modify a special detail, but the representation and behavior of the
complete device.
5.1.1
Resource Block Mode Handling
Since the Resource Block is characterizing the fieldbus device as a whole, its operation mode also affects the
complete IFC090-FF. To this end, the Resource Block supports the following operation modes
•
Automatic (Auto), and
•
Out of Service (OOS).
In Automatic mode, the complete Resource (i.e. Transducer and Function blocks) is able to operate and perform
their functional tasks. In the Out of Service mode, all other blocks are in Out of Service mode, too, and are not
capable of changing their mode unless the Resource block is set to to Automatic mode.
If a block is in Out of Service mode, this is also indicated by its BLOCK_ERR parameter.
5.1.2 Write
Protection
Normally, all (writable) parameters of all blocks are not protected against accidental write accesses. To avoid
such accidental write accesses you can use the IFC090-FF building software write lock. This write lock can be
controlled by the parameter WRITE_LOCK, which can have the following settings:
•
Not locked
(numerical value: 1), or
•
Locked
(numerical value: 2).
If set to Locked, all writable parameters (with the exception of parameter WRITE_LOCK itself) are write
protected until the write lock is cleared (i.e. set to Not locked).
If the control system should be notified by an alarm, if the write lock is cleared, this can be controlled by the
parameter WRITE_PRI. This parameter expects a numerical value which specifies the behavior of the write lock
clearing alarm parameter WRITE_ALM. Subject to the following settings of WRITE_PRI, WRITE_ALM behaves
as follows:
3
A parameter is called
“contained“
if it not use other blocks output parameters or can not be used by other
blocks input parameters, respectively.
