Configuring the HART Node for a HART Field Device

Configuring the DX99 HART Node for HART
Field Devices
Technical Note
Configuring the DX99 HART Node
This technical note describes how to perform a custom configuration of the DX99 HART FlexPower Node for interfacing with
a HART© communications enabled field device. The DX99 HART FlexPower Node has been tested for compatibility with
HART© Protocol field devices up to revision 7.5 and should provide universal compatibility with any HART© field device it
can power.
All HART variables and field device information are read concurrently. The HART field device is warmed up, read, then shut
down, based on the sample rate and warm-up time of the Node.
Setting a Custom Sample Rate and Warm-Up Time
The DX99 HART FlexPower Node is configured, by default, to sample a HART field device every 15 minutes and to warm-up
the HART field device for 60 seconds before reading HART variables. To optimize the battery life, match the sample rate
and warm-up time to a particular HART field device using the User Configuration Tool (UCT) software.
1. Launch the UCT.
2. After you have established a connection to the Node, select the device config tab along the left of the UCT
window.
3. In the device parameters tab, select the Node number of your device from the drop-down list.
4. Select 1 for your I/O Number, then select Sample Rate from the Parameter drop-down list.
5. Enter your sample rate, in increments of 62.5 milliseconds, in the Value field.
6. Press Send to send the new sample rate value to the Node.
7. Select Warm-up Time from the Parameter drop-down list.
8. Enter the warm-up time In the Value field in increments of 0.5 seconds.
9. The default warm-up time of 60 seconds is equal to 120 increments of 0.5 seconds. Press Send to send the new
warm-up time value to the Node.
Figure 1. User Configuration Tool - Selecting the Sample Rate
The default sample rate of 15 minutes is equal to 14400 increments of 62.5 milliseconds, using the following equation: 15
[minutes] × 60 [seconds per minute] × 16 [increments of 62.5 milliseconds per minute] = 14400.
Table 1: Commonly Used Sample Rates
Sample Rate in Minutes
Value
Sample Rate in Minutes
Value
30
28800
5
4800
25
24000
4
3840
20
19200
3
2880
15
14400
2
1920
10
9600
1
960
8
7680
Original Document
b_4190588 Rev. C
26 May 2016
Configuring the DX99 HART Node for HART Field Devices
Advanced Configuration of HART Field Devices
The DX99 HART FlexPower Node defaults to report a HART field device's primary and secondary variables, primary variable
units code, secondary variable units code, and a discrete sinking input. I/O 1 through 6 of the DX99 HART FlexPower Node
can be set to report any combination of the following information:
•
•
•
•
•
•
•
•
HART primary variable
HART secondary variable
HART tertiary variable
HART quaternary variable
Loop current
Unit codes for any of the four main variables
Communication status/response code
Field device status code
The primary, secondary, tertiary, and quaternary variables and loop current can be reported in their full, raw 32-bit float
format, taking up two I/O registers each. The 32-bit float data can be multiplied or divided by a factor of 10 up to seven
times (10,000,000) and then optionally converted to a signed or unsigned 16-bit integer to fit the data into a single I/O
register. Redefining the 32-bit floating point data reduces precision but allows for all four of the HART variables to be sent
through the SureCross network concurrently.
The engineering unit codes are a single byte code that indicates the unit of measure for each main variable. The DX99
HART FlexPower Node can be set to read back any of the four main HART variable unit codes. The communication status/
response code is another single byte code. If there is a communication error with the HART command sent from the Node
to the field device, the field device returns a communication error code in the communication status byte field. If the
communication is successful, the field device returns a response code in the byte field. Similarly, the device status code is
a single byte code indicating the current operating status of the HART Field Device.
As all these unit and status codes are each only one byte in length, they can be set as the high byte or low byte in any
input register to allow any combination of two unit or status byte codes to be sent back through the SureCross network in
a single input register.
Refer to the HART Protocol Technical Specifications manual for unit and status byte code details.
Example Configuration — Advanced HART Field Device Interface
This example configuration creates a custom HART Field Device interface configuration. The configuration of the Node's
registers is:
• I/O 1: Primary Variable - Level Percentage 0 to 100% (Upper word of 32-bit float)
• I/O 2: Primary Variable - Level Percentage 0 to 100% (Lower word of 32-bit float)
• I/O 3: Secondary Variable - Level Distance in Meters x 1000 (16-bit unsigned integer)
• I/O 4: Tertiary Variable - Distance to Interface x 1000 (16-bit unsigned integer)
• I/O 5: Quaternary Variable - Temperature in °C x 100 (16-bit signed integer)
• I/O 6: Communication Status/Response Code (High byte) and Device Status (Low byte)
Primary and Secondary Variables
1. Launch the User Configuration Tool software (UCT) and connect to the Node.
2. Select the device config tab.
3. I/O 1 and 2 are already set up correctly for reading the primary variable by default, we begin with I/O 3. In the
device parameters tab, select the Node number of your device from the drop-down list.
4. Select 3 for your I/O Number, then select Default Value from the Parameter drop-down list.
The default value parameter defines what HART data is sent back through the SureCross network and how the data is
manipulated before transmission. The default value is a 16-bit parameter value. The lower byte determines the requested
HART data as follows (all Codes are a single byte in length and can be set as the lower or upper byte):
2
Byte Value (hexadecimal)
HART Data
0x01
Primary Variable
0x02
Secondary Variable
0x03
Tertiary Variable
0x04
Quaternary Variable
0x05
Loop Current
0x10
Command Status/Response Code
www.bannerengineering.com - Tel: +1-763-544-3164
P/N b_4190588 Rev. C
Configuring the DX99 HART Node for HART Field Devices
Byte Value (hexadecimal)
HART Data
0x11
Field Device Status Code
0x21
Primary Variable Units Code
0x22
Secondary Variable Units Code
0x23
Tertiary Variable Units Code
0x24
Quaternary Variable Units Code
The upper byte determines if and how the HART data is manipulated, per the bitmask shown. When HART data is left in its
unmanipulated float form, this value must stay at its default value of zero.
Bit Position
7
6
5
4
3
2
1
0
Default 0x00
0
0
0
0
0
0
0
0
Not used
Float Enable
0 - Non-float data
1 - Float data
Register Size
0 - 16 bit
1 - 32 bit
Move Decimal Point
Raise 10 by this value (in decimal)
Decimal Point Move Direction
0 - Move right (multiply)
1 - Move left (divide)
Register Sign
0 - Unsigned
1 - Signed
Figure 2. HART Primary and Secondary Variable Bitmask
The Default Value parameter for I/O 3 is 2 (or 0x0002 in hexadecimal). For our example, we want to set I/O 3 to read the
HART Secondary Variable, the level distance in meters, multiplied by 1000 as a 16-bit unsigned integer.
If the 32-bit float value read 12.3456789 meters, the value returned through the SureCross network would be 12346 with
rounding. To set the Default Value parameter accordingly, the lower byte stays at 2 (or 0x02) per HART Data table,
because the Secondary Variable is still the requested data. The upper byte will be set to 3 (or 0x03). The bit mask would
be: 00000011. This value moves the decimal point three places to the right.
Combining the upper and lower bytes gives 770 (or 0x0302). In the Value field of the UCT, enter
Hexadecimal is selected) and press Send.
P/N b_4190588 Rev. C
www.bannerengineering.com - Tel: +1-763-544-3164
770 (or 302 if
3
Configuring the DX99 HART Node for HART Field Devices
After the HART secondary variable is redefined as a 16-bit unsigned integer from a 32-bit float, change the Report Type
and Units parameters accordingly. To finish configuring the secondary variable:
1.
2.
3.
4.
5.
6.
Select Report Type from Parameter drop-down list.
Enter a value of 1.
Click Send.
Select Units from the Parameter drop-down list.
Enter a value of 11.
Click Send.
Tertiary Variable
Set up the HART tertiary variable to be transmitted through the SureCross network on I/O 4 as a 16-bit unsigned integer
multiplied by a factor of 1000. By default, I/O 4 is disabled as it is the lower 16 bits of the 32-bit float value controlled by
I/O 3. To configure I/O 4, follow these steps:
1. In the device config > device parameters tab, select I/O Number 4 from the drop-down list.
2. Select each of the following parameters from the Parameter drop-down list, enter the applicable number into the
Value field and click Send after each change to send the new parameters to the Node.
Parameter
Value
Meaning
Enable Flag
1
On
Default Value
771 (or 0x0303)
The Default Value parameter is set to 771 (0x0303 if Hexadecimal is selected). The lower
byte of the default value is 0x03 for the tertiary variable. The upper byte is 0x03, which
moves the decimal point right three spaces (see Figure 2 on page 3).
I/O Type
45 (or 0x002D)
HART Input
Report Rate
960 (or 0x03C0)
60 seconds
Report Type
1
16-bit
Units
11 (or 0x000B)
0 through 65535
Quaternary Variable
The HART quaternary variable (temperature in °C) is configured to be transmitted through the SureCross network on I/O 5
as a 16-bit signed integer, multiplied by 100. Therefore, if the 32-bit float value was –12.3456789 [°C], the value returned
through the SureCross network would be –1235 with rounding.
1. In the device config > device parameters tab, select I/O Number 5 from the drop-down list.
2. Select Default Value from the Parameter drop-down list.
3. The default value parameter for I/O 5 is 8482 (0x2122 in hex), for retrieving the HART primary and secondary
variables unit codes. To set the default value parameter for our example, set the lower byte to 4 (or 0x04) and the
upper byte to 18 (or 0x12). The bit mask would be: 00010010 to move the decimal point two places to the right
and set the value to signed. Combining the upper and lower default value bytes gives 4612 (or 0x1204). In the
Value field of the UCT, enter 4612 (or 1204 if Hexadecimal is selected).
4. Click Send.
Communication Status/Response Code and Device Status
The HART Communication Status/Response Code and Field Device Status Code is configured to transmit through the
SureCross network on I/O 6. Each code is only a single byte in length, so they are combined and sent through the network
as a single 16-bit value. The Communication Status/Response Code as the high byte and Device Status Code as the low
byte.
By default, I/O 6 is a discrete sinking input, so it will need to be configured as a HART input as well as setting the correct
default value parameter.
1. In the device config > device parameters tab, select I/O 6 from the drop-down list.
2. For each of the following parameters from the Parameter drop-down list, enter the applicable number into the
Value field, and click Send to send the changes to the Node.
4
Parameter
Value
Meaning
Default Value
4113 (or 0x1011)
The default value parameter is set to 4113 (0x1011 in hex), where the upper byte
0x10 is for the Communication Status/Response Code and lower byte 0x11 is for the
Device Status Code.
I/O Type
45 (or 0x002D)
HART Input
www.bannerengineering.com - Tel: +1-763-544-3164
P/N b_4190588 Rev. C
Configuring the DX99 HART Node for HART Field Devices
Parameter
Value
Meaning
Report Rate
960 (or 0x03C0)
60 seconds
Report Type
1
16-bit
Sample Rate
0
Disabled (driven by I/O 1)
Units
11 (or 0x000B)
0 through 65535
The DX99 HART FlexPower Node has now been configured for a custom interface for a HART-enabled field device. For
configuration to take effect, reset the device using the User Configuration Tool's Device Config > Device Restore screen
and selecting Reset Device, or by disconnecting the device from the ribbon cable and reconnecting.
Battery Life
The following battery life curves represent the approximate battery life of the DX99 HART 13 V Node (DX99...D6) and the
DX99 HART 19 V node (DX99..D7) when used with specific HART field devices.
DX99 HART 13 V Node Battery Life
90
80
VegaFlex 81/Siemens Sitrans LG250 (30 s warm-up time)
Battery Life (months)
70
EH Levelflex (30 s warm-up time)
VegaPuls 62 (37 s warm-up time)
60
50
40
30
20
10
0
120
90
60
45
30
25
20
15
10
8
5
4
3
2
1
Sample Rate (minutes)
P/N b_4190588 Rev. C
www.bannerengineering.com - Tel: +1-763-544-3164
5
Configuring the DX99 HART Node for HART Field Devices
DX99 HART 13 V Node Battery Life
80
70
VegaFlex 81/Siemens Sitrans LG250 (60 s warm-up time)
EH Levelflex (60 s warm-up time)
VegaPuls 62 (60 s warm-up time)
Battery Life (months)
60
50
40
30
20
10
0
120
90
60
45
30
25
20
15
10
8
5
4
3
2
1
Sample Rate (minutes)
6
www.bannerengineering.com - Tel: +1-763-544-3164
P/N b_4190588 Rev. C
Configuring the DX99 HART Node for HART Field Devices
DX99 HART 19 V Node Battery Life
80
VegaFlex 81/Siemens Sitrans LG250 (30 s warm-up time)
70
EH Levelflex (30 s warm-up time)
Siemens LR250 (45 s warm-up time)
Battery Life (months)
60
VegaPuls 62 (37 s warm-up time)
50
40
30
20
10
0
120
90
60
45
30
25
20
15
10
8
5
4
3
2
1
Sample Rate (minutes)
P/N b_4190588 Rev. C
www.bannerengineering.com - Tel: +1-763-544-3164
7
Configuring the DX99 HART Node for HART Field Devices
DX99 HART 19 V Node Battery Life
70
60
VegaFlex 81/Siemens Sitrans LG250 (60 s warm-up time)
EH Levelflex (60 s warm-up time)
VegaPuls 62 (60 s warm-up time)
Battery Life (months)
50
40
30
20
10
0
120
90
60
45
30
25
20
15
10
8
5
Sample Rate (minutes)
www.bannerengineering.com - Tel: +1-763-544-3164
4
3
2
1