contains the necessary information for configuration of the fieldbus temperature transmitter
T53 via a host system with application software for Foundation Fieldbus™ (for PROFIBUS
HOST systems please refer to the “Configuration Manual for PROFIBUS”). The autoswitch
function of the modules ensures automatic switch to the connected protocol.
The Fieldbus Software
has been developped by WIKA according to the specifications of the Fieldbus Foundation
and the PROFIBUS Nutzerorganisation.
TM
The files for Foundation
Fieldbus are:
xxyy.ffo - Device Description binary file
xxyy.sym - Device Description symbol file
xxyyzz.cff - Capability file
xx, yy and zz refer to the version numbers of the files.
These files can be downloaded from our homepage www.wika.de.
Please follow the instructions for the application software in question when installing the
files.
Parameter lists abbreviations
In the Store column:
SRC = Static Revision Counter; N = No; D = Dynamic;
Cst = Constant. The parameter doesn’t change in a device
In the RO / R/W column:
RO = Read Only; R /W = Read Write; * = Mixed of RO and R/W; ** = Don’t care
1.0 The Resource Block, Fieldbus Foundation
1.1 Introduction
The resource block is used to define a hardware specific characteristics of the function block
applications. It provides WIKA manufacturer’s name, device name, DD and block status and
hardware details. It also indicates how much resource (memory and CPU) is available and
controls the overall device.
1.2 Description
This block contains data that is specific to the hardware that is associated with the resource.
All data is modelled within a controlled space, so there are no outside inputs into this block
required.
This parameter “set” is intended to be the minimum required for the Function Block Applica
tion associated with the resource in which it resides. Some parameters that could be in the
set, like calibration data and ambient temperature, are more part of their respective trans
ducer blocks. The “mode” is used to control major states of the resource. O/S mode stops
all function block execution. The actual mode of the function blocks will be changed to O/S
(out of service), but the target mode will not be changed. Auto mode allows normal operation
of the resource. IMan shows that the resource is initializing or receiving a software down
load. Parameters MANUFAC_ID, DEV_TYPE, DEV_REV, DD_REV, and DD_RESOURCE are
required to identify and locate the DD so that Device Description Hosting Services can se
lect the correct DD for use with the resource. The parameter HARD_TYPES is a read only bit
string that indicates the types of hardware that are available to this resource. If an I/O block
is configured that requires a type of hardware that is not available, the result will be a block
alarm for a configuration error. The RS_STATE parameter contains the operational state of
the Function Block Application for the resource containing this resource block.
-
-
-
-
1.3 RESTART parameter
The RESTART parameter allows degrees of initialization of the resource. They are:
1 - Run: it is the passive state of the parameter
2 - Restart resource: it is intended to clear up problems for example the memory manage
ment resource.
3 - Restart with defaults: it is intended to wipe configuration memory, it works like a factory
initialization.
4 - Restart processor: it provides a way to hit the reset button on the processor associated
with the resource This parameter does not appear in a view because it returns to 1 shortly
after being written.
1.4 Non-volatile parameters
All non-volatile parameters are saved in EEPROM and therefore used if the device is restart
ed.
1.5 Timeout for remote cascade modes
SHED_RCAS and SHED_ROUT set the time limit for loss of communication from a remote
device. These constants are used by all function blocks that support a remote cascade
mode. The effect of a timeout is described in Mode Calculation. Shedding from RCAS/ROUT
shall not happen when SHED_RCAS or SHED_ROUT is set to zero.
1.6 Alert Notification
The MAX_NOTIFY parameter value is the maximum number of alert reports that this resource
can have sent without getting a confirmation, corresponding to the amount of buffer space
available for alert messages. A user can set the number lower than that, to control alert
flooding, by adjusting the LIM_NOTIFY parameter value. If LIM_NOTIFY is set to zero, then
no alerts are reported. The CONFIRM_TIME parameter is the time for the resource to wait for
confirmation of receipt of a report before trying again. If the CONFIRM_TIME = 0 the device
shall not retry.
-
-
5
6
1.7 FEATURES / FEATURE_SEL parameters
The bit strings FEATURES and FEATURE_SEL determine optional behaviour of the resource.
The first defines the available features, and is read only. The second is used to turn on an
available feature by configuration. If a bit is set in FEATURE_SEL that is not set in FEA
TURES, the result will be a block alarm for a configuration error. The device supports the
following features: Reports supported, Fault State supported, Soft Write lock supported.
1.8 Fault state for the whole resource
If the user sets the SET_FSTATE parameter, the FAULT_STATE parameter will indicate active
and it will cause all output function blocks in the resource to go immediately to the condition
chosen by the fault state Type I/O option. It may be cleared by setting the CLR_FSTATE pa
rameter. The set and clear parameters do not appear in a view because they are momentary.
1.9 Write lock by software
The WRITE_LOCK parameter, if set, will prevent any external change to the static or non
volatile data base in the Function Block Application of the resource. Block connections and
calculation results will proceed normally, but the configuration will be locked. It is set and
cleared by writing to the WRITE_LOCK parameter. Clearing WRITE_LOCK will generate the
discrete alert WRITE_ALM, at the WRITE_PRI priority. Setting WRITE_LOCK will clear the
alert, if it exists. Before setting WRITE_LOCK parameter to Locked, it is necessary to select
the “Soft Write lock supported” option in FEATURE_SEL.
1.10 Features being implemented
The parameter CYCLE_TYPE is a bit string that defines the types of cycles that this resource
can do. CYCLE_SEL allows the configurator to choose one of them. If CYCLE_SEL contains
more than one bit, or the bit set is not set in CYCLE_TYPE, the result will be a block alarm
for a configuration error. MIN_CYCLE_T is the manufacturer specified minimum time to ex
ecute a cycle. It puts a lower limit on the scheduling of the resource.
-
-
-
MEMORY_SIZE declares the size of the resource for configuration of function blocks, in kilo
bytes. The parameter FREE_SPACE shows the percentage of configuration memory that is
still available. FREE_TIME shows the approximate percentage of time that the resource has
left for processing new function blocks, should they be configured.
1.11 BLOCK_ERR
The BLOCK_ERR of the resource block will reflect the following causes:
Device Fault State Set – When FAULT_STATE is active.
Simulate Active – When the Simulate jumper is ON.
Out of Service – When the block is in O/S mode.
1.12 Supported Modes
O/S, IMAN and AUTO
-
Parameter
ST_REV
TAG_DESC
STRATEGY
ALERT_KEY
1.13 Resource Block Parameter List, Fieldbus Foundation
Rel.
DescriptionType Store
Index
Is incremented each time that there is a change in a static
1
parameter in the physical block.
Tag name of the block. This parameter must be unique in the
2
configuration.
This can be used to group a Function Block. It is a user sup
3
plied parameter for identification purpose.
4Alert keys
Un-
signed
SRC2RO0
16
-
OCTET_
STRING
signed
SRC32R/W»«
Un-
SRC2R/W0
16
Un-
signed 8SRC1R/W0
Size
byte
RO /
Min. Max. Default
R/W
MODE_BLK
BLOCK_ERR
RS_STATE
TEST_RW
DD_RESOURCE
MANUFAC_ID
DEV_TYPE
DEV_REV
DD_REV
GRANT_DENY
HARD_TYPES
RESTART
FEATURES
FEATURE_SEL
CYCLE_TYPE
CYCLE_SEL
MIN_CYLCE_T
MEMORY_SIZE
NV_CYCLE_T
FREE_SPACE
FREE_TIME
SHED_RCAS
SHED_ROUT
5Block running modeDS-69Mix4*
6Block errors
BIT_
STRING
D2RO0
1,1,
17,16
Un-
7State of the function block application state machine
signed 8D1RO0
8Read/write test parameter used only for conformance testingDS-85D112 R/W0..0
String identifying the tag of the resource which contains the
9
Device Description for this resource.
Enumeration; controlled by FF
10
Manufacturer identification number - used by an interface
device to locate the DD file for the resource.
Manufacturer’s model number associated with the resource -
11
used by interface devices to locate the DD file for the resource.
Manufacturer revision number associated with the resource
12
- used by an interface device to locate the DD file for the
resource.
Revision of the DD associated with the resource - used by an
13
interface device to locate the DD file for the resource.
VISIBLE_
STRING
Un-
signed
32
Un-
signed
16
Un-
signed
8
Un-
signed
8
SRC32RO» »
SRC4RO
SRC2RO
SRC1RO
SRC1RO
WIKA
0x00ec
0x03
0x01
Access Permissions. Options for controlling access of host
14
computer and local control panels to operating, tuning and
DS-70 SRC2R/W0
alarm parameters of the block.
15The types of hardware available as channel numbers.
BIT_
STRING
SRC2RO0
1: Run,
2: Restart resource,
3: Restart with defaults,
16
4: Restart processor
Allows a manual restart to be initiated. Several degrees of
Un-
signed
8
D1R/W1
restart are possible.
-
-
BIT_
STRING
BIT_
STRING
BIT_
STRING
BIT_
STRING
Un-
signed
32
Un-
signed
16
Un-
signed
32
Floating
Point
Floating
Point
Un-
signed
32
Un-
signed
32
SRC2RO0
SRC2RW0
SRC2RO0xC000
SRC2**0xC000
SRC4RO0
SRC2RO0
SRC4RO0
D4RO0.0
D4RO0.0
SRC4R/W640000
SRC4R/W640000
17Used to show supported resource block options.
18Used to select resource block options.
Identifies the block execution methods available for this
19
resource
20Used to select the block execution method for this resource.
Time duration of the shortest cycle interval of which the
21
resource is capable.
Available configuration memory in the empty resource. To be
22
checked before attempting a download.
Interval between writing copies of NV parameters to non-vola
23
tile memory. Zero means never.
Percent of memory available for further configuration. Zero in a
24
preconfigured resource.
Percent of the block processing time that is free to process
25
additional blocks.
Time duration at which to give up on computer writes to func
26
tion block RCas locations.
ms time duration at which to give up on computer writes to
27
function block ROut locations.
7
8
Parameter
FAULT_STATE
SET_FSTATE
CLR_FSTATE
MAX_NOTIFY
Rel.
DescriptionType Store
Index
Active E D Condition set by loss of communication to an out
put block, failure promoted to an output block or a physical
28
contact. When Fault State condition is set, Then output func
-
-
tion blocks will perform their FSAFE actions.
Allows the fault state condition to be manually initiated by
29
selecting Set.
Writing a Clear to this parameter will clear the device fault state
30
if the field condition, if any, has cleared.
31Maximum number of unconfirmed notify messages possible.
Size
RO /
byte
Min. Max. Default
R/W
Un-
signed
N1RO1
8
Un-
signed
D1R/W1
8
Un-
signed
D1R/W1
8
Un-
signed 8SRC1RO8
LIM_NOTIFY
CONFIRM_TIME
WRITE_LOCK
UPDATE_EVT
BLOCK_ALM
ALARM_SUM
ACK_OPTION
WRITE_PRI
Maximum number of unconfirmed alert notify messages
32
allowed.
Un-
signed
8
SRC1R/W8
Un-
33Ms The minimum time between retries of alert reports.
If set, no writes from anywhere are allowed, except to clear
34
WRITE_LOCK. Block inputs will continue to be updated.
signed 32SRC4R/W640000
Un-
signed
SRC1R/W1
8
35This alert is generated by any change to the static dataDS-73D14RO
The block alarm is used for all configuration, hardware, con
nection failure or system problems in the block. The cause
of the alert is entered in the sub code field. The first alert to
become active will set the Active status in the Status attribute.
36
As soon as the Unreported status is cleared by the alert report
-
DS-72
D13R/W
ing task, another block alert may be reported without clearing
the Active status, if the sub code
has changed.
The current alert status, unacknowledged states, unreported
states, and disabled states of the alarms associated with the
37
function
DS-74Mix8R/W0,0,0,0
block.
0: Auto ACK Disable
1: Auto ACK Enable
38
Selection of whether alarms associated with the block will be
BIT_
STRING
SRC2R/W0
automatically acknowledged.
Un-
39Priority of the alarm generated by clearing the write lock.
signed 8SRC1R/W0
0,0,0,
0,0,9,0
0,0,0,
0,0,0,
8,0,0
WRITE_ALM
ITK_VER_NR
40This alert is generated if the write lock parameter is cleared.DS-72D13R/W
ITK Version Number
41
This parameter informs which ITK version is the device (for certified devices only).
Un-
signed
16
SRC2RO4
0,0,0,
0,0,0,
10,0,0
2.0 The Transducer Block
2.1 The Transducer Block
contains all of the manufacturer-specific parameters that define how the T53 Transmitter
functions. Selections such as setting of input type, engineering units, defining the dual func
tionality when using the dual input, and so forth, are performed in the Transducer Block.
The transducer block in T53 allows the user to select a large number of sophisticated func
tions. Therefore, the configuration of the transmitter must be carried out with the greatest
possible care.
2.2 The data of the Transducer Block Parameter List are grouped as follows:
2.8 AI_TRANSDUCER Block
2.8.1 Sensor characterising parameters
2.8.2 RTD / resistor specific parameters
2.8.3 Thermocouple specific parameters
2.8.4 Output conditioning parameters
2.8.5 Output parameters
2.8.6 Diagnostic parameters
2.8.7 Sensor error detection parameters
2.8.9 Sensor calibration parameters
2.9 PR_CUST_LIN Block
2.9.2 Linear Interpolation Linearisation
2.9.4 Custom Polynomial linearisation
2.10 PR_CUST_PRIV Block
2.10.1 PR_CUST_PRIV Block
All product-specific parameters are set off in grey background in the TB Parameter List. In
order to configure these parameters, the files mentioned in the introduction must be avail
able to the application software.
-
-
-
2.3 Default configuration
WIKA delivers the transmitters with at default configuration which will suit the customer’s
demand in many cases. The configuration task has thus been reduced considerably.
The individual default configurations are shown in the TB Parameter List, but in short the
default configuration is as follows:
Pt100 acc. to the standard EN 60 751 (2.8.1 LIN_TYPE, value 102)
°C (2.8.1 PRIMARY_VALUE_UNIT, value 1001)
3-wire connection (2.8.2 SENSOR_CONNECTION, value 1)
Only sensor 1 (2.8.4 SENSOR_MEAS_TYPE, value 220)
No sensor error detection (2.8.7 SENSOR_WIRE_CHECK_1, value 3)
2.4 Your application set up.
In the Transducer block all parameters marked R / W can be adapted to suit any measurement in temperature, ohm or mV. The way of presenting the file data mentioned in the
introduction varies greatly from one piece of application software to the other. Some pro
grams show drop down menus in which the parameters must be selected via text lines, while
other programs require the user to type in the numerical value of the parameter selection.
-
9
10
2.5 AI_Transducer Block Configuration Flowchart
Configure T53
Transducer block
Temperature
measurement?
Set
PRIMARY_VALUE_UNIT
to F,R,C or K
RTD?
Thermo-couple?
Set LIN_TYPE to RTD
type (Pt100 etc.)
4-wire?
Set
SENSOR_CONNECTION
to 2-,3- or 4-wire.
Enter wire resistance in
Ohms for both wires to
COMP_WIRE1
2-wire?
Enter wire resistance in
Ohms for both wires to
COMP_WIRE2
YES
Enter setup for sensor 2:
YES
Set LIN_TYPE to TC
type (TC K etc.)
Set RJ_TYPE (internal,
external etc.)
Set LIN_TYPE_2 to RTD
type (Pt100 etc.)
Set
SENSOR_MEAS_TYPE
to single sensor type
Dual sensor?
Enter setup for sensor 2:
Set LIN_TYPE_2 to TC type
(TC K etc.)
Enter RJ temperature to
EXTERNAL_RJ_VALUE
RJ_TYPE
external?
YES
YES
RJ_TYPE
ext. 2.wire?
Enter wire resistance in
Ohms for both wires to
COMP_WIRE_RJ
YES
YES
YES
2c
Set
SENSOR_MEAS_TYPE
to single sensor type
2b
2a
Set SENSOR_MEAS_TYPE
to dual sensor type
Set SENSOR_MEAS_TYPE
to dual sensor type
YES
Dual sensor?
YES
2c
RTD+Thermo-
couple?
2b
Set LIN_TYPE to TC
type (TC K etc.)
Set RJ_TYPE
(internal, external etc.)
Set
SENSOR_MEAS_TYPE
to dual sensor type
Set LIN_TYPE_2 to
RTD type (Pt100 etc.)
Enter RJ temperature to
EXTERNAL_RJ_VALUE
RJ_TYPE
external?
YES
YES
2a
Error! (try again)
Resistance?
Set
PRIMARY_VALUE_UNIT
to Ohm or kOhm
Set
SENSOR_CONNECTION
to 2-,3- or 4-wire.
Dual sensor?
Enter wire resistance in
Ohms for both wires to
COMP_WIRE1
2-wire?
YES
Enter setup for sensor 2:
YES
Set LIN_TYPE_2 to
”no linearisation” or
”linearisation table”
Set
SENSOR_MEAS_TYPE
to single sensor type
Set LIN_TYPE to
”no linearisation” or
”linearisation table”
Set SENSOR_MEAS_TYPE
to dual sensor type
Enter wire resistance in
Ohms for both wires to
COMP_WIRE2
Millivolts?
Set
PRIMARY_VALUE_UNIT
to V,mV or µV
Set LIN_TYPE to
”no linearisation” or
”linearisation table”
Dual sensor?
Set LIN_TYPE_2 to
”no linearisation” or
”linearisation table”
Set
SENSOR_MEAS_TYPE
to single sensor type
Set SENSOR_MEAS_TYPE
to dual sensor type
3b
3a
Enter setup for sensor 2:
YES
YES
YES
4-wire?
YES
11
12
3b3a
Potentiometer?
Set
PRIMARY_VALUE_UNIT
to ”%”
Set
SENSOR_CONNECTION
to 3- or 4-wire.
Enter wire resistance in
Ohms for 2 wires to
COMP_WIRE1
3-wire?
YES
Enter setup
for sensor 2:
YES
Set LIN_TYPE_2 to
”no linearisation” or
”linearisation table”
Set
SENSOR_MEAS_TYPE
to single sensor type
Set LIN_TYPE to
”no linearisation” or
”linearisation table”
Set SENSOR_MEAS_TYPE
to dual sensor type
Enter wire resistance in
Ohms for 2 wires to
COMP_WIRE2
Error! (try again)
Finished.
Transducer block
is configured!
Enter Custom RTD
polynomial values
Linearisation
table?
Custom RTD?
Enter linearisation
table values
YES
YES
Enter Custom TC
polynomial values
Custom TC?
YES
Dual sensor?
YES
Loading...
+ 25 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.