Manual Radar Smartradar Flexline Ultima Revisão
Manual Radar Smartradar Flexline Ultima Revisão
SmartRadar FlexLine
Contact Information:
Honeywell Enraf
Delftechpark 39, 2628 XJ Delft
PO Box 812, 2600 AV Delft
The Netherlands
CHAPTER 1 GENERAL
1.3 Trademarks
HART® is a registered trademark of the HART Communication
Foundation.
1.4 Contact
Head Office - Delft, The Netherlands
Honeywell Enraf
Delftechpark 39, 2628 XJ Delft
PO Box 812, 2600 AV Delft
The Netherlands
E-mail: enraf.helpdesk@honeywell.com
Website: http://www.honeywell.com/ps
CHAPTER 2 SAFETY
2.1 General
The SmartRadar FlexLine is a radar-based level gauge which is used in
inventory measurement systems. It can also be used to interface with
other systems and sensors such as pressure, density, or temperature
sensors.
For the correct and safe servicing of this product, it is essential that all
personnel follow the generally accepted safety procedures in addition to
the safety precautions specified in this manual.
2.2.1 Warnings
The following warning symbol is used in this manual to urge attention in
order to prevent personal injuries or dangerous situations, further
described in this manual.
Symbol Description Remark
General warning Will always be explained by text.
2.2.2 Cautions
The following caution mark is used in this manual to urge attention in
order to prevent damages to the equipment further described in this
manual.
Symbol Description
General caution sign
2.3.4 Users
The mechanical and electrical installation must be carried out only by
trained personnel with knowledge of the requirements for installation of
explosion-proof equipment in hazardous areas.
The entire installation procedure must be carried out in accordance with
national, local, and company regulations.
The entire electrical installation shall be carried out in accordance with
the national requirements for electrical equipment to be installed in
hazardous areas.
2.4 Liability
The information in this installation guide is the copyright property of
Enraf B.V., Netherlands. Enraf B.V. disclaims any responsibility for
personal injury or damage to equipment caused by:
Deviation from any of the prescribed procedures,
Execution of activities that are not prescribed,
Neglect of the safety regulations for handling tools and use of elec-
tricity.
The contents, descriptions and specifications in this Service Manual are
subject to change without notice. Enraf B.V. accepts no responsibility for
any errors that may appear in this Service Manual.
2.5 Labels
FIGURE 2-1 Identification label with Safety note on the SmartRadar FlexLine
2.7.1 General
WARNING! Treat the flange surface of the cover and the housing
with care.
Keep the flange surface free of dirt.
The O-ring must be present and undamaged.
2.7.1.3 Tools
FCC information:
This device complies with Part 15 of the FCC Rules. Operation is
subject to the following two conditions:
1. This device may not cause harmful interference, and 2. This device
must accept any interference received, including interference that
may cause ndesired operation.
Lantronix Lantronix
Mains
Integrated Supply
SmartView
wireless gauge
N-
connection
CA
Stand-alone HCI-1WL
SmartView
RS-232/485 FII-SMV
RADAR ANTENNA
TII-XR
level measurement
RS-232/485 FII-DO
FCI-HT
Portable FII-VT
SmartView
PRESSURE
TRANSMITTERS
HIMS or
762 VITO vapour pressure
INTERFACE measurement
temperature and/or and/or
2 or 4
water bottom external water probe
Alarm relays
measurement (HART-bus)
ESF07-0026
FIGURE 3-1 SmartRadar FlexLine system architecture overview for R120
Lantronix Lantronix
Mains
Integrated Supply
SmartView
wireless gauge
N-
connection
CA
HCI-1WL
Stand-alone
SmartView
RS-232/485 FII-SMV
RADAR ANTENNA
TII-XR
level measurement
RS-232/485 FII-DO
FCI-HT
Portable FII-VT
SmartView
PRESSURE
TRANSMITTERS
HIMS or
762 VITO vapour pressure
INTERFACE measurement
temperature and/or and/or
2 or 4
water bottom external water probe
Alarm relays
measurement (HART-bus)
prefix - suffix
XXX-YYY
specific name or function
function LEDs
NOVRAM
temperature sensor
jumpers
microcontroller
with program memory
power supply
Jumpers:
With the jumpers, specific hardware settings can be made:
Jumper
Function
Number
1 All warning and monitoring-related commissioning entitiesa are
protected and cannot be changed
2 The password is protected from being read
3 All commissioning entities are protected and cannot be changed
4 Board-specific jumper
5 Board-specific jumper
Health LED
The Health LED (= LE1, the blue circle) indicates the general health
status of the FlexConn module.
Health Status Flashing Pattern
Good
Uncertain
Bad
2 function LEDs
These LEDS indicate module-specific activities, such as for instance
data being transmitted or received.
3 voltage monitors
The output of these monitors, being voltage levels from three different
FlexConn PCB locations, are used for diagnostics purposes.
See FIGURE 3-4.
ESF07-0023
FIGURE 3-4 Locations of the 3 voltage monitors
1 temperature sensor
For the operational PCB, this sensor acts as an input for environmental-
temperature diagnostics. The PCB’s environmental temperature is used
as a measure for the temperature inside the SmartRadar FlexLine.
3.3 Entities
Information exchange between the various FlexConn modules takes
place by means of the entities.
An entity represents a unique information association in the FlexConn
architecture. This information may consist of measuring data, status
data, commissioning parameters, diagnostics data, or commands.
In addition to the information exchange between FlexConn modules,
entities are used for data presentation on the SmartView display, and for
the communication between the Engauge service tool and the
SmartRadar FlexLine.
The entities are represented by a textual description, for example,
“Reset”, “Tank bottom”, “Health”, or “Baudrate”.
The entities structure is related to the following:
General status information
Generic FlexConn part
Function-specific FlexConn part
The “Health” entity reflects the condition of the entire module, each
single module function, and the calculated or measured value of a
sensor function.
The “Health” entity structure is defined by following items:
1. status
2. status category
3. status code
The status field gives high-level information:
good
uncertain
bad
The following table provides information about the status category that
is, the general reason why the status is good, uncertain, or bad.
The following tables provides information about the status code and the
specific reason why the status is good, uncertain, or bad. This
information is presented as an information number coupled with a
textual description of this specific situation.
hw fail
cal fail
sw fail
un-init
killed
last
actual manual stored instrument environment
valid
001 056 077 104 632 328 207 782 065 478 199 389 011 072 ........................................................
The “Commissioned” entity informs the end user if the most important
commissioning entities of the concerned FlexConn module and its
implemented functions are set correctly.
True = the most important entities are set correctly
False = the most important entities are not set correctly
A 1 0 0 0 0
internal preliminary
bug fixes
minor functionality
warning + measuring data related part
main functionality
hardware modifications
3.4.1 General
The SmartView is used to set and control most of the FlexConn module
settings.
< >
<
<
MAIN
MENU SELECT
ESF07-0024
FIGURE 3-5 An impression of the SmartView
H C I
FII-DO G N
FII-DO:>
board H C I
Relay 1 G N
Relay 2 G Y
Relay 3 U Y nnn
Relay 4 B Y
Relay 1 G N
Relay 2 G Y
Relay 3 U Y nnn
Relay 4 B Y
ESF09-0001
FIGURE 3-6 Example of an Engauge screen
4.1 SmartView
4.1.1 General
The SmartView is the basic tool in which you can communicate with the
SmartRadar FlexLine modules.
Open keyboard contacts may be dangerous in an explosion-hazardous
environment. The SmartView is built up as a totally shielded explosion-
safe tool.
ESF07-0027
FIGURE 2-1 The 3 different SmartView options
4.1.3 Connections
Within a hazardous environment, connecting or disconnecting electrical
equipment is dangerous, because of the sparking risks.
The portable SmartView however is designed such that it may be
connected/disconnected within a hazardous zone.
The fixed version SmartViews (integrated within the instrument or tank-
side mounted) contain pre-installed fixed connections.
< >
<
<
MAIN
MENU SELECT
ESF07-0024
FIGURE 2-2 The SmartView controls
PV Go to previous PV screen
Button Function
within menu ...
Commissioning Within the menu screens, move cursor 1 line up
Within the edit screens, scroll characters as long as the button is
pressed
+ Show menu
Go to PV screen
+ Decrease contrast
+ Increase contrast
Depending on the state of the menu process and the pressed button(s),
the following screens can be displayed.
start-up
SmartView
Menu Structure
PV
screen
+
<
<
MAIN
menu password-protected
extra
information
display
contrast
backlight
identification
display
settings
display test
primary
values (PV)
ESF07-0043
By using the [menu] screen of the SmartView (see FIGURE 2-3) you can
view and/or modify settings, or you can send a specific command to a
sensor or a digital I/O board.
< >
<
<
MAIN
MENU SELECT
ESF07-0030
FIGURE 2-3 The menu screen
The [backlight] screen (see FIGURE 2-4) allows you to enable/disable the
backlight. The SmartView only turns the backlight ON if following
conditions are met:
[backlight] is enabled by the host
[backlight] is enabled by the user
When the left or right button is pressed, the backlight settings
immediately changes. The backlight setting is stored in non-volatile
memory.
< >
<
<
MAIN
MENU SELECT
ESF07-0031
FIGURE 2-4 The backlight screen
The [display contrast] screen (see FIGURE 2-5) displays a horizontal scroll
bar. By moving the scroll bar, you can adjust the contrast. Moving to the
right immediately increases the contrast, moving to the left decreases
the contrast.
< >
<
<
MAIN
MENU SELECT
ESF07-0032
FIGURE 2-5 The display contrast screen
The [display settings] screen allows you to set the time-outs for the
buttons. The screen displays the following items:
Feature Possible States Default
Buttons time-out to main screen ON/OFF ON
Buttons time-out to standby mode ON/OFF ON
<
<
MAIN MAIN
E S F0 7- 0 03 3 + 00 2 9
FIGURE 2-6 Identification screen examples
The [extra information] mode can be configured to display either the [level &
temperature] screen or the [extra information] screen (see FIGURE 2-7). The
[extra information] screen displays information about a specific function.
The specific functions are described in CHAPTER 7. The [level &
temperature] screen (see FIGURE 2-7) displays information about the
measured product level and temperature. In this menu mode, it is not
possible to change any settings.
MAIN M AI N
ESF07- 0039/0012
FIGURE 2-7 The level & temperature screen (left) and the extra information screen (right)
<
<
<
MAIN MAIN
E S F0 7- 0 02 8 + 00 4 4
FIGURE 2-8 PV-screen examples (left: level status, right: digital I/O status)
Max. Size
Data Field Description
[characters]
Primary Value 9 The measured value, for example,
+025.1277
PV identification 13 Quantity name, for example,
Product level
Product temperature
P1 pressure
PV units 5 Quantity unit, for example
m
kg/m3
kPa
PV type 3 Type can be:
INN (innage)
ULL (ullage)
REL (relative)
ABS (absolute)
PV health 9 Status of the Primary Value:
UNCERTAIN
BAD
Max. Size
Data Field Description
[characters]
PV representation 15 Representation of the PV:
Manual
Last valid
Stored
Instrument
Environment
Hardware
Software
Commission
Calibration
Operational
No data
No init.
Killed
Over range
Under range
PV alarms 9 Alarm type that occurred:
High High
High
Low
Low Low
Tank identification 8 Tank name, for example, CRUDE 07
Alive indicator 1 Blinking cursor (bottom right) indicates
PV being updated
REMARKS: 1. In error situation, the data fields are filled with “#”.
When the password is entered correctly (only once for both menu
entries), you can change the values. 15 minutes after the last button is
pressed, the password needs to be re-entered.
< >
<
<
MAIN
MENU SELECT
ESF07-0040
FIGURE 2-9 The password screen
< >
<
<
MAIN
MENU SELECT
ESF07-0034
FIGURE 2-10 The board list screen
The [function list] screen (see FIGURE 2-11) displays all the available
functions of the previously selected board. You can navigate through
the function list by using the up and down buttons. You can return to
the [board list] screen by pressing the left button. A function can be
selected by simultaneously pressing the left + right button. If a
FlexConn module does not contain any function commands, this is
indicated in the list (<no cmd>).
< >
<
<
MAIN
MENU SELECT
ESF07-0045
FIGURE 2-11 The function list screen
MENU SELECT
ESF07-0035
FIGURE 2-12 The command list screen
< >
<
<
MAIN
MENU SELECT
ESF07-0036
FIGURE 2-13 The board list screen (commissioning)
The [function list] screen (see FIGURE 2-14) displays all configurable
entities of a function.
The actual entity value is also visible.
You can navigate through the board list by using the up or down
button. A function can be selected by simultaneously pressing the
left + right button. You can return to the [board list] screen by pressing
the left button.
< >
<
<
MAIN
MENU SELECT
ESF07-0046
FIGURE 2-14 The function list screen (commissioning)
< >
<
<
MAIN
MENU SELECT
ESF07-0047
FIGURE 2-15 The entity list screen
NOTE: Use the left button to return to the [entity list] screen
without executing the modification(s). Press the left
+ right button simultaneously to undo this (these)
modification(s)!
<
<
<
MAIN MAIN
ESF07-0037
FIGURE 2-16 Examples of the value edit screen
4.2 Engauge
field line
BPM or RS-485
(or RS-485)
RS-232
RS-232
ESF07-0041
FIGURE 2-17 Connecting the Engauge service tool - wired connections
OneWireless
SmartRadar FlexLine
OneWireless
Gateway
Ethernet
Lantronix
(or RS-485)
RS-232
ESF09-0010
FIGURE 2-18 Connecting the Engauge service tool - OneWireless
ESF09-0001
FIGURE 2-19 Example (1) of an Engauge screen
ESF09-0002
FIGURE 2-20 Example (2) OneWireless Site Scan
ESF09-0003
FIGURE 2-21 Example (3) of an Engauge screen
ESF09-0004
FIGURE 2-22 Example (4) of an Engauge screen
4. On the Wireless Device Manager Settings page, type the WDM Tag
Name and the Description.
The Tag Name is the unique name that is used to identify the WDM. It can
be up to 16 characters long and must begin with an alphabetic character.
Do not use special characters in the Tag Name; underscore is the only
acceptable character. After completing the initial configuration, you cannot
change the WDM name.
The Description can be up to 255 characters long.
9. Click Next.
The Network Settings page appears.
10. Under Field Device Network (FDN), configure the network settings for the
wireless field device network as follows.
a) Field Device Network IP Address: These settings are used to
configure the wireless field device network Ethernet connection
for the WDM. This is used for communication with FDAP.
11. Under Process Control Network (PCN), configure the process control network
settings as follows.
• Process Control Network IP Address: The process control network
settings are used to configure the process control network Ethernet
connections for the WDM. This is used for communication with moni-
toring applications and external controllers.
• Subnet Mask
• Default gateway: Used to access the subnets outside the PCN
subnet. This is an optional configuration option.
12. Click Next.
• The password must contain at least one character and can contain up
to 32 characters. It should not start or end with a space and must not
contain single quote (‘).
17. Verify the WDM settings, correct errors if any, and then click Finish.
If there are any errors in the configuration information that you have
provided, then the system does not allow you to click Finish.
18. On the Browser Redirect dialog box, click OK.
The wizard redirects the Web browser to the revised process control
network IP address.
CHAPTER 5 INSTALLATION
communication antenna
lightning arrestor
1
4. Click Apply.
The unprovisioned access points start appearing in the Selection
Panel. You can filter the device list to view only the unprovisioned
access points in the network.
5. On the ribbon bar, in the Filter group, click Device Status > Un-
Provisioned.
6. Expand the extended Selection Panel to view the available device
parameters.
7. Select the required access point in the Selection Panel or the map
view and then click Accept on the ribbon bar.
8. Click Accept.
The Progress column displays the status as In Progress, Provi-
sioning, and then Completed when complete. Do not close the
dialog box when over-the-air provisioning is initiated for devices.
9. Click Close.
The Accept Over the Air Devices dialog box closes.
6.1.5 Resetting the provisioning key from SmartRadar Flexline gauge using a
SD card
To reset the provisioning key from a SmartRadar Flexline gauge
using a SD card
1. Connect an SD card to a computer or a Laptop and format the card
with default windows settings.
2. Generate a reset key using the OneWireless Device Manager and
transfer the key to the SD card.
3. Power OFF the SmartRadar FlexLine device and open the
enclosure.
4. Insert the SD card in the SD card slot provided on the HCI-1WL
board.
5. Close the SmartRadar FlexLine device and power it on.
The provisioning key on the SmartRadar FlexLine is automatically reset
and the device enters the factor default mode.
6.2.2.1 Considerations
Device routing assignment can be configured only for devices that
are capable of operating as routers and I/O devices.
To configure routing assignment
1. On the Selection Panel, select the field device.
2. On the Property Panel, expand Device Management.
3. Select Routing Assignment, as appropriate.
The following are the Routing Assignment options available.
• Routing Disabled — Disables the ability of a routing field device
to function as a router. The field device can function only as an I/O
device.
• Routing Enabled — Enables the routing field device to function
as a router and an I/O device. The default join policy configured is
Follow System Manager Policy.
• Not Applicable
- Does not apply to devices that are capable of operating as
access points.
- Does not apply to devices that are only capable of operating as
routers.
4. Select one of the following Join Assignment options, as required.
The Join Assignment overrides the system manager join policy.
This is applicable only for routing field devices.
• Join Disabled — Disables device-join through this device.
• Join Enabled — Enables device-join through this device.
• Follow System Manager Policy — Enables the device to follow
the system manager join policy. Device-join through this device
depends on the configured system manager join policy.
The Join Status is a read-only parameter that indicates the resultant
join state for all the devices.
• Access Points, FDAP access points, and FDAP routers have the
Join Assignment permanently set to Join Enabled.
• Non-routing field devices have the Join Assignment perma-
nently set to Join Disabled.
3. In the Channel drop-down list, select the channels for which data
publication needs to be enabled.
6.4.2 Configure CIU Prime and CIU Plus using the Ensite Pro configuration tool
The following details describe the settings for CIU Prime configuration.
For more information regarding the Ensite Pro configuration tool, refer
to the Ensite Pro Configuration Tool Instructional manual.
1. In the Edit CIU Prime dialog box, enter the following details in
HostPort1 and HostPort2.
1. Baudrate — Select 19200 as the baudrate from the drop-down
list.
2. Turn-around delay — Enter 10 msec as the turn around delay.
2. In the CIU Prime — FieldPort Settings dialog box, enter the
following details in FieldPort.
1.Time-out — Enter 500 msec as the time-out
2.Retries— Enter 3 as the number of retries.
The publication data for input and output field devices can be configured
using the Input Publication panel in the Property Panel. Depending on
the device type, a field device can have an Input Publication panel. This
is determined by the DD file for the field device.
The Input Publication panel contains the following configuration options.
Contract Status — A contract is a communication resource
(bandwidth) allocation between two devices on the ISA100 network.
The following are the status values that are displayed depending on
the status of the contract.
• Not Configured - No contract established due to incorrect config-
uration of the device.
• Activating - Contract establishment is in progress.
• Active- Contract is active.
• Active, Negotiated Down - If a device requests a contract for
periodic publications at a fast rate (such as 1 second) and if the
communication resources are not available, the contract is nego-
tiated down to a slower publication period (such as 5 seconds).
• Terminating - Contract termination is in progress.
• Failed - Contract establishment is failed.
• Inactive - Contract is inactive.
Rate – The rate at which a field device publishes data.
For serial interface connection, connect a serial cable from the interface
client to the serial port on the WDM.
6.5.2.1.1 Rs-232
For RS-232, select the serial port on which the serial cable is connected as
COM1.
6.5.2.1.2 RS-485
2. In the Lantronix Devices tree on the left pane, select the Lantronix
Xpress-DR or Lantronix Xpress-DR-IAP device name.
3. On the Telnet Configuration tab, click Connect.
4. When prompted, press Enter to go to the setup mode.
5. On the Main menu, press 1 on the keyboard to configure channel 1
and set the configuration parameters as follows:
• Baud Rate = 19200
• I/F Mode = 4C
• Flow = 00
• Port Number = 34568
• Connect Mode = CC
• Datagram Mode = 01
The Remote IP Address can be entered only when the Datagram
Mode is set to 01.
• Remote IP Address = IP Address of the WDM
• Remote Port = 55598
• Packet Control = 00
• Send Character 1 = 00
• Send Character 2 = 00
6. Press 9 on the keyboard, to save and exit the Lantronix main menu.
CHAPTER 7 COMMISSIONING
7.1 General
7.1.1 Introduction
This chapter provides an overview of the commissioning information as
per the FlexConn module.
In some cases the Wireless Builder and/or the Key Server Manager
Wireless
application(s) for R120 are used. This is indicated by a corresponding
Builder button (left).
Key Server
Manager
7.2.1 Introduction
The Host Communication Instrument - Bi-Phase Mark (HCI-BPM) board
is a communication module for the instrument (gauge).
isolation transformer
F4A07-0005
FIGURE 7-1 The HCI-BPM board with its isolation transformer
* After having checked/set all before listed entities, make sure you
check the following:
• The [Board Commissioned] and the [BPM slave Commissioned] entities are
<True>.
• The [Board Health] and the [BPM slave Health] entities are <GOOD>.
7.3.1 Introduction
The Host Communication Instrument - Gauge Processing Unit (HCI-
GPU) board is a communication module for the instrument (gauge).
F4A07- 0006a
FIGURE 7-2 The HCI-GPU board
The HCI-GPU can communicate with any hosts through three different
communication protocols:9
• The Enraf GPU protocol with its records and items (limited)
• The Enraf FlexConn protocol with its entities
• The Modbus protocol
In the first situation the CAN-RS module behaves similar to an Enraf
GPU slave, communicating through the Enraf GPU protocol. If a valid
record or item is received, a related FlexConn message type A is issued
to the CAN-bus for obtaining the desired data.
In the second situation, when production-, test-, configuration-, and
service tools are used, the FlexConn protocol must be used through the
RS232/485 physical layer.
In the third situation the CAN-RS module behaves similar to a Modbus
slave communicating through the Modbus protocol.
7.3.2 Specifications
• System Specification:
Typical TurnAround Delay (TAD) = 35 ms *
Maximum TAD = 65 ms *
Refresh rate of 32 FlexLines on one link = 5.76 sec * (@ scan rate
of 180 ms)
7.3.3.1 Introduction
Slave Coil
Function 05 Force data CRC check
address address
8 bits 8 bits 16 bits 16 bits 16 bits
Slave Coil
Function 05 Force data CRC check
address address
8 bits 8 bits 16 bits 16 bits 16 bits
7.3.3.4 Commisioning
address+0 Byte 1
address+1 Byte 2
address+2 Byte 3
address+3 Byte 4
• The first table that follows contains all gauge data in fixed point
format starting at 0x0000. A scaling factor needs to be applied
here.
• The second table contains all gauge data in floating point format
starting at 0x1000. No scaling to be applied here.
Floating point: IEEE-754
Signed integers: two’s complement
Interpretation
Conversion
parameter
Data type
Modbus
Modbus
Modbus
Scaling
Par.no.
factor
units
No. of registers
Address (dec)
address (hex)
Interpretation
Conversion
parameter
Data type
Modbus
Modbus
Modbus
Scaling
Par.no.
factor
units
ProductLevelStatus 0x0002 40003 char 1 See 7.3.3.6.1
ProductLevelAlarms 0x0003 40004 char 1 See 7.3.3.6.13
2 Water Level 0x0004 SD40005 long 2 METRES devide by 10000
FEET devide by 1000
INCHES devide by 100
WaterLevelStatus 0x0006 40007 char 1 See 7.3.3.6.2
3 ProductTemp 0x0007 SD40008 long 2 CELSIUS devide by 100
FAHRENHEIT devide by 100
ProductTempStatus 0x0009 40010 char 1 See 7.3.3.6.3
4 VapRoomTemp 0x000A SD40011 long 2 CELSIUS devide by 100
FAHRENHEIT devide by 100
VapRoomTempStatus 0x000C 40013..16 byte 4 See 7.3.3.6.4
5 VapRoomPress 0x0010 SD40017 long 2 PASCAL multiply by 100
KILO_PASCAL devide by 1000
PSI devide by 1000
VapRoomPressStatus 0x0012 40019..23 byte 5 See 7.3.3.6.5
6 ObsDensity 0x0017 SD40024 long 2 KILOGRAM_PER_M3 devide by 100
POUNDS_PER_FT3 devide by 10000
DEGREES_API devide by 1000
ObsDensityStatus 0x0019 40026..30 byte 5 See 7.3.3.6.6
7 Gauge Status 0x002A 40043 byte 1 See 7.3.3.6.14
8 Spot temperature 1 0x0200 SD40513 long 2 CELSIUS devide by 100
FAHRENHEIT devide by 100
9 Spot temperature 1 pos. 0x0202 SD40515 long 2 METRES devide by 10000
FEET devide by 1000
INCHES devide by 100
No. of registers
Address (dec)
address (hex)
Interpretation
Conversion
parameter
Data type
Modbus
Modbus
Modbus
Scaling
Par.no.
factor
units
FAHRENHEIT devide by 100
17 Spot temperature 5 pos. 0x0212 SD40531 long 2 METRES devide by 10000
FEET devide by 1000
INCHES devide by 100
18 Spot temperature 6 0x0214 SD40533 long 2 CELSIUS devide by 100
FAHRENHEIT devide by 100
19 Spot temperature pos. 6 0x0216 SD40535 long 2 METRES devide by 10000
FEET devide by 1000
INCHES devide by 100
20 Spot temperature 7 0x0218 SD40537 long 2 CELSIUS devide by 100
FAHRENHEIT devide by 100
21 Spot temperature 7 pos. 0x021A SD40539 long 2 METRES devide by 10000
FEET devide by 1000
INCHES devide by 100
22 Spot temperature 8 0x021C SD40541 long 2 CELSIUS devide by 100
FAHRENHEIT devide by 100
23 Spot temperature 8 pos. 0x021E SD40543 long 2 METRES devide by 10000
FEET devide by 1000
INCHES devide by 100
24 Spot temperature 9 0x0220 SD40545 long 2 CELSIUS devide by 100
FAHRENHEIT devide by 100
25 Spot temperature 9 pos. 0x0222 SD40547 long 2 METRES devide by 10000
FEET devide by 1000
INCHES devide by 100
26 Spot temperature 10 0x0224 SD40549 long 2 CELSIUS devide by 100
FAHRENHEIT devide by 100
No. of registers
Address (dec)
address (hex)
Interpretation
Conversion
parameter
Data type
Modbus
Modbus
Modbus
Scaling
Par.no.
factor
units
FEET devide by 1000
INCHES devide by 100
34 Spot temperature 14 0x0234 SD40565 long 2 CELSIUS devide by 100
FAHRENHEIT devide by 100
35 Spot temperature 14 pos. 0x0236 SD40567 long 2 METRES devide by 10000
FEET devide by 1000
INCHES devide by 100
36 Spot temperature 15 0x0238 SD40569 long 2 CELSIUS devide by 100
FAHRENHEIT devide by 100
37 Spot temperature 15 pos. 0x023A SD40571 long 2 METRES devide by 10000
FEET devide by 1000
INCHES devide by 100
38 Spot temperature 16 0x023C SD40573 long 2 CELSIUS devide by 100
FAHRENHEIT devide by 100
39 Spot temperature 16 pos. 0x023E SD40575 long 2 METRES devide by 10000
FEET devide by 1000
INCHES devide by 100
40 Ambient Temperature 0x0300 SD40769 long 2 CELSIUS devide by 100
FAHRENHEIT devide by 100
Ambient
0x0302 40771 integer 1 See 7.3.3.6.7
TemperatureStatus
41 Product Pressure 0x0303 SD40772 long 2 PASCAL multiply by 100
KILO_PASCAL devide by 1000
PSI devide by 1000
Product PressureStatus 0x0305 40774 byte 5 See 7.3.3.6.8
No. of registers
Address (dec)
address (hex)
Interpretation
Conversion
parameter
Data type
Modbus
Modbus
Modbus
Scaling
Par.no.
factor
units
Hart Input Variable 4 0x0315 40790 Integer 1 See 7.3.3.6.9
status
46 Hart Input Variable 5 0x0316 SD40791 long 2 Free format devide by 100
Hart Input Variable 5 0x0318 40793 Integer 1 See 7.3.3.6.9
status
47 First Relay Board 0x0319 SD40794 long 2
- Relay 1
First Relay Board 0x031B 40796 Integer 1 See 7.3.3.6.10
- Relay 1 Status
48 First Relay Board 0x031C SD40797 long 2
- Relay 2
First Relay Board 0x031E 40799 Integer 1 See 7.3.3.6.10
- Relay 2 Status
49 First Relay Board 0x031F SD40800 long 2
- Relay 3
First Relay Board 0x0321 40802 Integer 1 See 7.3.3.6.10
- Relay 3 Status
50 First Relay Board 0x0322 SD40803 long 2
- Relay 4
First Relay Board 0x0324 40805 Integer 1 See 7.3.3.6.10
- Relay 4 Status
51 Second Relay Board 0x0325 SD40806 long 2
- Relay 1
Second Relay Board 0x0327 40808 Integer 1 See 7.3.3.6.10
- Relay 1 Status
52 Second Relay Board 0x0328 SD40809 long 2
- Relay 2
Second Relay Board 0x032A 40811 Integer 1 See 7.3.3.6.10
- Relay 2 Status
53 Second Relay Board 0x032B SD40812 long 2
- Relay 3
Second Relay Board 0x032D 40814 Integer 1 See 7.3.3.6.10
- Relay 3 Status
54 Second Relay Board 0x032E SD40815 long 2
- Relay 4
Second Relay Board 0x0330 40817 Integer 1 See 7.3.3.6.10
- Relay 4 Status
55 Overfill Protection Status 0x0331 40818 char 1 See 7.3.3.6.12
First Relay Board
56 Overfill Protection Status 0x0332 40819 char 1
Second Relay Board
57 Safety ShutDown Timer 0x0333 40820 Integer 1
Left First Relay Board
58 Safety ShutDown Timer 0x0334 40821 Integer 1
Left Second Relay Board
59 Analog Output 0x0335 SD40822 long 2 N.A. devide by 100
Analog OutputStatus 0x0337 40824 integer 1 See 7.3.3.6.11
60 Tank Identification 0x0338 40825 char 8 N.A.
No. of registers
Address (dec)
address (hex)
Interpretation
Conversion
parameter
Data type
Modbus
Modbus
Modbus
Scaling
Par.no.
factor
units
61 GPU Device Number 0x0340 40833 integer 1
No. of registers
Address (dec)
address (hex)
Interpretation
Conversion
parameter
Data type
Modbus
Modbus
Modbus
Par.no.
units
1 ProductLevel 0x1000 SD44097 floating 2 METRES
point
FEET
INCHES
ProductLevelStatus 0x1002 44099 char 1 See 7.3.3.6.1
ProductLevelAlarms 0x1003 44100 char 1 See 7.3.3.6.13
2 WaterLevel 0x1004 SD44101 floating 2 METRES
point
FEET
INCHES
WaterLevelStatus 0x1006 44103 char 1 See 7.3.3.6.2
3 ProductTemp 0x1007 SD44104 floating 2 CELSIUS
point
FAHRENHEIT
ProductTempStatus 0x1009 44106 char 1 See 7.3.3.6.3
4 VapRoomTemp 0x100A SD44107 floating 2 CELSIUS
point
FAHRENHEIT
VapRoomTempStatus 0x100C 44109..12 byte 4 See 7.3.3.6.4
5 VapRoomPress 0x1010 SD44113 floating 2 PASCAL
point
KILO_PASCAL
PSI
VapRoomPressStatus 0x1012 44115..19 byte 5 See 7.3.3.6.5
6 ObsDensity 0x1017 SD44120 floating 2 KILOGRAM_PER_M3
point
POUNDS_PER_FT3
DEGREES_API
ObsDensityStatus 0x1019 44122..26 byte 5 See 7.3.3.6.6
7 Gauge Status 0x102A 44139 byte 1 See 7.3.3.6.14
No. of registers
Address (dec)
address (hex)
Interpretation
Conversion
parameter
Data type
Modbus
Modbus
Modbus
Par.no.
units
8 Spot temperature 1 0x1200 SD44609 floating 2 CELSIUS
point
FAHRENHEIT
9 Spot temperature 1 pos. 0x1202 SD44611 floating 2 METRES
point
FEET
INCHES
10 Spot temperature 2 0x1204 SD44613 floating 2 CELSIUS
point
FAHRENHEIT
11 Spot temperature 2 pos. 0x1206 SD44615 floating 2 METRES
point
FEET
INCHES
12 Spot temperature 3 0x1208 SD44617 floating 2 CELSIUS
point
FAHRENHEIT
13 Spot temperature 3 pos. 0x120A SD44619 floating 2 METRES
point
FEET
INCHES
14 Spot temperature 4 0x120C SD44621 floating 2 CELSIUS
point
FAHRENHEIT
15 Spot temperature 4 pos. 0x120E SD44623 floating 2 METRES
point
FEET
INCHES
16 Spot temperature 5 0x1210 SD44625 floating 2 CELSIUS
point
FAHRENHEIT
17 Spot temperature 5 pos. 0x1212 SD44627 floating 2 METRES
point
FEET
INCHES
18 Spot temperature 6 0x1214 SD44629 floating 2 CELSIUS
point
FAHRENHEIT
19 Spot temperature 6 pos. 0x1216 SD44631 floating 2 METRES
point
FEET
INCHES
No. of registers
Address (dec)
address (hex)
Interpretation
Conversion
parameter
Data type
Modbus
Modbus
Modbus
Par.no.
units
FAHRENHEIT
21 Spot temperature 7 pos. 0x121A SD44635 floating 2 METRES
point
FEET
INCHES
22 Spot temperature 8 0x121C SD44637 floating 2 CELSIUS
point
FAHRENHEIT
23 Spot temperature 8 pos. 0x121E SD44639 floating 2 METRES
point
FEET
INCHES
24 Spot temperature 9 0x1220 SD44641 floating 2 CELSIUS
point
FAHRENHEIT
25 Spot temperature 9 pos. 0x1222 SD44643 floating 2 METRES
point
FEET
INCHES
26 Spot temperature 10 0x1224 SD44645 floating 2 CELSIUS
point
FAHRENHEIT
27 Spot temperature 10 pos. 0x1226 SD44647 floating 2 METRES
point
FEET
INCHES
28 Spot temperature 11 0x1228 SD44649 floating 2 CELSIUS
point
FAHRENHEIT
29 Spot temperature 11 pos. 0x122A SD44651 floating 2 METRES
point
FEET
INCHES
30 Spot temperature 12 0x122C SD44653 floating 2 CELSIUS
point
FAHRENHEIT
31 Spot temperature 12 pos. 0x122E SD44655 floating 2 METRES
point
FEET
INCHES
32 Spot temperature 13 0x1230 SD44657 floating 2 CELSIUS
point
FAHRENHEIT
33 Spot temperature 13 pos. 0x1232 SD44659 floating 2 METRES
point
FEET
No. of registers
Address (dec)
address (hex)
Interpretation
Conversion
parameter
Data type
Modbus
Modbus
Modbus
Par.no.
units
INCHES
34 Spot temperature 14 0x1234 SD44661 floating 2 CELSIUS
point
FAHRENHEIT
35 Spot temperature 14 pos. 0x1236 SD44663 floating 2 METRES
point
FEET
INCHES
36 Spot temperature 15 0x1238 SD44665 floating 2 CELSIUS
point
FAHRENHEIT
No. of registers
Address (dec)
address (hex)
Interpretation
Conversion
parameter
Data type
Modbus
Modbus
Modbus
Par.no.
units
KILO_PASCAL
PSI
Hart Input Variable 3 0x1312 44883 Integer 1 See 7.3.3.6.9
status
45 Hart Input Variable 4 0x1313 SD44884 floating 2 KILOGRAM_PER_M3
point
POUNDS_PER_FT3
DEGREES_API
Hart Input Variable 4 0x1315 44886 Integer 1 See 7.3.3.6.9
status
46 Hart Input Variable 5 0x1316 SD44887 floating 2 Free format
point
Hart Input Variable 5 0x1318 44889 Integer 1 See 7.3.3.6.9
status
47 First Relay Board - Relay 0x1319 SD44890 floating 2
1 point
First Relay Board - Relay 0x131B 44892 Integer 1 See 7.3.3.6.10
1 Status
48 First Relay Board - Relay 0x131C SD44893 floating 2
2 point
First Relay Board - Relay 0x131E 44895 Integer 1 See 7.3.3.6.10
2 Status
49 First Relay Board - Relay 0x131F SD44896 floating 2
3 point
First Relay Board - Relay 0x1321 44898 Integer 1 See 7.3.3.6.10
3 Status
50 First Relay Board - Relay 0x1322 SD44899 floating 2
4 point
First Relay Board - Relay 0x1324 44901 Integer 1 See 7.3.3.6.10
4 Status
51 Second Relay Board - 0x1325 SD44902 floating 2
Relay 1 point
Second Relay Board - 0x1327 44904 Integer 1 See 7.3.3.6.10
Relay 1 Status
52 Second Relay Board - 0x1328 SD44905 floating 2
Relay 2 point
Second Relay Board - 0x132A 44907 Integer 1 See 7.3.3.6.10
Relay 2 Status
53 Second Relay Board - 0x132B SD44908 floating 2
Relay 3 point
Second Relay Board - 0x132D 44910 Integer 1 See 7.3.3.6.10
Relay 3 Status
54 Second Relay Board - 0x132E SD44911 floating 2
Relay 4 point
Second Relay Board - 0x1330 44913 Integer 1 See 7.3.3.6.10
Relay 4 Status
55 Overfill Protection Status 0x1331 44914 char 1 See 7.3.3.6.12
First Relay Board
No. of registers
Address (dec)
address (hex)
Interpretation
Conversion
parameter
Data type
Modbus
Modbus
Modbus
Par.no.
units
56 Overfill Protection Status 0x1332 44915 char 1 See 7.3.3.6.12
Second Relay Board
57 Safety Shutdown Timer 0x1333 44916 Integer 1
Left First Relay Board
58 Safety Shutdown Timer 0x1334 44917 Integer 1
Left Second Relay Board
59 Analog Output 0x1335 SD44918 floating 2 N.A.
point
Analog Output Status 0x1337 44920 integer 1 See 7.3.3.6.11
60 Tank Identification 0x1338 44921 char 8 N.A.
61 GPU Device Number 0x1340 44929 integer 1
After being requested by the host, the slave returns the relevant status
information. The following tables provide the possible received status
bytes from the relevant registers, such as product level, product
temperature and so on.
For a listing of ASCII codes, see 7.3.4 - Standard ASCII codes.
This register contains the bit-coded product level status. This status
information is coded such that an ASCII code for a character is
generated. The ASCII characters are listed below.
Product Level status Meaning
F invalid level data
C out of measuring range
B measurement blocked
M warning
? reduced accuracy
- valid product level
This register contains the bit-coded water level status. This status
information is coded such that an ASCII code for a character is
generated. The ASCII characters are listed below.
Water Level status Meaning
F invalid water alarm data
A water above probe warning
Health
status Meaning
code
2561 LOWEST_ELEMENT_OFFSET_NOT_COMMISSIONED
2562 MRT_ELEMENT_LENGTH_NOT_COMMISSIONED
2563 MEASUREMENT_TYPE_NOT_COMMISSIONED
2564 ELEMENT_TYPE_NOT_COMMISSIONED
2565 NUMBER_OF_ELEMENTS_NOT_COMMISSIONED
2566 SECOND_ELEMENT_OFFSET_NOT_COMMISSIONED
2567 SENSOR_LENGTH_NOT_COMMISSIONED
2568 RTD_ELEMENT_POSITION_NOT_COMMISSIONED
2569 RTD_CONFIGURATION_NOT_COMMISSIONED
2570 MULTI_ELEMENT_OPTION_NOT_COMMISSIONED
2571 DYNAMIC_EXCLUSION_NR_OF_ELEMENTS_NOT_COMMISSIONED
2572 LOW_ELEMENT_USAGE_MEASUREMENT_TYPE_NOT_COMMISIONED
2573 TEMPERATURE_ELEMENT_EXCLUDE_ZONE_NOT_COMMISSIONED
2574 SMOOTHING_LEVEL_NOT_COMMISSIONED
2575 R_ELEMENT_SHORTCUT
2576 R_ELEMENT_NOT_CONNECTED
2577 T_ELEMENT_OUT_OF_RANGE
2578 ELEMENT_IN_WATER
2579 ELEMENT_FAIL
2580 NO_VALID_PRODUCT_LEVEL
2581 ELEMENT_SKIPPING
2582 NO_RELEVANT_ELEMENTS
2583 LEVEL_BELOW_LOWEST_ELEMENT
2584 NO_LAST_VALID_VALUE_AVAILABLE
2585 LEVEL_BELOW_TEMP_EXCLUDE_ZONE
2586 LEVEL_IN_TEMP_EXCLUDE_ZONE
2587 R_CABLE_OUT_OF_LIMITS
2588 R_TEST_OUT_OF_LIMITS
2589 VCC1_OUT_OF_LIMITS
2590 R_ELEMENT_INVALID_VALUE
2591 VOLTAGE_MON_PRIMARY_CIRCUIT_LO_LIM_EXCEEDED
2592 VOLTAGE_MON_PRIMARY_CIRCUIT_HI_LIM_EXCEEDED
2593 PROBE_RANGE_NOT_COMMISSIONED
2594 PROBE_OUT_OF_WNM_RANGE
Health
status Meaning
code
2596 PRODUCT_LEVEL_NO_STATUS_CATEGORY_GOOD_ACTUAL
Health
status Meaning
code
1536 MORE_STATUS_AVAILABLE
1537 PV_OUT_OF_LIMITS
1538 SV_OR_TV_OUT_OF_LIMITS
1539 DEVICE_MALFUNCTION
1540 WRONG_PV_UNIT_CODE
1541 SCAN_INITIALIZING
1542 PRODUCT_LEVEL_SCAN_ERROR
1543 P1_NOT_INSTALLED
1544 P3_NOT_INSTALLED
1545 NO_P1_AVAILABLE
1546 NO_P3_AVAILABLE
1547 UNCERTAIN_P1
1548 UNCERTAIN_P3
1549 MANUAL_P1_USED
1550 MANUAL_P3_USED
1551 LAST_VALID_P3_USED
1552 NO_MANUAL_OR_LAST_VALID_P3
1553 NO_PRODUCT_LEVEL_AVAILABLE
1554 UNCERTAIN_PRODUCT_LEVEL
1555 PRODUCT_LEVEL_BELOW_MINIMUM_HIMS
1556 LAST_VALID_PRODUCT_LEVEL_USED
1557 MANUAL_PRODUCT_LEVEL_USED
1558 NO_WATER_LEVEL_AVAILABLE
1559 UNCERTAIN_WATER_LEVEL
1560 LAST_VALID_WATER_LEVEL_USED
1561 WATER_LEVEL_ABOVE_P1
Health
status Meaning
code
1562 NEGATIVE_DENSITY_CALCULATED
1563 NO_MANUAL_OR_LAST_VALID_DENSITY
1564 MANUAL_WATER_LEVEL_USED
1565 DENSITY_OPTION_NOT_ENABLED
1566 P1_ERROR
1567 P3_ERROR
1568 G1_ERROR
1569 G2_ERROR
1570 G3_ERROR
1571 G4_ERROR
1572 G5_ERROR
1573 DENSITY_ERROR
1574 P1_UNCERTAIN
1575 P3_UNCERTAIN
1576 G1_UNCERTAIN
1577 G2_UNCERTAIN
1578 G3_UNCERTAIN
1579 G4_UNCERTAIN
1580 G5_UNCERTAIN
1581 DENSITY_UNCERTAIN
1582 TOO_MANY_HART_DEVICES_DETECTED
1583 WATER_LEVEL_SCAN_ERROR
7.3.3.6.10 Relay
Health
status Meaning
code
2305 RELAY_TEST_FAILED
2307 PV_SCAN_VALUE_BAD
2308 PV_SCAN_VALUE_UNCERTAIN
2309 INVALID_MESSAGE_LENGTH
2310 NACK_CODE_RECEIVED
2311 ERROR_REQUESTING_ENTITY
2312 NO_BOARD_AVAILABLE
2313 ERROR_RELAY_1
2314 ERROR_RELAY_2
2315 ERROR_RELAY_3
2316 ERROR_RELAY_4
2317 LICENSE_NOT_SET
2318 REDUNDANT_BOARD_ERROR
2319 XBAND_OVERFILL_DISABLED
2320 NOT_COMMISSIONED
2321 BOARD_HEALTH_BAD
2322 REDUNDANT_BOARD_HEALTH_BAD
2323 REDUNDANT_BOARD_COM_FAIL
2324 SAFETY_TIMER_EXPIRED
2325 COMMISSIONING_MISMATCH
2326 RELAY_MODE_NOT_COMMISSIONED
2327 XBAND_BOARD_MISSING
2328 XBAND_LEVEL_BAD
2329 ALARM_MODE_NOT_COMMISSIONED
2330 MONITOR_BOARD_PARAMETERS_NOT_COMMISSIONED
Health
status Meaning
code
2817 CALIBRATION_SET_POINTS_NOT_CALIBARTED
2818 POLLING_ADDRESS_SET_TO_NON_ZERO
2819 DAC_READ_BACK_FAIL
2820 AO_INITIALIZING
2821 BURNOUT_VALUE_OUT_OF_RANGE
2822 ANAOUT_FIXED_AT_4MA
2823 MULTI_DROP_MODE
2824 TUNNEL_FAILED_IN_GETTING_AN_ENTITY
2825 TUNNEL_FAILED_IN_PUTTING_AN_ENTITY
2826 UNITS_NOT_SELECTED
2827 LINKED_PV_NOT_SET
2828 LINKED_SV_NOT_SET
2829 LINKED_TV_NOT_SET
2830 LINKED_QV_NOT_SET
2831 PV_UNIT_CODE_NOT_SELECTED
2832 RANGE_VALUES_NOT_SELECTED
2833 PV_OUT_OF_LIMITS
2834 UPPER_TRANSDUCER_LIMIT_NOT_SET
2835 TRANSDUCER_SERIAL_NUMBER_NOT_SET
2836 UNABLE_TO_GET_LINKED_VARIABLE
2837 UPPER_RANGE_VALUE_GREATER_THAN_UPPER_TRANSDUCER_
LIMIT
2838 LOWER_RANGE_VALUE_LESS_THAN_LOWER_TRANSDUCER_LIMIT
7.3.3.6.13 Alarms
The following table lists the Gauge status information and the
description.
Gauge status (decimal) Meaning
0 Level gauge is measuring level
255 Level gauge is in failure
The following table lists Modbus commands and their related addresses
(coils) and data.
Modbus Modbus Number of
Modbus command Data
address (hex) address (dec) registers
FlexConn Modbus Protocol Switch 0x00 00001 0xFF00 1
Reset Device 0x10 00017 0xFF00 1
Product Level Alarm Test Hi Hi 0x11 00018 0xFF00 1
Product Level Alarm Test Hi 0x12 00019 0xFF00 1
Product Level Alarm Test Lo 0x13 00020 0xFF00 1
Product Level Alarm Test Lo Lo 0x14 00021 0xFF00 1
Start Proof Test First Relay Board 0x15 00022 0xFF00 1
Stop Proof Test First Relay Board 0x16 00023 0xFF00 1
Start Proof Test Second Relay Board 0x17 00024 0xFF00 1
Stop Proof Test Second Relay Board 0x18 00025 0xFF00 1
7.4.1 Introduction
The Host Communication Instrument OneWireless (HCI-1WL) board is
a communication module for the instrument (gauge).
radio module
F4A09-0011
FIGURE 7-4 The HCI-1WL duplex board with flatcable interconnection
7.4.3.1 Introduction
7.4.3.3 Authentication
1. Ensure the OneWireless Network is operational, including running
Key Server Key Server Manager (KSM) software, and at least 1 multi-node
Manager configured as gateway.
2. Use the KSM to write security information to a memory card. See the
Key Server Manager manual for instructions on how to use the key
server. For a sample screen, see FIGURE 7-5.
3. Insert the memory card into the memory card slot of the HCI-1WL
device.
4. Make sure to fully close the device if it is installed in an explosion
hazardous area.
5. Switch on the device
The device will now automatically join the OneWireless network.
You can follow the authentication/joining process by navigating to the
correct page on the SmartView, see 7.5.7.1. Or by using Engauge, see
7.5.8.1, if there is also a wired connection available.
If the message [NOREDUN] or [CONNECT] does NOT become visible, the
authentication failed.
* If authentication failed, verify that the wireless network is operating
correctly, and try again with a new security key.
7.4.5.1 Introduction
Before you continue with this step, familiarize yourself with the
Wireless Builder configuration tool for the OneWireless network. For
a detailed operation guide for the Wireless Builder, Refer to the
OneWireless Wireless Builder User’s Guide, R120.
With the Wireless Builder you can create, delete, commission, load, and
unload the SmartRadar just like any other OneWireless devices. You
can also activate and inactivate transducer blocks, and program the
different parameters, such as publication period, as with any other
devices.
Once the Authentication process has been successfully completed, the
SmartRadar automatically is listed in the Online window of Wireless
Builder as an uncommissioned device.
Right-click the device to commission it as described in the Wireless
Builder manual.
By default, the SmartRadar contains one transducer block, Radar Level.
More transducer blocks can be added, during further commissioning.
7.4.5.2.1 Introduction
Wireless
* Expand the device template in the Library tree (click +), to view all
the available transducer blocks.
Builder
* Drag and drop the transducer block(s) that must be instantiated
(= made concrete) from the Library tree to the device in the Offline
tree.
The Main Tab contains the general settings of the Transducer Block
(TB).
Parameter Description
Name Specify the name of the transducer block.
Associated Device Specifies the device that contains the transducer block that you are editing.
The device name is set during commissioning with the Wireless Builder and is stored
in the TAG descriptor entity.
Actual Mode Specify the actual operation mode of the transducer block. This may differ from the
normal mode. For example, if the device is Out of Service.
Normal Mode Specify that this is the mode the transducer block should be in normal situations.
Permitted Mode Specify the permitted modes for the transducer block.
Parameter Description
Process Variable You can manually overwrite the parameter (such as level), if the transducer block is
set to manual mode.
This is not standard within OneWireless. The manual value entered here is also
available in the FlexConn environment. If the Transducer block is not in Manual mode
an error code is generated after selecting OK.
Parameter Description
EU at 100% Not used in the SmartRadar FlexLine.
EU at 0% Not used in the SmartRadar FlexLine.
Units Index Select the required engineering unit from the list of available units. (Level units for the
level TB, and temperature units for the Temperature TB)
Note: For supported units, see 7.4.5.2.8.
Decimal Not used in the SmartRadar FlexLine.
The Alarm tab contains the various alarm settings (High high, High,
Low, and Low low).
Parameter Description
Alert Disable Use this option to disable an alarm.
Alert Priority Use this option to define the alert priority.
For more information on alert priority, see the OneWireless Documentation.
In Alarm Specifies the actual alarm status.
Alarm Limit Specify the alarm trip point.
Parameter Description
Stale Lim Specify the Publication data stale limit. For more details, see OneWireless
documentation.
Period Specify the publication time for the primary variable of this transducer block. The
values can be 1, 5, 10, or 30 seconds. For more details, see OneWireless
documentation.
Parameter Description
Alarm Test Select an alarm level to test - High high, High, Low, or Low low - and select OK. The
SmartRadar performs an Alarm test command.
For detail settings, see 7.4.5.2.4.6.
Alarm Hysteresis Specify the alarm hysteresis setting.
For detail settings, see 7.4.5.2.4.6.
Parameter Description
Alarm Test Select an alarm level to test - High high, High, Low, or Low low - and select OK. The
SmartRadar performs an Alarm test command.
For detail settings, see 7.4.5.2.4.6.
Alarm Hysteresis Specify the alarm hysteresis setting.
For detail settings, see 7.4.5.2.4.6.
Ullage Level Scale:
- EU at 100% Not used in the SmartRadar FlexLine.
- EU at 0% Not used in the SmartRadar FlexLine.
- Units Index Select the required engineering unit from the list of available units. (level units for the
level TB, and temperature units for the temperature TB).
Note: For supported units, see 7.4.5.2.8.
- Decimal Not used in the SmartRadar FlexLine.
Parameter Description
Rate of Change Scale:
- EU at 100% Not used in the SmartRadar FlexLine.
- EU at 0% Not used in the SmartRadar FlexLine.
- Units Index Select the required engineering unit from the list of available units. (level units for the
level TB, and temperature units for the temperature TB).
Note: For supported units, see 7.4.5.2.8.
- Decimal Not used in the SmartRadar FlexLine
Example
Configurable Transducer block 1 could be programmed to represent
the radar level from the CAN-XBAND. Then the PV of this tranducer
block represents the PV of the radar level function, the Innage value.
The SV of this transducer block represents the SV of the radar level
function, the Ullage level.
The current firmware version does have some limitations on what can
be programmed in these transducer blocks.
• Configurable Transducer block 1 can only represent Levels. This is
valid for both the PV and the SV.
• Configurable Transducer block 2 can only represent Temperatures.
This is valid for both the PV as the SV.
• Configurable Transducer block 3 can only represent either pressure
or Density. This is valid for both the PV and the SV.
• Configurable Transducer block 4 can represent parameters with
variable dimensional units. The following parameters are supported:
Level, Temperature, Pressure, Density, Current, or NO UNIT. This is
valid for both the PV and the SV.
In wireless builder these limitations must be taken into account when
changing the units index, for both the PV as the SV. If you select a
dimensional unit that is not supported by the Transducer block then an
error message appears.
The Units Index for the PV is available on the Ranges tab.
The Units Index for the SV is availabke on the Other tab. This tab has a
different layout than in a standard transducer block, and is described
below.
Parameter Description
Alarm Test Select an alarm level to test - High high, High, Low, or Low low - and select OK. The
SmartRadar performs an Alarm test command.
For detail settings, see 7.4.5.2.4.6.
Alarm Hysteresis Specify the alarm hysteresis setting.
For detail settings, see 7.4.5.2.4.6.
Secondary Variable Specifies the secondary variable of this transducer block. This Secondary Variable
equals the Secondary Value (SV) of the assigned FlexConn function.
- EU at 100% Not used in the SmartRadar FlexLine.
- EU at 0% Not used in the SmartRadar FlexLine.
Parameter Description
- Units Index Select the required engineering unit from the list of available units. (level units for the
level TB, and temperature units for the temperature TB).
The temperature details can be found on the Other tab. This tab has a
different layout than it has in a standard transducer block. It is described
below.
Parameter Description
Alarm Test Select an alarm level to test - High high, High, Low, or Low low - and select OK. The
SmartRadar performs an Alarm test command.
For detail settings, see 7.4.5.2.4.6.
Alarm Hysteresis Specify the alarm hysteresis setting.
For detail settings, see 7.4.5.2.4.6.
Average Vapour temperature Specifies the average Vapour temperature
EU at 100% (avg temp scale) Not used in the SmartRadar FlexLine.
EU at 0% Not used in the SmartRadar FlexLine.
Parameter Description
Units Index Select the required engineering unit from the list of available units. (level units for the
level TB, and temperature units for the temperature TB).
Parameter Description
Name Specify the name of the transducer block.
Parameter Description
Associated Device Specifies the device that contains the transducer block you are editing.
The device name is set during commissioning with Wireless Builder and is stored in
the TAG descriptor entity.
Actual Mode Specify the actual operation mode of the transducer block. This may differ from the
normal mode, for example if the device is Out of Service.
Normal Mode Specify the mode that the transducer block should be in normal situations.
Permitted Mode Select the permitted modes for the transducer block.
Binary Output Variable Select this option to control the relay. This field has no function if the relay itself is not
programmed to be a remote controlled relay.
Binary Read back value Select the read-back value to represent the actual position of the relay.
Parameter Description
Stale Lim Specify the publication data stale limit. For more details, see OneWireless
documentation.
Parameter Description
Period Select the publication time to determine the primary variable of this transducer block.
This can be 1, 5, 10, or 30 seconds. For more details, see OneWireless
documentation.
Example
To link a configurable transducer block to the Radar Level of
the TII-XR, the following settings need to be configured:
[Board ID] = 5
[Board instance] = 0
[Function instance] = 1
[Unit type] = 1
7.5.1 Introduction
The Host Communication Instrument OneWireless (HCI-1WL) board is
a communication module for the instrument (gauge).
Radio board
F4A09-0011
FIGURE 7-6 The HCI-1WL single slot assembly
7.5.3.1 Introduction
7.5.3.3 Authentication
1. Ensure the OneWireless Network is operational and at least 1 multi-
node configured as gateway.
2. Provision a SmartRadar FlexLine field device using the SD card to
authenticate the keys from the WDM.
3. Insert the SD card into the memory card slot of the HCI-1WL device.
4. Make sure to close the device if it is installed in an explosion
hazardous area.
5. Switch on the device
The device is now automatically join the OneWireless network.
You can follow the authentication/joining process by navigating to the
correct page on the SmartView, see 7.5.7.1. Or by using Engauge, see
7.5.8.1, if there is also a wired connection available.
If the message [NOREDUN] or [CONNECT] does NOT become visible, the
authentication failed.
* If authentication failed, verify that the wireless network is operating
correctly, and try again with a new security key.
* Go to the HCI-1WL
* Select [Board] and issue the [Restore Default] command.
7.5.5.1 Introduction
7.5.5.2.1 Introduction
To configure a channel, you must first add the transducer blocks to this
field device.
3. Click Apply.
To add channel to publication group
1. On the Property Panel, expand Input Publication panel.
2. In the Channel drop-down list, click the channel for which data publi-
cation needs to be enabled.
3. Click Apply.
To activate the channel
The Field Device Summary displays the general details of the field
device.
For more information regarding the details to configure the tag name
and description, refer to the "Click Reset Statistics to reset all the
ENRAF interface statistics." section.
Configure the Mode and Scale entities for the SmartRadar FlexLine
field device channel.
For more information regarding the configuration of the mode and scale
entities, refer to the "Configure Mode and Scale" section.
The publication data for input and output field devices can be configured
using the Input Publication panel in the Property Panel. Depending on
the device type, a field device can have an Input Publication panel.
This is determined by the DD file for the field device.
For more information regarding the configuration of the Input publication
and Output publication entities, refer to the "Configure publication rate"
section.
Water level transducer blocks can be used to publish water level data
measurements from FII-VT board.
The water level transducer block publishes water levels as PV and
ullage level as SV.
Example
Configurable Transducer block 1 is programmed to represent the
radar level from the CAN-XBAND. Then the PV of this tranducer block
represents the PV of the radar level function, the Innage value. The
SV of this transducer block represents the SV of the radar level func-
tion, the Ullage level.
Parameter Description
Actual/Target Specifies the actual operation mode of the transducer block. This may differ from the
normal mode, for example if the device is Out of Service.
Normal Specifies the mode the transducer block should be in normal situations.
Permitted Mode Specifies the permitted modes for the transducer block which can be selected.
Output Variable Specifies the value to control the relay. This field has no function if the relay itself is not
programmed to be a remote controlled relay.
Readback Value Specifies the read-back value that represents the actual position of the relay.
Parameter Description
Average Vapour Temperature Specifies the average Vapour temperature.
Average Ambient temperature Specifies the average ambient temperature
Lowest element Offset Specifies the offset of the lowest temperature element relative to the bottom of the
tank.
Number of elements Specifies number of installed temperature elements.
Parameter Description
MRT or RTD element type Specifies the type of installed temperature element.
Example
To link a configurable transducer block to the Radar Level of
the TII-XR, the following settings need to be configured:
[Board ID] = 5
[Board instance] = 0
[Function instance] = 1
[Unit type] = 1
7.5.7.1 Introduction
< >
<
<
MAIN
MENU SELECT
Parameter Description
PRSSI Primary RSSI = Signal strength indicator for primary wireless connection
SRSSI Secondary RSSI = Signal strength indicator for the redundant wireless connection
SECCONN
CONNECT The device is connected to the OneWireless network via 2 multinodes / gateways.
NOREDUN The device is connected to the OneWireless network via 1 multinode / gateway only.
• SD Status
In the display of the SmartView one out of the following SD card
statuses is visible:
Display Text Description
SDOK SD card with security key present
7.5.8.1 Introduction
Additionally, there are 3 commands that can be given to the radio board
on the HCI-1WL module.
7.5.8.2 Commands
* Select [Read device information], to read the static information from the
radio board.
After executing this command, the static information from the radio
board is read from the radio board and made available in diagnostic
entities. See 7.5.8.3.
* Select [Read dynamic info], to read the dynamic information from the
radio board.
After executing this command, the dynamic information from the radio
board is read from the radio board and made available in diagnostic
entities. See 7.5.8.3.
* Select [Restore Defaults], to remove the security key information from
the radar.
In this way, the radar is disconnect from the wireless network.
CAUTION! With this command all settings on the radio board will
be erased!
• Connection Status
Display Text Description
NO KEY: No security key information available
Insert a memory card with security information.
SECCONN
CONNECT The device is connected to the OneWireless network via 2 multinodes / gateways.
PRSSI Primary RSSI = Signal strength indicator for primary wireless connection
SRSSI Secondary RSSI = Signal strength indicator for the redundant wireless connection
• Additional Items
Parameter Description
Radio diagnostic No explanation.
These diagnostic information items are only relevant if requested by the factory.
Radio software
build number
Radio Network
address
Radio
communication
channel
Wireless Network
ID
Radio mode
Radio IEEE Address
7.5.11.1 Upgrading the SmartRadar FlexLine device firmware using Wireless Device
Manager
7.5.11.2 Upgrading the SmartRadar FlexLine firmware using the Engauge service tool
7.6.1 Introduction
The Transducer Interface Instrument - X-Band Radar (TII-XR) - is the
heart of Enraf’s precision X-band (10 GHz) radar system.
It uses the Frequency Modulated Continuous Wave (FMCW) and
synthesized pulse reflection principle. Using Enhanced Performance
Signal processing (EPS), a smart level detection is possible by filtering
out known obstacles.
F4A07-0007
FIGURE 7-7 The TII-XR board with its Digital Signal Processor
7.6.2.1 General
Radar reference
to roof
Offset
Nozzle
length
Stilling well
F4A07-0008
FIGURE 7-8 Basic commissioning entities
* To get the radar gauge level without any compensations enabled (but
with averaging filter and maximum Safe fill warnings enabled),
program the entities listed in the tables below.
* For a Free space application, program following entities:
Entity Name Explanation
[Tank bottom position] The gauge uses this information to calculate
the level (innage), and to determine the
position of the bottom reflection (part of peak
selection).
[Maximum Safe fill] With this entity the gauge checks if the
programmed upper measuring range is valid
([Minimum measurable distance] at least
<0.5 m> from the antenna).
[Upper reference position] This entity is only used if “ullage” is to be read
from the SmartRadar FlexLine. The ullage is
then calculated from the measured level
(innage) as [Upper reference position]-measured
level.
[Offset to roof] The distance between radar reference and the
tank roof. The gauge uses this information to
determine the position of the echoes caused
by the product and the roof. A positive value
means the roof is below radar reference (see
also FIGURE 7-9).
With the [Accept reference] command, the gauge’s innage or ullage value
is initialized in accordance with the before programmed reference data.
From here the gauge will follow all relative level changes.
This command will only be accepted if the product level is <GOOD>.
This command also puts the SmartRadar FlexLine in accurate level
measurement mode, so this command MUST be given!
The [Accept reference] command can handle either a reference innage or a
reference ullage level. To adjust to an innage level fill in entity [Reference
innage], to adjust to an ullage level fill in entity [Reference ullage]. This level
value is mostly obtained by a manual level measurement (hand dip);
see FIGURE 7-10.
When all values are sent to the SmartRadar FlexLine, the [Accept
reference] command can be given.
When an innage or ullage reference value is not available, the [Accept
reference] command must be given without filling any of these entities.
The SmartRadar FlexLine will now be put into accurate level
measurement mode.
Radar reference
Reference ullage
Tank bottom position
Reference innage
F4A07-0009
FIGURE 7-10 Level check entities
* Set the entities [High high alarm], [High alarm], [Low alarm], [Low low alarm],
and [Alarm hysteresis] to the desired values.
For definitions, see FIGURE 7-11
Alarm Hysteresis
Alarm Hysteresis
Normally, level alarms can be verified when the level reaches the low-
level or high-level alarm set point. The level alarms and, if applicable,
the hard alarm contact coupled to one of the level alarms can be
checked by a “loop check” command. This check is independent from
the actual level value.
The level alarm signalling can be checked in several ways:
• via the communication line to the host
• via the hard alarm output contact
* To perform the alarm test, set [Alarm test enable] to <Enable> and set
[Alarm test] to the required alarm (<High High alarm>, <High Alarm>, <Low
Alarm>, or <Low Low alarm>). [Alarm test] is a parameter command, and
the command will be executed when the parameter is sent to the
gauge. When the command is given, the corresponding alarm will be
set for 1 minute.
7.6.2.6 Compensations
7.6.2.6.1 Filtering
The gauge contains an output filter for both radar innage and radar
ullage. The higher the [Filter averaging constant], the more damping on the
radar innage and radar ullage values. The filter also introduces a lag
between actual ullage/innage and filtered ullage/innage when the
product level is changing. The higher the [Filter averaging constant], the
larger the lag. The minimum [Filter averaging constant] value is 0 (no
filtering), the maximum [Filter averaging constant] value is 99. For the
general filter behavior, see FIGURE 7-12.
Exponentially weighted moving average filter
5.3
5.25
maximum lag [s]
5.2
maximum lag [m]
Ullage [m]
5.15
Ullage
5.1 Average
5.05
4.95
0 20 40 60 80 100 120
Time [s]
If the correction is properly made, both values of each of the three pins
should be equal to each other.
If the product level in the tank is above pin position 1 or below pin
position 3, the correction is extended by the following estimation:
• above pin1: there is an interpolation from the radar zero point (no
correction) to the position of pin 1 (with its correction).
• below pin 3: the correction found at pin 3 is valid for the range below
pin position 3.
At installation of the verification pins, the distances of the pins towards
the flange of the stilling well (L1, L2, and L3) are noted.
The FlexLine measures ullage from the radar zero point.
NOTE: The radar zero point from the FlexLine with an H04
Antenna is located at the flange of the tank
separator. See FIGURE 7-14.
In case the 1” ball valve is used (that is with antenna models H04/N1
and H04/N4), an offset must be added to the distances of the
verification pins.
* The above found verification pin distances must be entered in the
following entities:
Entity name Explanation
Verification pin physical position 1 Physical ullage of verification pin 1 with
respect to radar zero
Verification pin physical position 2 Physical ullage of verification pin 2 with
respect to radar zero
Verification pin physical position 3 Physical ullage of verification pin 3 with
respect to radar zero
reflections from the verification pins are stronger and recognized by the
SmartRadar FlexLine.
or, Field02:
(with TII-XR firmware version A1131 and board descriptor V5)
• By SmartView:
* From the menu select:
• [Commands]
• board [TII-XR] and
• [Product level].
* Then scroll through the list of commands, and select the command
[Disable v-pins].
The status code of the [Primary value] or the [Secondary value] can display
an error (status = <BAD>) or a warning (status = <UNCERTAIN>).
Most common error messages are:
Message Cause
Radar max safe fill not set error [Maximum safe fill] still set to 0 (zero)
Radar max safe fill out of range [Maximum safe fill] value too high
7.7.1 Introduction
The Field Interface Instrument - Digital Output (FII-DO) board has 4
software-controlled, electromechanical relays; see FIGURE 7-20.
relay 1
relay 4
relay 2
F4A07-0001
FIGURE 7-20 The relays and LEDs on the FII-DO board
With jumpers, the relays can individually be set to Normally Open (NO)
or Normally Closed (NC).
In addition to the board’s [Health] LED LE1, the LEDs LE2 and LE3 are
available (see FIGURE 7-20). They can be associated to a relay, by
setting the [LED Association] entity.
JPx0
n.o. n.c.
Ryx_b
Ryx_a
F4A07-0002
FIGURE 7-21 The relays’ hardware jumpers
The <Energized> option is used for fail-safe operation whereas the <De-
Energized> option is used for non-fail-safe operation.
* Set each individual relay to the required configuration, by selecting
the proper entities. See also next overview (fail-safe configuration is
coloured).
Physically
Relay Mode Relay State Physical Result
Configured
Normally Open De-Energized Activated Closed
(NO)
Deactivated Open
Energized Activated Open
Deactivated Closed
Normally Closed De-Energized Activated Open
(NC)
Deactivated Closed
Energized Activated Closed
Deactivated Open
7.7.4.1 PV Monitor
In [PV Monitor] mode, each individual FII-DO-relay unit can monitor the
Primary Value (PV) or Secondary Value (SV) of another board
connected to the CAN bus, and either activate or deactivate the
associated relay if a certain condition is <True> or <False>.
* If [Remote Control] or [Not In Use] mode must be selected, skip to section
7.7.4.2 or 7.7.4.3 respectively.
* From the [Alarm Mode] menu, select [PV Monitor].
* Select [Monitor Board ID], set proper value.
* Select [Monitor Board Instance], set proper value.
* Select [Monitor Function Instance], set proper value.
* Select [Monitor Source], select either <PV> or <SV>, as desired.
The [Monitor Board ID], [Monitor Board Instance], and [Monitor Function Instance]
entities determine the location of the entity to be scanned.
The [Monitor Source] entity determines if either the Primary Value <PV> or
Secondary Value <SV> entity shall be scanned.
The behavior of each individual relay in PV Monitor mode is further
controlled by the [Monitor Mode] and the [Status Behavior] entities; see next.
The Status Behavior entity determines what happens to the relay if the
health of the scanned PV or SV differs from Good. The [Status Behavior]
should be set to one of the following options: <BAD>, <BAD-UNCERTAIN>,
or <Not Used>.
• If the [Status Behavior] is set to <BAD>, and the scanned PV or SV
health is Bad, the respective relay will be activated.
• If the [Status Behavior] is set to <BAD-UNCERTAIN>, and the scanned PV
or SV health is Bad or Uncertain, the respective relay will be
activated.
• If the [Status Behavior] is set to <Not Used>, the respective relay will not
be activated if the scanned PV or SV health is Bad or Uncertain.
* Set the [Status Behavior] entity either to <BAD>, <BAD-UNCERTAIN>, or
<Not Used>.
7.7.5 Commands
The following commands can be given to the FII-DO:
• Activate
• Deactivate
• Acknowledge
7.7.5.1 Activate
7.7.5.2 Deactivate
7.7.5.3 Acknowledge
FII-DO Operation
Mode
Alarm ☛
Mode Activate /
Deactivate
monitoring commands
PV Not Remote
Monitor In Use Control
Remote Local
Mode Mode
Alarm PV/SV
status data
(HH/HA/LA/LL)
F4A07-0004
FIGURE 7-22 FII-DO operation mode survey
7.7.11.1 Introduction
250 VAC / 3 A
relay 3
(ca. 40 VDC / 3 A)
F4A10-0001
FIGURE 7-23 Locations and ratings of the Electro Mechanical Relays on the FII-DO board
• The relays must be set to Normally Open (jumper, see 7.7.3.1) and
Normally Energized (configuration parameter, see 7.7.3.2).
• In a normal situation, the relay contacts are closed.
• Relays 4 are used to increase the availability: if a problem is
detected with the other relays, the redundancy takes care that the
overfill protection function will work (see also FIGURE 7-24).
• The relays typically can stop a pump or close a valve that is used
filling a storage tank. See FIGURE 7-24.
• Overfill safety analysis, including diagnostic tests is done every
second.
• The 2 FII-DO boards are continuously checking each other for a
correct functioning. This is done every second. In case of
malfunction, 2 retries are executed before the status is definitely
determined.
• The radar scans the overfill protection status every second and will
react accordingly.
• Both board contacts are always opened if one out of the following
events occurs:
Level = 0 (product level >= threshold, product level TV = BAD/
UNCERTAIN, TII-XR board does not respond)
Voltage = 0 (one of more board voltages out of range)
Board diagnostic = 0 (board status = BAD / UNCERTAIN)
Board diagnostic of counter part (redundant board) = 0 (board
status = BAD / UNCERTAIN)
Counter part (redundant board) communication = 0 (other
relay board does not respond)
85 - 240 VAC, 3A
250 VAC, 3A
PSX
(ca. 40 VDC, 3A)
power
49
FII-DO 1 TII-XR
application-
controlled
R3 R4 ART2A
product
level
diagnostics
FII-DO 2
R3 R4
overfill threshold
HH
product level
48
OR
LL
underfill threshold
pump valve
F4A10-0002
FIGURE 7-24 Overfill protection application using 2 FII-DO boards
H = Healthy
1 2 3 4 5 6 7 8 9 10 11 12 13 14
F = Fail
? = Warning, reduced accuracy
- = valid
FII-DO 1 FII-DO 2 TII-XR
Overfill Protection Overfill Protection level status GPU protocol
status status
O O F
O H F
O W F
W O F
W H ?
W W ?
H O F
H H -
H W ?
no comms X F
X no comms F
FII-DO 1 FII-DO 2
49 Ofp_b
14 15 16 17 14 15 16 17
CN2 (R1 + R2)
19 Ry3_b 21 Ry4_b
18 19 20 21 18 19 20 21
R3 R4
CN3 FII-DO 1 Ry4_a
CN3 (R3 + R4)
18 Ry3_a 20
19 Ry3_b 21 Ry4_b
CN3 FII-DO 2
R3 R4
18 Ry3_a 20 Ry4_a
48 Ofp_a
49 Ofp_b 48 Ofp_a
* Make sure all jumpers are set to Normally Open (N.O.). See 7.7.3.1.
* Set the [Board Instance] entity of each FII-DO board to a different value
(e.g. 0 and 1).
The boards are redundant and share the same board ID, so to be
able to address the board uniquely by the internal (CAN-bus) or
external FlexConn protocol, the board instance must be different to
distinguish the boards from each other.
* Set the [Counterpart Board Instance] entity of each FII-DO board to the
[Board instance] of the counterpart FII-DO board (redundant board).
* Set the [Relay Mode] entity of R3 and R4 relay to <Normally Energized> for
both FII-DO boards.
* Set the [Alarm Mode] entity of R3 and R4 relay to <PV Monitoring> for
both FII-DO boards.
* Set the [Monitor Mode] entity of R3 and R4 relay to <Local> for both FII-
DO boards.
* Set the [Threshold] entity and [Hysteresis] entity of R3 and R4 relay to
the application-specific desired values, for both FII-DO boards iden-
tically.
* For overfill protection, configure the [Threshold] entity above the HA
and HH setting of the TII-XR board. Entities [High alarm] and [High high
alarm].
* For underfill protection,configure the [Threshold] entity below the LA
and LL setting of the TII-XR board. Entities [Low alarm] and [Low low
alarm].
* For overfill protection, configure the [Threshold Mode] entity of R3 and
R4 relay to <Treat as HA> for both FII-DO boards.
The threshold will now be approached as high alarm above [High
alarm] and [High high alarm], with the relevant hystresis behaviour.
* For underfill protection, configure the [Threshold Mode] entity of R3 and
R4 relay to <Treat as LA> for both FII-DO boards.
The threshold will now be approached as low alarm below [Low alarm]
and [Low low alarm], with the relevant hysteresis behaviour.
* Set the other relevant entities:
The [Overfill Protection Status] entity shows the Overfill Protection Status of
each FII-DO board.
<H> = Healthy
<W> = Gauge alarm (Warning)
<O> = Overfill alarm
With the [Safety shut down timer] entity, the user can set the time that a safe
shutdown will be forced when only an error or failure in one relay chain
is detected. Default value: <0>: Safety Shutdown Timer DISABLED.
7.7.11.7.2 TII-XR
7.8.1 Introduction
The Field Interface Instrument - SmartView (FII-SMV) board is a module
that communicates with SmartView.
< >
<
<
MAIN
F4A07-0013
FIGURE 7-25 The FII-SMV board with the SmartView display
At request from SmartView the FII-SMV board prepares data sets for it.
The requests from SmartView depend on the actual screen at the time.
The communication between the FII-SMV and SmartView uses an own
protocol on an RS-485 physical layer.
The SmartView display can be delivered in 3 versions, each version
having its own specific address:
• Portable SmartView (address 1)
• SmartView fixed on the instrument (address 2)
• SmartView as a tank-side indicator (address 3)
The FII-SMV board continuously scans all addresses, and only the one
with the lowest address will be served.
7.8.3 Reading the SmartRadar FlexLine field device information from the
SmartView
To read the SmartRadar FlexLine field device information from the
SmartView
1. On SmartView, press the UP ARROW and DOWN ARROW simulta-
neously (MENU push buttons) to view the menu items on the display.
2. On the display, scroll to the commands item using the MENU
buttons.
3. Press the LEFT ARROW and RIGHT ARROW (SELECT push
buttons) simultaneously. You are prompted to enter the password.
The default password for SmartView is AAAAAA.
4. Use the MENU push buttons to enter the password and then press
the SELECT push buttons. The list of commands appears.
5. Scroll to select the CAN-1WL FlexConn board name and then press
the SELECT push buttons.
6. Scroll to select board and then press the SELECT push buttons.
7. Scroll to select Read Dev Param then press the SELECT push
buttons.
8. On the display, scroll to the commissioning item using the MENU
buttons.
9. Scroll to select the CAN-1WL FlexConn board name and then press
the SELECT push buttons.
The details available on the SmartView are as follows:
Board Serial No
Network Address
Device revision
CAN-1WL Build
Tx Power Level
Radio Mode
SD Card Status
Key Tx Status
Radio Diag1
Radio Diag2
Device Diag1
Device Diag2
7.9 Pressure & Density Measurement and Other HART Inputs (FCI-HT)
7.9.1 Introduction
The Field Communication Instrument - HART (FCI-HT) board is a
HART®1 master module that enables hybrid-signal (both analog +
digital) communication between the FlexConn instrument and a HART
sensor.
LE3 LE2
LE1
planar
transformer
F4A07-0014
FIGURE 7-26 The FCI-HT board
4 mA
Time
F4A07-0015
FIGURE 7-27 The analog and digital signals within the HART® communication
Product
Pressure
P1
HART-Bus
Vapour
VITO LEVEL
Pressure
P3
Water Product
Level Level
TII-XR or
FCI-HT FII-VT
X-Band radar
CAN-Bus
HART-Bus
Product
Pressure VITO LEVEL
P1
Water Product
Level Level
TII-XR or
FCI-HT FII-VT
X-Band radar
CAN-Bus
FIGURE 7-29 Floating-roof or free-venting tank HIMS density measurement system diagram
Example 2
2 HART density devices and 1 distance device can be connected.
• density device 1 allocated to Function 6
• density device 2 allocated to Function 7
• the distance device allocated to Function 3
Generic
5
HART
Generic
4
HART
Generic
3
HART
Generic
2
HART
HART-Bus
Generic
1
HART
FCI-HT
CAN-Bus
Generic
1
HART
FCI-HT
CAN-Bus
7.9.3.1 General
7.9.3.2 P1 Pressure
The correction factor stored in the [P1 PV offset] entity is then subtracted
from the filtered value. If the [P1 PV offset] entity = 0 no offset is applied.
Depending on the [PV selected type] entity, the P1 pressure can be
displayed as either absolute pressure or relative pressure.
7.9.3.3 P3 Pressure
The software analyses the status of these 4 (3) inputs, to determine the
value and status of the [HIMS Density PV].
If the HIMS Density PV status is <Good Actual>, the HIMS Density PV
value is also stored in memory in the [Last Valid Density] entity, to allow
recovery from a power-down situation when a HIMS Density PV value is
not available.
If any of the 4 input statuses are bad, the software will check for a
[Manual Product Density] entity value to be entered. If a [Manual Product
Density] entity value is entered, this value will be used for the HIMS
Density PV. If no [Manual Product Density] entity value is entered, the
software will check if a [Last Valid Product Density] entity value was stored. If
a [Last Valid Product Density] entity value was stored, this value will be used
for the HIMS Density PV. If no [Manual Product Density] or [Last Valid Product
Density] entity value is found, an error will be reported.
When calculating HIMS Density, the software will check for a negative
density value. If the value is negative, the same manual or last-valid
mechanism is used as described before. If the value is positive, HIMS
Density is calculated.
When calculating HIMS Density, in order to achieve a valid result, the
software will also check if the product level is above the [Minimum HIMS
Level] entity value. If this condition is <True>, HIMS Density is calculated.
If the product level is below the [Minimum HIMS Level] entity value, the
same manual or last valid mechanism is used as described before.
When calculating HIMS Density, if the [Water Level Correction] entity is
<Enabled>, the software will check if the scanned water level <= [Distance
P1 to Zero Level]. If this is <True>, the HIMS Density is calculated. If the
water level > [Distance P1 to Zero Level], the same manual or last valid
mechanism is used as described before. If [Water Level Correction] entity is
<Disabled>, the software will not check the scanned water level.
HART Unit
Sensor Type Accepted HART Units Abbreviation
Code
Pressure Pounds per square inch psi 6
Pascal Pa 11
Kilo Pascal kPa 12
HART Unit
Sensor Type Accepted HART Units Abbreviation
Code
Temperature Degrees Celsius °C 32
Degrees Fahrenheit °F 33
Distance Feet ft 44
Meters m 45
Inches in 47
3
Density Kilograms per cubic meter kg/m 92
3
Pounds per cubic foot lb/ft 94
Degrees API API 104
Once a device has been allocated to a function, the HART PV, SV, and
TV are translated into the FlexConn function’s PV, SV, and TV.
The required sensor value of the generic HART device may not be in
the HART PV but it is translated into the FlexConn PV.
Example:
FlexConn PV
Accepted HART Units Abbreviation Abbreviation
Unit Translation
Pounds per square inch psi Pascal Pa
Pascal Pa
Kilo Pascal kPa
Degrees Celsius °C Celsius °C
Degrees Fahrenheit °F
Feet ft Meters m
Meters m
Inches in
Kilograms per cubic meter kg/m3 Kilograms per kg/m3
cubic meter
Pounds per cubic foot lb/ft3
Degrees API API
TABLE 6-9 Generic HART device units into FlexConn PV unit translation
Function Function
Function Allocation Function Type
Category Sub-type
Function 1 P1 Pressure Sensor (1) Product pressure (5) (6)
Function 2 P3 Pressure Sensor (1) Vapour pressure (13) (7)
Function 3 Distance Sensor (1) HART transmitter (12) (16)
Function Function
Function Allocation Function Type
Category Sub-type
Function 4 Temperature Sensor (1) HART transmitter (12) (16)
Function 5 Pressure Sensor (1) HART transmitter (12) (16)
Function 6 Density Sensor (1) HART transmitter (12) (16)
Function 7 Other Sensor (1) HART transmitter (12) (16)
Function 8 HIMS Density Sensor (1) Product density (6) (8)
The function type entity for Functions 3 through 7 can be changed from
the default value <HART transmitter> to provide more information about the
sensor, by setting the [User function type] entity and then resetting the FCI-
HT board.
The possible values are detailed in TABLE 6-11.
Functions 1 through 8 have fixed values for [PV Unit Type] and [Function
Identification] entities, as detailed in TABLE 6-12.
Function
Function Allocation PV Unit Type
Identification
Function 1 P1 Pressure UNIT_TYPE_PRESSURE <P1 Pressure>
Function 2 P3 Pressure UNIT_TYPE_PRESSURE <P3 Pressure>
Function 3 Distance UNIT_TYPE_LENGTH <Distance>
Function 4 Temperature UNIT_TYPE_TEMPERATURE <Temperature>
Function 5 Pressure UNIT_TYPE_PRESSURE <Pressure>
Function 6 Density UNIT_TYPE_DENSITY <Density>
Function 7 Other UNIT_TYPE_UNDEFINED <Other Units>
Function 8 HIMS Density UNIT_TYPE_DENSITY <HIMS Density>
PV
PV Unit Display Unit Displayed
Selected Range
Type Type Units
Unit
Other Milli <m ...> 1 -
(none) <-> 2 -
Kilo <k ...> 3 -
Mega <M ...> 4 -
P1 Pressure
HIMS
Sensor P1 Ambient Air Pressure and P1 Installed Commissioned
Density
Detected
<Enabled> N/A [P1 ambient air pressure] <default> <True>
AND
[P1 installed] = <enable>
[P1 ambient air pressure] = <default> <False>
OR
[P1 installed]= <disable>
P1 Pressure
HIMS
Sensor P1 Ambient Air Pressure and P1 Installed Commissioned
Density
Detected
<Disabled> Yes [P1 ambient air pressure] <default> <True>
AND
[P1 installed] = <enable>
[P1 ambient air pressure] = <default> <False>
OR
[P1 installed] = <disable>
No N/A <True>
P3 Pressure
HIMS
Sensor P3 Installed P3 Ambient Air Pressure Commissioned
Density
Detected
<Enabled> Yes <Enable> [P3 ambient air pressure] <True>
<default>
[P3 ambient air pressure] <False>
= <default>
<Disable> N/A <False>
No <Enable> N/A <False>
<Disable> <True>
<Disabled> Yes <Enable> [P3 ambient air pressure] <True>
<default>
<Disable> [P3 ambient air pressure] <False>
<default>
N/A [P3 ambient air pressure] <False>
= <default>
No N/A N/A <True>
HART Sensor
Function User Function Type Commissioned
Detected
3 Yes = <Product level> OR <Water level> <True>
<Product level> OR <Water level> <False>
No N/A <True>
4 Yes = <Product temp.> OR <Vapour temp.> <True>
<Product temp.> OR <Vapour temp.> <False>
No N/A <True>
5 N/A N/A <True>
6 N/A N/A <True>
7 N/A N/A <True>
Terminal
Name Function
Number
24 V_Loop HART Bus power
25 GND_Loop HART Bus ground
LED
Function
Number
LE2 HART data Transmit
LE3 HART data Receive
7.10.1 Introduction
The Host Communication Interface – HART Analog Output (HCI-HAO)
is a HART® slave module which communicates with the associated
HART master over the HART bus.
LE3 LE2
LE1
planar
transformer
F4A09-0005
FIGURE 7-33 The HCI-HAO board
4 mA
Time
F4A07-0015
FIGURE 7-34 The analog and digital signals within the HART® communication
7.10.5.2 Commissioning
Function
Name Explanation Default Value Function
Part
[PV Link board ID] Board ID of Other FlexConn <0> Board Board Specific
to be linked as PV to HCI-
HAO
[PV Link board instance] Board Instance of the linked <0>
PV board
[PV Link function instance] Function Instance of the <0>
linked PV board
[PV Link Sensor Value]* Primary or secondary <PV_LINK>
variable of linked card can
be assigned to this
Function
Name Explanation Default Value Function
Part
[HART PV unit code] Unit code for linked PV <UNIT_CODE_UNKNOWN> Function 1 Communication
(HART
[HART Upper Transducer Upper transducer limit for <0>
communication)
Limit] connected sensor of linked
PV board
[HART Lower Lower transducer limit for <0>
Transducer Limit] connected sensor of linked
PV board
[Polling Address] Polling address of the <0>
device, which is used for
poll-based addressing
[Transducer Serial Transducer serial number <123>
Number] of connected sensor of
linked PV board
[Upper Range Value] Upper range value for PV. <0> Function 2 Sensor
This value is used to (Analog Output)
calculate the analog output
current.
[Analog Output at 4mA] Calibration reading when <0>
[Calibrate at 4 mA] command
is given
[Analog Output at 18 Calibration reading when <0>
mA] [Calibrate at 18 mA] command
is given
[Lower Range Value] Lower range value for PV. <0>
This value is used to
calculate the analog output
current.
[Analog Burnout Value] Analog burnout value in <3.6mA>
case of malfunctioning
device
All the entities in the above table would be initialized to their default
values after [init novram] command is given. All the entities should have
their proper values so as to make the respective Function and Board
health to <GOOD> status.
The [Analog Output at 4 mA] and [Analog Output at 18 mA] fields should be
entered after giving proper calibration commands (for more details, see
7.10.4).
Function
Name Explanation Default Value Function
Part
[SV Link board ID] Board ID of Other FlexConn <0> Board Board Specific
which is linked as SV to
HCI-HAO
[SV Link board instance] Board Instance of the linked <0>
SV board
[SV Link function instance] Function Instance of the <0>
linked SV board
[TV Link board ID] Board ID of Other FlexConn <0>
which is linked as TV to
HCI-HAO
[TV Link board instance] Board Instance of the linked <0>
TV board
[TV Link function Function Instance of the <0>
instance] linked TV board
[QV Link board ID] Board ID of Other FlexConn <0>
which is linked as QV to
HCI-HAO
[QV Link board Board Instance of the linked <0>
instance] QV board
[QV Link function Function Instance of the <0>
instance] linked QV board
[Linked Primary Value] PV / SV value of linked PV <0>
board in the set unit code
[Linked Secondary PV value of linked SV <0>
Value] board in the set unit code
[Linked Tertiary Value] PV value of linked TV board <0>
in the set unit code
[Linked Quarternary PV value of linked QV <0>
Value] board in the set unit code
Function
Name Explanation Default Value Function
Part
[HART SV unit code] Unit code for linked SV <UNIT_CODE_UNKNOWN> Function 1 Communication
(HART
[HART TV unit code] Unit code for linked TV <UNIT_CODE_UNKNOWN>
communication)
[HART QV unit code] Unit code for linked QV <UNIT_CODE_UNKNOWN>
[Configuration changed Increments every time the <0>
Counter] configuration is changed
[Device ID] Same as Enraf Serial
number. This is a unique
number to every board.
[Device Type] Device type registered with <127>
the HART Communication
Foundation
[Manufacturer ID Number] Manufacturer ID registered <148>
with the HART
Communication Foundation
[Number of Preambles] Number of preambles <7>
required for a request from
the HART master
[Number of Response Number of preambles in the <7>
Preambles] HCI-HAO response stream
[Fixed Current Value] Fixed analog output current <0> Function 2 Sensor
set by HART command 40 (Analog Output)
[Loop Current Mode] If HART mode selected is <Enabled>
<Standard 4-20mA>, then it is
enabled.
If HART mode selected is
<Fixed 4-20mA>, then it is
disabled.
[Percentage of Range] Percentage of current PV <0>
with respect to the limits set
The following are typical jumper settings done on the HCI-HAO board.
Jumper Connection Default Default
Position Description
Number Details Position Connections
JP1 ON Short 2 & 3 W&M Entity Protection OFF Short 1 & 2
JP2 ON Short 2 & 3 Password Read Protection OFF Short 1 & 2
JP3 ON Short 2 & 3 Write Protection All Entities OFF Short 1 & 2
JP4 ON Short 2 & 3 Free OFF Short 1 & 2
JP5 ON Short 2 & 3 Free OFF Short 1 & 2
JP6 ON Short 2 & 3 CAN termination 120E resistor OFF Short 1 & 2
JP7 & JP8 A Short 1 & 2 Active mode for Analog Output A Short 1 & 2
JP7 & JP8 P Short 2 & 3 Passive mode for Analog Output
t.b.d.
LED
Function
Number
LE2 HART data Transmit
LE3 HART data Receive
7.11.1 Introduction
The Field Interface Instrument - VITO1 (FII-VT) board is a VITO-data
processor module, which calculates average product- and Vapour
temperatures, and optionally a water level.
LE3 LE2
LE1
planar
transformer
F4A07-0016
FIGURE 7-35 The FII-VT board with its planar transformer
By using the HART® protocol (see also 7.9.1), the FII-VT module can be
connected to one VITO-interface which in turn is connected to a probe
for product temperature, Vapour temperature, water level, or a
combination of these.
The FII-VT board has a planar transformer for galvanic isolation from
the HART bus. See FIGURE 7-35.
LED LE1 is the board’s [Health] LED. LEDs LE2 and LE3 will be flashing
to indicate activity on the HART bus. LE2 indicates data is being
transmitted (Tx), LE3 indicates data is being received (Rx).
7.11.3 Commissioning
762 VITO MTT interface 762 VITO MTT interface 762 VITO MTT interface 762 VITO MTT interface
> 700 mm
> 700 mm
> 700 mm
> 700 mm
gas immersion depth
H x H x H x H x
sensor length/14
sensor length/15
sensor length/14
sensor length/15
. . . .
hysteresis
. . . .
sensor length
sensor length
sensor length
sensor length
overall length
overall length
overall length
overall length
x x x x
x x x x
level
x x x x
product immersion depth
hysteresis
x x x x
L x x L x x
lowest element offset
1000 mm
X X
S S
L x L x
65
65
25
25
15
15
Pt 100 reference resistor H Highest spot S Sensitive length = 0.5 / 1.0 / 1.5 / 2.0 m
X Thermocouple (spot) L Lowest spot X Depending on actual Sensitive length,
this length = 1.0 / 1.5 / 2.0 / 2.5 m
F4A07-0017
FIGURE 7-36 Tank and temperature probe data (1)
762 VITO 762 VITO 762 VITO 762 VITO 762 VITO
LT interface LT interface LT interface LT interface LT interface
> 700 mm
> 700 mm
> 700 mm
> 700 mm
H x
H x H x
H x
sensor length/8
sensor length/7
sensor length/8
sensor length/7
. . . .
. . . .
sensor length
sensor length
sensor length
sensor length
overall length
overall length
overall length
overall length
x x x x
x x x x
x x x x
x x x x
x x x x
L L
lowest element offset
1000 mm
1000 mm
1000 mm
sensitive length
L x L x
65
25
F4A07-0018
FIGURE 7-37 Tank and temperature probe data (2)
7.11.3.1.3 Water Level (for 766/768 Combi probes and 765 Water probe only)
RTD Multi
3 spots RTD probe
F4A07-0020
FIGURE 7-38 Resistance Temperature Detector (RTD) elements positions
flying leads
extension tube
anchor eye
F4A07-0019
FIGURE 7-39 Multiple Resistance Thermometer (MRT) parameters
For the entities to be set for the stand-alone 765 VITO water probe (see
FIGURE 7-40), see 7.11.3.3.1.
762 VITO
LT interface
15
F4A07-0042
FIGURE 7-40 The model 765 VITO water probe
7.12.1 Introduction
The Field Interface Instrument - Resistance Temperature Detector (FII-
RTD) board is a sensor module for the instrument (gauge) and
calculates average product- , Vapour- and ambient temperatures.
For accomplishing this, RTDs or MRTs must be directly connected to
the FII-RTD module.
LE3 LE2
LE1
planar
transformer
F4A09-0008
FIGURE 7-41 The FII-RTD board
permanent check checking range if [Temperature range check] is enabled permanent check
spot element spot element range check result = OK spot element spot element
in fail in fail*) in fail*) in fail
(3 retries) (3 retries)
F4A09-0006
FIGURE 7-42 Temperature range check feature
NO EXCLUSION
STATIC EXCLUSION DYNAMIC EXCLUSION
(default)
MPTs > = 2 elements MPTs > = 3 elements
RTDs and MPT
LAST VALID
LAST VALID
USE T2
USE T1
elements fail
T1 T1 calculation
FAIL
FAIL
FAIL
T1 pos < Temperature element T2 pos < Smoothing level < T3 pos
F4A09-0007
FIGURE 7-43 Low element usage settings overview
7.12.4 Commissioning
7.12.4.1 Commissioning Parameters for 1 or 2 RTDs (3- and 4-wire) Temperature Calcula-
tions
[Element weighing factor] Each element can floating point numbers: <1.0>
individually be given a <-x.x .. +x.x>
weighing factor, which is
applicable if the calculation
method is CUSTOM.
[Gauge temperature scale] Determines whether the <IPTS-68> <ITS-90>
IPTS-68 or ITS-90 scale is <ITS-90>
used.
[Low element usage] See FIGURE 7-43 <No Exclusion> <No Exclusion>
<Static Exclusion>
<Dynamic Exclusion>
[Low element behaviour] See FIGURE 7-43 <Temp To Fail> <Temp To Fail>
<Temp To Last Valid>
<Temp Use First Element>
<Temp Use Second Element>
[Temperature element exclude See FIGURE 7-43 floating point number: <1.0>
zone] <-x.x .. +x.x>
For viewing the software version, the Engauge Generic tab can be
viewed; also a Reset board command can be issued here.