3ERVICEæ-ANUAL 3MART2ADARæ&LEX,INE
Contact Information: Head Office - Delft, The Netherlands Honeywell Enraf Delftechpark 39, 2628 XJ Delft PO Box 812, 2600 AV Delft The Netherlands Tel.: +31 (0)15 2701 100 Fax: +31 (0)15 2701 111 E-mail: enraf.helpdesk@honeywell .com Website: http://www.honeywell.com/ps +RQH\ZHOO ,QWHUQDWLRQDO ,QF
Table of Contents CHAPTER 1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1.1 Target Group for this Service Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1.2 Structure of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1.3 Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1.4 Trademarks . . . . . . . . . . . . .
Table of Contents 3.2 FlexConn Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 3.3 Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 3.3.1 Status Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 3.3.1.1 Health Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 3.3.1.
Table of Contents CHAPTER 5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 CHAPTER 6 Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 6.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 6.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 6.4.4 Removing a Radar From the OneWireless Network . . . . . . . . . . . . . . . . . . 6-38 6.4.5 6.4.5.1 6.4.5.2 6.4.5.2.1 6.4.5.2.2 6.4.5.2.3 6.4.5.2.4 6.4.5.2.5 6.4.5.2.6 6.4.5.2.7 6.4.5.2.8 6.4.6 Commissioning the HCI-1WL in the OneWireless Network. . . . . . . . . . . . . 6-39 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39 Transducer Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents 6.6.4.1.1 6.6.4.1.2 6.6.4.2 6.6.4.3 Monitor Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-84 Status Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-84 Remote Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-85 Not in Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-85 6.6.
Table of Contents 6.8.5 Hardware Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-121 6.8.5.1 Terminal Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-121 6.8.5.2 LED Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-121 6.9 HART Analog Outputs (HCI-HAO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-122 6.9.1 Introduction . . . . . . . . . . . . .
General CHAPTER 1 GENERAL 1.1 Target Group for this Service Manual This SmartRadar FlexLine Service Manual is meant for service engineers who are assigned to commission a SmartRadar FlexLine. 1.2 Structure of this Manual Chapter Title Contents Description 1 - GENERAL This introductory manual part 2 - SAFETY Here all safety-related information is housed. All essential and mandatory safety instructions, precautions, and measures are described here.
General 1.4 Trademarks HART® is a registered trademark of the HART Communication Foundation. 1.5 Contact Head Office - Delft, The Netherlands Honeywell Enraf Delftechpark 39, 2628 XJ Delft PO Box 812, 2600 AV Delft The Netherlands Tel.: +31 (0)15 2701 100 Fax: +31 (0)15 2701 111 E-mail: enraf.helpdesk@honeywell .com Website: http://www.honeywell.com/ps 1-2 SmartRadar FlexLine Service Manual Part No.: 4417.
Safety CHAPTER 2 SAFETY 2.1 General The SmartRadar FlexLine is a radar-based level gauge to be 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 generally accepted safety procedures in addition to the safety precautions specified in this document. 2.2 Safety Conventions 2.2.
Safety 2.3.2 EC Declaration of Conformity (for EU) Refer to the EC declaration of conformity shipped with the device. 2.3.3 Control Drawings for FM & CSA Refer to the control drawings shipped with the device. 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.
Safety 2.5 Labels FIGURE 2-1 Identification label with Safety note on the SmartRadar FlexLine 2.6 Personal Safety WARNING! In hazardous areas it is compulsory to use personal protection and safety gear. This can be: Safety helmet, fire-resistive overall, safety shoes, safety glasses, working gloves, LELmeter. Pay attention to the kind of product in the tank. If there is any danger for your health, wear a gas mask and take all necessary precautions.
Safety NOTE: The emitted microwave energy is far below the accepted limits for exposure to the human body. The device was tested in conformity with parts of the following standards and/or publications: - 1999/519/EC COUNCIL RECOMMENDATION of 12 July 1999 - t.b.d. 2.7 Warnings and Cautions 2.7.1 General 2.7.1.1 Opening of the Instrument When it is required to open the instrument in an explosive hazardous environment, take care of the following.
Safety 2.7.1.4.2 Safe Zone WARNING! Avoid generation of static electricity. Make sure no explosive gas mixtures build up in the working area. 2.7.1.5 Required Skills WARNING! The technician must have technical skills to be able to safely install the equipment. The technician also must be trained to work in accordance with the national requirements for electrical equipment in hazardous areas. 2.8 Electrical 2.8.
Safety SmartView: KEMA 07ATEX0011X and IECEX KEM 07.0004 X. SmartConn: KEMA 07ATEX0093 and IECEX KEM 07.0031. Without SmartView: Ex d [ia] T6 Ta: -40 °C - +65 °C. With SmartView: Ex d [ia] ia T4 Ta: -25 °C - +65 °C. FM [including OneWireless option] Without SmartView: Class I DIV I group C,D T6 NEMA 4X Ta: -40 °C - +65 °C. With SmartView: Class I DIV I group C,D T4 NEMA 4X Ta: -25 °C - +65 °C.
Safety CAUTION Anyradiated changesoutput or modifications approved by the party responsible for NOTE: The power ofnot theexpressly device is far below compliance could void the user's authority to operate this equipment. the exposure limits. Nevertheless, use the device in such a manner that the potential for human contact during normal operation is minimal. 2.9.3.3 IC (Industry Canada) Industry Canada Statement: device complies withBRSS-210 of the Industry Canada Rules. Operation is subject 2.9.
Safety 2-8 SmartRadar FlexLine Service Manual Part No.: 4417.
System Architecture CHAPTER 3 SYSTEM ARCHITECTURE 3.1 SmartRadar FlexLine Architecture The SmartRadar FlexLine system is built up from interchangeable hardware modules. These modules consist of uniform printed circuit boards (PCBs), each of them representing a different, unique functionality. Together with the software implemented on these hardware parts, each PCB makes up a so-called FlexConn module.
System Architecture 3.2 FlexConn Modules One of the main characteristics of the SmartRadar FlexLine architecture is its placement flexibility of the FlexConn modules. If desired, any types of modules can be added at any locations. Even placement of 2 identical modules is possible within the SmartRadar FlexLine system. Each FlexConn module has one or more functions. In general, this can be a sensor function, a communication function, or a digital-interface function.
System Architecture Each FlexConn PCB consists of a generic and a specific electronics part. The generic part can be found on any FlexConn modules. The specific electronics part represents an application-specific function.
System Architecture Jumpers: With the jumpers, specific hardware settings can be made: Jumper Number Function 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 a) For an explanation of the entities concept, see 3.3.
System Architecture 3 voltage monitors The output of these monitors, being voltage levels from 3 different FlexConn PCB locations, are used for diagnostics purposes. See FIGURE 3-3. voltage monitor VM3 voltage monitor VM1 voltage monitor VM2 FIGURE 3-3 Locations of the 3 voltage monitors ESF07-0023 1 temperature sensor For the operational PCB, this sensor acts as an input for environmentaltemperature diagnostics.
System Architecture 3.3 Entities Information exchange between the various FlexConn modules takes place by means of the so-called entities. An entity represents a unique information association within the FlexConn architecture. This information may consist of measuring data, status data, commissioning parameters, diagnostics data, or commands.
System Architecture Status Status Category actual manual Good last valid stored instrument Uncertain environment general hardware fail general firmware fail general commissioning fail general calibration fail general operational fail Bad over range (data available!) under range (data available!) no data available un-initialized killed Finally the status code informs about the specific reason why the status is good, uncertain, or bad.
System Architecture 3.3.1.2 Commissioned Entity 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 3.3.
System Architecture 3.4 SmartView Display 3.4.1 General FIGURE 3-4 < < By means of the SmartView most of the FlexConn module settings can be controlled. MAIN < > ESF07-0024 An impression of the SmartView For each sensor and digital I/O function implemented on a FlexConn module, a Primary Value screen becomes available on the SmartView display.
System Architecture Status Category Display Text over range over range under range under range no data available no data un-initialized no init killed killed 3.4.2 Status Entities on SmartView Choosing sub-menu “commissioning” from the main menu, a survey results of all FlexConn modules present in the SmartRadar FlexLine system. Each module is followed by an indication for the “Health” and the “Commissioned” status respectively.
System Architecture 3.4.3 Generic Entities on SmartView From the functions survey screen of the concerning FlexConn module, the generic entity commands or the commissioning entity can be selected via the “board” entry. FII-DO:> board H C I Relay 1 G N Relay 2 G Y Relay 3 U Y nnn Relay 4 B Y 3.4.4 Specific Entities on SmartView Selecting a specific function, for instance, “Relay 2”, gives access to the specific entities for this function.
System Architecture 3.5 Engauge Service Tool The Engauge service tool is a PC application with which all FlexConn module settings can be done as well. By means of the Engauge’s explorer, each FlexConn module of the concerned SmartRadar FlexLine system can individually be selected by double-clicking on the module’s icon. The so-called “board descriptor” is loaded then resulting in a screen with “tab” pages. By selecting these tab pages, all settings of the specific module are accessible. See example below.
System Architecture 3.5.1 Status Entities in Engauge Each board descriptor user interface starts with the tab page “Status”. On this tab page the “Health” and “Commissioning” entities for the whole module and the individual functions are placed. 3.5.2 Generic Entities in Engauge The “Status” tab page is always followed by the “Generic” tab page, on which the general commands and diagnostics entities are placed. 3.5.
System Architecture 3 - 14 SmartRadar FlexLine Service Manual Part No.: 4417.
Service Tools CHAPTER 4 SERVICE TOOLS 4.1 SmartView 4.1.1 General The SmartView is the basic tool with which the user can communicate with the SmartRadar FlexLine modules. As normally open keyboard contacts may be dangerous in an explosion-hazardous environment, the SmartView is built up as a totally shielded explosion-safe tool. 4.1.
Service Tools 4.1.4 SmartView Controls FIGURE 4-2 < < The SmartView has 5 push buttons and an LCD-screen with a backlight that can be switched on/off as desired. By using a menu, most SmartRadar FlexLine control operations can be done. MAIN < > ESF07-0024 The SmartView controls The buttons have the following functions: Button Function within menu ...
Service Tools Button Function within menu ...
Service Tools 4.1.5 SmartView Menu Structure 4.1.5.
Service Tools 4.1.5.1.1 Start-up Screen The SmartView starts up showing: 1. 2. 3. 4. Black test Blank test Enraf logo + software version + tank ID PV screen 4.1.5.1.2 Menu Screen FIGURE 4-3 < < By using the [menu] screen of the SmartView (see FIGURE 4-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 > ESF07-0030 The menu screen Menu Item Part No.: 4417.762_Rev07 < Description [menu] Screen title.
Service Tools Menu Item TABLE 4-1 Description [display settings] Allows you to switch ON/OFF buttons time-out: x Main screen: If no button is pressed within 15 minutes, SmartView switches to PV screen x Standby mode: If no button is pressed within 15 minutes, SmartView switches to standby mode [display test] Performs blank/black test [extra information] The [extra information] screen shows information about a specific function. See also 4.1.5.1.8. The menu items 4.1.5.1.
Service Tools 4.1.5.1.4 Display Contrast Screen FIGURE 4-5 < < The [display contrast] screen (see FIGURE 4-5) displays a horizontal scroll bar. By moving the scroll bar, you can adjust the contrast. Moving to the right immediately increases contrast, moving to the left decreases contrast. MAIN < > ESF07-0032 The display contrast screen 4.1.5.1.5 Display Settings Screen The [display settings] screen allows you to set the buttons time-outs.
Service Tools 4.1.5.1.
Service Tools 4.1.5.1.8 Extra Information Screen The [extra information] mode can be configured to show either the [level & temperature] screen or the [extra information] screen (see FIGURE 4-7). The [extra information] screen shows information about a specific function. The specific functions are described in chapter 6. The [level & temperature] screen (see FIGURE 4-7) shows information about the measured product level and temperature. In this menu mode, it is not possible to change any settings.
Service Tools Data Field Max. Size [characters] Primary Value 9 PV identification 13 Description The measured value, e.g. +025.1277 Quantity name, e.g. x Product level x Product temperature x P1 pressure PV units 5 Quantity unit, e.g.
Service Tools REMARKS: 1. In error situation, the data fields are filled with “#”. 2. SmartView will enter standby mode when the communication with the host is lost. 3. The data fields PV health, PV representation, and PV alarms are only visible if they are applicable. 4.1.5.1.10 Password Screen The [commands] and [commissioning] menus are password-protected. The [password] screen (see FIGURE 4-9) appears when you enter the [commands] or the [commissioning] menu.
Service Tools 4.1.5.1.11 Commands Menu Screens The [commands] menu starts with the [board list] screen FIGURE 4-10 < < (see FIGURE 4-10). You can navigate through the board list by using the up and down buttons. A board can be selected by simultaneously pressing the left + right button. MAIN < > ESF07-0034 The board list screen The [function list] screen (see FIGURE 4-11) shows all available FIGURE 4-11 The function list screen < < functions of the previously selected board.
Service Tools FIGURE 4-12 < < function list by using the up or down button. A command can be selected by simultaneously pressing the left + right button. You can return to the [function list] screen by pressing the left button. MAIN < > ESF07-0035 The command list screen 4.1.5.1.12 Commissioning Menu Screen The [commissioning] menu starts with the [board list] screen < < (see FIGURE 4-13). You can navigate through the board list by using the up or down button.
Service Tools The [function list] screen (see FIGURE 4-14) displays all configurable FIGURE 4-14 < < entities of a function. The actual entity value is visible as well. 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.
Service Tools On selection of an available entity, the [value edit] screen is presented (see FIGURE 4-16). · If an invalid value is entered, the message “value out of range” will be displayed. · If the value is not accepted by the FlexConn module, the message “value not accepted” will be displayed. · You can scroll along the characters by push and hold the up button. · An entity modification is only executed on simultaneously pressing the left + right button. After this, first a range check is done.
Service Tools 4.2 Engauge 4.2.1 Connecting the Engauge Service Tool The Engauge service tool is a PC application with which all FlexConn module settings can be done as well. 4.2.1.1 Wired Connections Situation (FIGURE 4-17) Connecting the serial COM-port of a PC or laptop via an RS-232 (or RS485) transmission line to either a Communication Interface Unit (CIU) or a SmartLink, enables the control of a SmartRadar FlexLine system.
Service Tools 4.2.1.2 OneWireless Situation (FIGURE 4-18) Connecting the serial COM-port of a PC or laptop via an RS-232 (or RS-485) transmission line and a Lantronix server, or directly via an Ethernet connection (Engauge version 2.4 and up only), to a OneWireless gateway enables the control of a OneWireless SmartRadar FlexLine system.
Service Tools 4.2.2 Using Engauge After starting up the Engauge application, first the specific transmission address of the concerned SmartRadar FlexLine system must be set correctly. Also the transmission speed (baudrate) must be set. After this is done, Engauge’s explorer appears, and each FlexConn module of the concerned SmartRadar FlexLine system is visible on the left panel. See FIGURE 4-19.
Service Tools Browsing through the tab pages reveals the same information/ parameter settings as can be found using the SmartView, although in a more user friendly way. However, some settings or commands can only be executed by Engauge. For example, executing an Alarm simulation test is only possible with Engauge. 4.2.3 Some Engauge Screen Examples In the following some Engauge screen samples follow. FIGURE 4-20 Example (2) of an Engauge screen Part No.: 4417.
Service Tools FIGURE 4-21 Example (3) of an Engauge screen 4 - 20 SmartRadar FlexLine Service Manual ESF09-0003 Part No.: 4417.
Service Tools FIGURE 4-22 Example (4) of an Engauge screen Part No.: 4417.
Service Tools 4 - 22 SmartRadar FlexLine Service Manual Part No.: 4417.
Installation CHAPTER 5 INSTALLATION Before starting with commissioning activities, first make sure all mechanical and electrical installation aspects have been completed correctly. For installation, see the Installation Guide for the SmartRadar FlexLine. In case the OneWireless Communication Option (HCI-1WL) is installed, a lightning arrestor is integrated by default.
Installation 5-2 SmartRadar FlexLine Service Manual Part No.: 4417.
Commissioning CHAPTER 6 COMMISSIONING 6.1 General 6.1.1 Introduction This chapter gives an overview of the commissioning information per FlexConn module. NOTE: Not all modules are always present. Commissioning a FlexConn module is done by setting software parameters, the so-called entities (see Chapter 3), to the desired specific values. This can either be done by using Engauge or SmartView (see Chapter 4). 6.1.
Commissioning 6.2 Enraf Fieldbus (HCI-BPM) 6.2.1 Introduction The Host Communication Instrument - Bi-Phase Mark (HCI-BPM) board is a communication module for the instrument (gauge).
Commissioning The HCI-BPM module supports 2 protocols: The Enraf GPU protocol with its records and items (limited); The Enraf FlexConn protocol with its so-called entities. The module can communicate with: 880 CIU prime 858 CIU 780 SmartLink 6.2.2 Commissioning the HCI-BPM For a correct functioning of the HCI-BPM module within an instrument (gauge), the following entities can be set by using either Engauge or SmartView. ☛ By using the following table, check each entity for correctness.
Commissioning Name Value Range Default Value Explanation [Pressure units] (2 digits before separator) (3 digits before separator) The unit in which pressurerelated GPU records and items are shown [Density units] The unit in which densityrelated GPU records and items are shown [Decimal separator] The decimal separator in which GPU-related records and ite
Commissioning 6.3 Enraf GPU-FlexConn / Modbus Protocol (HCI-GPU) 6.3.1 Introduction The Host Communication Instrument - Gauge Processing Unit (HCIGPU) board is a communication module for the instrument (gauge).
Commissioning NOTE: A protocol switch has been implemented as to switch back and forward between the GPU-FlexConn and the Modbus protocol. The physical layers for the communication are RS-232, isolated and non-isolated, and RS-485, isolated. RS-232 is used for direct point-topoint connections whereas RS-485 facilitates a multi-point network with up to 32 drivers and 32 receivers. The HCI-GPU (slave) module can be used in any field devices provided with the FlexConn architecture.
Commissioning 6.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) • Refresh rate of 32 FlexLines on one link = 4.80 sec * (free running host mode: no scan rate setting) Recommended minimum host settings: • Time out >= 65 ms * (assuming time out measurement resets at start of slave message) • Scan rate >= 180 ms * * Note: @ 100 register @ 19K2 baud Part No.: 4417.
Commissioning 6.3.3 Commissioning the HCI-GPU - Modbus Protocol 6.3.3.1 Introduction The Modbus protocol has been developed by Modicon and is used to establish master-slave/client-server communication between intelligent devices. Modbus is a de facto open standard and the most widely used network protocol in the industrial manufacturing environment. There are different flavors of Modbus.
Commissioning A typical message frame is shown below: Start Address Function Data CRC check End T1T2T3T4 8 bits 8 bits n * 8 bits 2 * 8 bits T1T2T3T4 Start: Synchronisation 3.5 character time elapsed. Address: The address field of a message frame contains eight bits. The address must be within the range 1 to 247 (decimal). A master addresses a slave by placing the slave address in the address field of the message.
Commissioning • The register data in the response message is packed as two bytes: Slave address Function 03 Byte count (N) Data CRC check 8 bits 8 bits 8 bits (N) x 8 bits 16 bits • The amount of bytes N is double the amount of requested registers, because each register occupies two bytes. Function code 05 Write single coil Coils are located in the memory range (0)0000 ... (0) FFFFH. The value of a coil can be forced to: FF00H = ON, or 0000H = OFF.
Commissioning A changeover is done by the protocol switch. Protocol switching is bound to the following: Engauge only supports GPU-FlexConn to Modbus switching. Once the HCI-GPU is in Modbus mode, Engauge cannot execute any modifications as Engauge does NOT support Modbus communication. This scenario may be found at a first-time installation or during servicing issues.
Commissioning 6.3.3.4 Commisioning For a correct functioning of the HCI-GPU module within an instrument (gauge), the following entities can be set by using either Engauge or SmartView. ☛ By using the following table, check each entity for correctness.
Commissioning Name Value Range Default Value Explanation [Modbus register address offset] <0x0000..0xEE00> <0> As per Modbus, function code 03 supports 0000 to FFFF register addressing. Considering modbus map starting at 0x0000 and 0x1000 and keeping this constant, the offset address should be (0xFFFF 0x1138 = 0xEEC7) . For Round off number 0xEE00. Offset can be moved any where between 0x0000 to 0xEE00. 0x1138 is total number of registers of both modbus map.
Commissioning Byte order in Modbus registers For data type that is long and float IEEE-754, the 32 bits are devided over two 16-bits registers.
3 4 5 6 WaterLevelStatus 0x0006 40007 char 1 ProductTemp 0x0007 SD40008 long 2 ProductTempStatus 0x0009 40010 char 1 VapRoomTemp 0x000A SD40011 long 2 VapRoomTempStatus 0x000C 40013..16 byte 4 VapRoomPress 0x0010 2 SD40017 long VapRoomPressStatus 0x0012 40019..23 byte 5 ObsDensity 0x0017 SD40024 2 long Interpretation Scaling factor Conversion units No. of registers Data type Modbus Address (dec) Modbus address (hex) Modbus parameter Par.no.
Spot temperature pos. 6 long 2 FAHRENHEIT devide by 100 METRES devide by 10000 FEET devide by 1000 INCHES devide by 100 devide by 100 20 Spot temperature 7 0x0218 SD40537 long 2 CELSIUS 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.
FEET devide by 1000 INCHES devide by 100 devide by 100 36 Spot temperature 15 0x0238 SD40569 long 2 CELSIUS FAHRENHEIT devide by 100 37 Spot temperature 15 pos. 0x023A SD40571 long 2 METRES devide by 10000 38 Spot temperature 16 39 Spot temperature 16 pos.
First Relay Board - Relay 1 Status 0x031B 40796 Integer 1 First Relay Board - Relay 2 0x031C SD40797 long First Relay Board - Relay 2 Status 0x031E 40799 Integer 1 First Relay Board - Relay 3 0x031F SD40800 long First Relay Board - Relay 3 Status 0x0321 40802 Integer 1 First Relay Board - Relay 4 0x0322 SD40803 long First Relay Board - Relay 4 Status 0x0324 40805 Integer 1 Second Relay Board - Relay 1 0x0325 SD40806 long Second Relay Board - Relay 1 Status 0
Commissioning ProductLevel floating 2 point Interpretation Conversion units SD44097 No. of registers 0x1000 Data type Modbus Address (dec) 1 Modbus address (hex) Par.no. Modbus parameter 6.3.3.5.2 Floating Point Format Gauge Data METRES FEET INCHES 2 ProductLevelStatus 0x1002 44099 char 1 ProductLevelAlarms 0x1003 44100 char 1 WaterLevel 0x1004 SD44101 floating 2 point See 6.3.3.6.1 See 6.3.3.6.
floating 2 point CELSIUS 13 Spot temperature 3 pos. 0x120A SD44619 floating 2 point METRES Interpretation SD44617 Conversion units 0x1208 Data type Modbus Address (dec) Spot temperature 3 Modbus parameter 12 Par.no. Modbus address (hex) No. of registers Commissioning INCHES FAHRENHEIT FEET INCHES 14 Spot temperature 4 0x120C SD44621 floating 2 point CELSIUS 15 Spot temperature 4 pos.
Spot temperature 9 floating 2 point Interpretation Conversion units SD44641 No. of registers 0x1220 Data type Modbus Address (dec) 24 Modbus address (hex) Par.no. Modbus parameter Commissioning CELSIUS FAHRENHEIT 25 Spot temperature 9 pos. 0x1222 SD44643 floating 2 point METRES FEET INCHES 26 Spot temperature 10 0x1224 SD44645 floating 2 point CELSIUS FAHRENHEIT 27 Spot temperature 10 pos.
37 Spot temperature 15 pos. 0x123A SD44667 floating 2 point Interpretation Conversion units No. of registers Data type Modbus Address (dec) Modbus address (hex) Modbus parameter Par.no. Commissioning METRES FEET INCHES 38 Spot temperature 16 0x123C SD44669 39 Spot temperature 16 pos.
Hart Input Variable 5 status 47 48 0x1318 44889 Integer 1 First Relay Board - Relay 0x1319 1 SD44890 floating 2 point First Relay Board - Relay 0x131B 1 Status 44892 Integer 1 Interpretation Conversion units No. of registers Data type Modbus Address (dec) Modbus address (hex) Par.no. Modbus parameter Commissioning See 6.3.3.6.9 See 6.3.3.6.
Commissioning 6.3.3.6 Status Information After being requested so by the host, the slave will return the relevant status information. The following tables give the possible received status bytes from the relevant registers, such as product level, product temperature etc. For a listing of ASCII codes, see 6.3.4. 6.3.3.6.1 Product Level This register contains the bit-coded product level status. This status information is coded in such a way that an ASCII code for a character is generated.
Commissioning such a way that an ASCII code for a character is generated. The 8-bits ASCII coded character is placed in the Low byte of the register; the High byte remains empty (zero).
Commissioning Vapour Room Pressure status Meaning 1 bit 0 - P1 exceeds min. / max. trip pressure 1 - P2 exceeds min. / max. trip pressure 2 - P3 exceeds min. / max.
Commissioning Health status code Meaning 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_ELEMEN
Commissioning 6.3.3.6.
Commissioning Health status code Meaning 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 6.3.3.6.10 Relay Part No.: 4417.
Commissioning Health status code Meaning 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 6.3.3.6.
Commissioning Health status code Meaning 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 6.3.3.6.12 Overfill Protection Status For a listing of ASCII codes, see 6.3.4.
Commissioning 6.3.3.7 Modbus Coils The following table lists Modbus commands and their related addresses (coils) and data.
Commissioning of the original request in the function code field of the response. All function codes have a most–significant bit (MSB) of 0 (their values are all below 80 hexadecimal). In an exception response, the FlexLine device sets the MSB of the function code to 1. This makes the function code value in an exception response exactly 80 hexadecimal higher than the value would be for a normal response.
Commissioning 6.3.4 Standard ASCII codes 6 - 34 SmartRadar FlexLine Service Manual Part No.: 4417.
Commissioning 6.4 The OneWireless Communication Option (HCI-1WL) 6.4.1 Introduction The Host Communication Instrument OneWireless (HCI-1WL) board is a communication module for the instrument (gauge). radio module FIGURE 6-4 The HCI-1WL duplex board with flatcable interconnection ESF09-0011 This module consists of 2 boards (see FIGURE 6-4): a standard FlexConn board with a memory-card interface, and an interface board with a standard Honeywell OneWireless Radio board attached.
Commissioning is built as an "open system" to allow all field devices and equipment that are built to the OneWireless standard to be integrated into a system, regardless of the device manufacturer. This interoperability of devices using OneWireless technology is to become an industry standard for automation systems. In the Onewireless network, devices like the Smartradar FlexLine publish their measuring values autonomously at the network.
Commissioning 6.4.3.2 Preparing the Radar Before adding a radar to a one wireless Network, old security information must be removed from the radar. To prevent this from happening by accident, this functionality is only available via the SmartView. To erase the security information: ☛ Go to [Menu] > [Commands] ☛ Enter the password ☛ Go to the HCI-1WL ☛ Select [Board] and issue the [Restore Default] command. 6.4.3.
Commissioning FIGURE 6-5 Sample screen of the Key Server Manager 6.4.4 Removing a Radar From the OneWireless Network To remove a radar from a Onewireless Network, the security key information must be removed from the radar. To prevent this from happening by accident, this functionality is only available via the SmartView. To erase the security key information: ☛ Go to [Menu] > [Commands] ☛ Enter the password ☛ Go to the HCI-1WL ☛ Select [Board] and issue the [Restore Default] command.
Commissioning 6.4.5 Commissioning the HCI-1WL in the OneWireless Network 6.4.5.1 Introduction Once the authentication process is completed, the SmartRadar can be commissioned in the OneWireless network. 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, please refer to the OneWireless Wireless Builder User’s Guide, R120 or later.
Commissioning 6.4.5.2 Transducer Blocks 6.4.5.2.1 Introduction Besides the Radar Level transducer block, up to 16 additional transducer blocks can be added to the device via Wireless Builder. This can easily be done by “drag and drop”. The specific parameters of all available transducer blocks can be set via Wireless Builder. This section describes how to use the Configuration Form to configure the transducer blocks (channels). Please refer to the Configuring Channels chapter in the OneWireless manual.
Commissioning Transducer Block See section Vapour pressure - Vapour temperature - Water level - All Transducer blocks can be loaded for any SmartRadars. However a transducer block will only give valid data when a relevant option is installed in the SmartRadar. So for temperature transducer blocks to become actual available, an FII-RTD or FII-VT must be installed in the SmartRadar, and for the Relay output transducer blocks to work correctly, an FII-DO must be installed etc. 6.4.5.2.
Commissioning 6.4.5.2.4 Wireless Builder Screens 6.4.5.2.4.1 Main Tab This tab contains the general settings of the Transducer Block (TB). Parameter Description Name Here you can specify the name of the transducer block. Associated Device 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 The actual operation mode of the transducer block.
Commissioning Parameter Description Permitted Mode With these check boxes you can select the permitted modes for the transducer block. Process Variable If the transducer block is set to manual mode, you can manually overwrite the parameter (such as level). This is not standard within OneWireless. The manual value entered here will also be available in the FlexConn environment. If the Transducer block is not in Manual mode an error code will be generated after pressing the OK button. 6.4.5.2.4.
Commissioning Parameter Description Decimal Not used in The SmartRadar FlexLine 6.4.5.2.4.3 Alarm Tab This tab contains the various alarm settings (High high, High, Low, and Low low). Parameter Description Alert Disable With this settings it is possible to disable an alarm. Alert Priority With this setting it is possible to define the alert priority. For more information on alert priority, see the Onewireless Documentation. In Alarm This light shows the actual alarm status.
Commissioning NOTE: Having alerts on measured variables is not standard in OneWireless. Be careful using these alarms when the user is also using Experion. As these alarms will be visible as system alarms and NOT as process alarms. 6.4.5.2.4.4 Configuration Tab This tab describes the publication time and time-out settings. Parameter Description Stale Lim Publication data stale limit. For more details, see OneWireless documentation.
Commissioning 6.4.5.2.4.5 Other Tab (1) Via this tab, an alarm test can be initiated. Parameter Description Alarm Test By selecting an alarm level to test - High high, High, Low, or Low low - and pressing OK, the SmartRadar will perform an Alarm test command. For detail settings, see 6.4.5.2.4.6. Alarm Hysteresis This is the alarm hysteresis setting. For detail settings, see 6.4.5.2.4.6. 6 - 46 SmartRadar FlexLine Service Manual Part No.: 4417.
Commissioning 6.4.5.2.4.6 Other Tab (2) The following example screen shows possible detail settings of the Other tab. Parameter Description Alarm Test By selecting an alarm level to test - High high, High, Low, or Low low - and pressing OK, the SmartRadar will perform an Alarm test command. For detail settings, see 6.4.5.2.4.6. Alarm Hysteresis This is the alarm hysteresis setting. For detail settings, see 6.4.5.2.4.6.
Commissioning Parameter Description - Decimal Not used in the SmartRadar FlexLine Rate of Change Scale: - EU at 100% Not used in the SmartRadar FlexLine - EU at 0% Not used in the SmartRadar FlexLine - Units Index In this field you can 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 6.4.5.2.8. - Decimal Not used in the SmartRadar FlexLine 6.4.5.2.
Commissioning The Units Index for the SV can be found on the Other tab. This tab has a different layout than in a standard transducer block, and is described hereafter. Parameter Description Alarm Test By selecting an alarm level to test - High high, High, Low, or Low low - and pressing OK, the SmartRadar will perform an Alarm test command. For detail settings, see 6.4.5.2.4.6. Alarm Hysteresis This is the alarm hysteresis setting. For detail settings, see 6.4.5.2.4.6.
Commissioning Parameter Description - Units Index In this field you can 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: See also limitations described before. Note: For supported units, see 6.4.5.2.8. - Decimal Not used in the SmartRadar FlexLine 6.4.5.2.
Commissioning The temperature details can be found on the Other tab that. This tab has a different layout than it has in a standard transducer block. It is described below. Parameter Description Alarm Test By selecting an alarm level to test - High high, High, Low, or Low low - and pressing OK, the SmartRadar will perform an Alarm test command. For detail settings, see 6.4.5.2.4.6. Alarm Hysteresis This is the alarm hysteresis setting. For detail settings, see 6.4.5.2.4.6.
Commissioning Parameter Description Units Index In this field you can 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 6.4.5.2.8. Decimal Not used in the SmartRadar FlexLine Average Ambient temperature This is the average ambient temperature Lowest element offset Offset of lowest temperature element relative to the bottom of the tank Element position 1...
Commissioning 6.4.5.2.7 Relay Output Transducer Block Settings The Relay output transducer blocks are standard Binary Output transducer blocks. (In contrast to all other transducer blocks, which are Analog Input transducer blocks.) There are 4 relay output blocks, each representing one of the 4 relays that can be installed in the SmartRadar FlexLine. These transducer blocks can be used to remotely control the relays, provided these relays are programmed as remote controllable in Engauge.
Commissioning Parameter Description Actual Mode 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 This is the mode the transducer block should be in, in normal situations. Permitted Mode With these check boxes you can select the permitted modes for the transducer block. Binary Output Variable This field can be used to control the relay.
Commissioning 6.4.5.2.8 Supported Units The SmartRadar Flexline supports the following units: Parameter Supported Units Level and position Meters (m) Millimeters (mm) Inches (in) Feet (ft) Level rate of change Millimeters / second (mm/s) Meters / hour (m/h) Inch / minute (in/min) Feet / minute (ft / minute) Temperature Degrees Celsius (ºC) Degrees Fahrenheit (ºF) Pressure Pascal (Pa) kilo Pascal (kPa) bar psi Density kg / m3 kg / l g / ml lbs / ft3 deg API 6.4.
Commissioning Name Explanation Value Range Default [Board ID] The board ID of the board that contains the function you want to map to the configurable transducer block. Look in the board list which boards are available. <0...255> <0> [Board Instance] The board instance of the board that contains the function you want to map. This is usually 0. Look in the board list to see if any boards are available more than once in the instrument. <0...
Commissioning Name Explanation Value Range Default [Function Instance] This identifies the function which data you want to map to this transducer block. <0...15> <0> [Unit Type] The unit type is necessary to identify in One Wireless. <0...5> <0> units of data: 0 = no unit 1 = level 2 = temperature 3 = pressure 4 = density 5 = current All 4 configurable transducer blocks have the same settings in Engauge.
Commissioning For a correct functioning of the HCI-GPU module in an instrument (gauge), the following entities can be set by using either Engauge or SmartView. ☛ By using the following table, check each entity for correctness. Name Value Range Default Value Explanation [Identification] 8 characters e.g. <--------> Name of a tank or instrument [GPU instrument address] <0..99> <0> The address of this instrument for GPU messages. Note: Each instrument must have a unique GPU address.
Commissioning Name Value Range Default Value Explanation [Pressure units] (2 digits before separator) (3 digits before separator) The unit in which pressurerelated GPU records and items are shown [Density units] The unit in which densityrelated GPU records and items are shown [Decimal separator] The decimal separator in which GPU-related records and ite
Commissioning 6.4.8 Using the SmartView with the OneWireless Communication Option 6.4.8.1 Introduction The SmartView replaces the display that is usually available on OneWireless transmitters. 6.4.8.2 SmartView OneWireless Status Display < < At the Smartview, there is a special OneWireless status display available, called the [extra information] display. See screen below.
Commissioning Signal strength (RSSI = Radio Signal Strength Indicator) The signal strength is shown in dBm. Below -80 to -85 dBm no reliable connection is possible. When there is no redundant wireless connection the secondary RSSI does not show a relevant value. Connection status In the display of the Smartview the following Connection status messages can / will be visible: Display Text Description NO KEY: No security key information available Insert a memory card with security information.
Commissioning 6.4.9.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 6.4.9.3. [Read dynamic info], to read the dynamic information from the radio board.
Commissioning Radio Signal Status Parameter Description TX power level Transmission power level Note: This is an Advanced Setting! Please read section 6.4.10 before changing this setting. 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.
Commissioning 6.4.10 Advanced Settings - Transmission Power Level Professional installers are allowed to change to power settings in situations that an external antenna is used to compensate for long external cables. CAUTION! It is NOT allowed to set the transmission power to a higher level than is allowed by the local authorities. When a radar with an integrated antenna is ordered, the value is set to the correct value in the factory.
Commissioning 6.4.11 Firmware Upgrade You can upgrade the radio firmware via OneWireless Wireless Builder. For more details see the Wireless Builder manual in the chapter “Upgrading Firmware in commissioned device”. NOTE: Only the radio firmware can be upgraded via Wireless Builder. Firmware upgrade of the HCI-1WL board and the other FlexConn boards is done via the normal FlexConn upgrade procedures. Part No.: 4417.
Commissioning 6.5 Product Level Measurement (TII-XR) 6.5.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.
Commissioning For correct measuring results, a number of parameters such as [Tank bottom position], [Upper reference position], and [Offset to roof] must be defined before. In addition, alarm settings and compensation (filtering) constants are to be set. This can be done by using either Engauge or SmartView. 6.5.2.2 Level Start-Up For entity definitions, see FIGURE 6-7 and FIGURE 6-8. Free Space applications Stilling Well applications FIGURE 6-7 Basic commissioning entities Part No.: 4417.
Offset to roof positive radar reference Offset to roof negative Commissioning FIGURE 6-8 ESF07-0011 Definition of [Offset to roof] ☛ 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.
Commissioning Entity Name Explanation [Nozzle length] Needs only to be set if the antenna is installed inside the nozzle. ☛ For a Stilling well 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).
Commissioning Upper reference position Reference ullage Reference innage Tank bottom position Radar reference Tank zero (dipping plate) FIGURE 6-9 ESF07-0009 Level check entities NOTE: This command does not adjust the [Tank bottom position], so this entity should be set manually to approximately the correct value (within ± 0.1 m). ☛ Give the [Accept reference] command. ☛ Make sure the [Accept reference status] is .
Commissioning 6.5.2.4 Alarm Settings ☛ Set the entities [High high alarm], [High alarm], [Low alarm], [Low low alarm], and [Alarm hysteresis] to the desired values. For definitions, see FIGURE 6-10 Maximum safe fill High High alarm High Alarm Alarm Hysteresis Alarm Hysteresis Tank zero Low Alarm Low Low alarm FIGURE 6-10 Alarm and hysteresis definitions ESF07-0012 All above mentioned entities MUST be set as the defaults are extremes (1E+12).
Commissioning 6.5.2.5 Alarm Loop Checking Normally, level alarms can be verified when the level reaches the lowlevel 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.
Commissioning In the table below some filtering figures are given. [Filter averaging constant] Approximate noise reduction factor 50 1.4 0.1 0.1 * dL/s 70 1.8 0.25 0.25 * dL/s 90 3 1 1 * dL/s 95 4.5 2 2 * dL/s 98 7 5.5 5.5 * dL/s 99 10 11 11 * dL/s Maximum lag [s] Maximum lag [distance] 6.5.2.6.2 Verification Pins When a radar level gauge is installed on a pressurized tank, both ISO and API suggest to use so-called verification pins to verify the radar level measurement.
Commissioning corrected) distances with the real pin positions. If the correction is properly made, both values of each of the three pins should be equal to each other. FIGURE 6-12 Ullage correction using the verification pins 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).
Commissioning FIGURE 6-13 Radar zero point and verification pins positions In normal (product measuring) position (see FIGURE 6-14), the E-field (electrical field of the microwave) is located perpendicular to the direction of the verification pins. In this position, the verification pins are less visible to the SmartRadar FlexLine. FIGURE 6-14 Product measuring position In verification pin measuring position (see FIGURE 6-15), the E-field should be in parallel with the verification pin direction.
Commissioning reflections from the verification pins are stronger and recognized by the SmartRadar FlexLine. FIGURE 6-15 Verification pin measuring position To measure the position of the verification pins, the SmartRadar FlexLine must be turned 90 degrees as follows: Release the coupling nut of the SmartRadar FlexLine housing. Lift the SmartRadar FlexLine housing from tank separator. Rotate the SmartRadar FlexLine for 90°. This can only be done in one direction because of the locking pin.
Commissioning • or, Field02: (with TII-XR firmware version A1131 and board descriptor V5) • or, Verification pins: (from TII-XR firmware version A1140 and board descriptor V6) For the SmartView the command is implemented from TII-XR firmware version A1142, and resides under the Command menu as follows: ☛ From the menu select: [Commands] board [TII-XR] and [Product level]. ☛ Then scroll through the list of commands, and select the command [Enable v-pins].
Commissioning [Product level]. ☛ Then scroll through the list of commands, and select the command [Disable v-pins]. Below an example of two reflection diagrams from product measuring mode and verification-pin measuring mode, and an example of the compensation sheet. FIGURE 6-16 Product measuring mode, reflection diagram example FIGURE 6-17 Verification pin measuring mode, reflection diagram example 6 - 78 SmartRadar FlexLine Service Manual Part No.: 4417.
Commissioning FIGURE 6-18 Verification pin compensation, example 6.5.2.7 Errors and Warnings The status code of the [Primary value] or the [Secondary value] can display an error (status = ) or a warning (status = ). 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 6.5.2.
Commissioning 6.5.2.9 Overfill Protection Application For the configuration of the TII-XR within an Overfill protection application, see 6.6.11. 6.6 Relay Contacts (FII-DO) 6.6.1 Introduction The Field Interface Instrument - Digital Output (FII-DO) board has 4 software-controlled, electromechanical relays; see FIGURE 6-19.
Commissioning 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 6-19). They can be associated to a relay, by setting the [LED Association] entity. ☛ For a fail-safe level application, continue with section 6.6.10. 6.6.2 Operation Mode The FII-DO can operate in one of two modes: [Alarm Mode] and [Fallback Mode]. This is controlled by the [Operation Mode] entity.
Commissioning 6.6.3 Relay Configuration 6.6.3.1 Jumper Settings At installation, each individual relay contact was configured as required with the hardware jumpers JPx0, where x = Relay 1 to 4 respectively. See FIGURE 6-20. JPx0 n.o. n.c. Ryx_b Ryx_a FIGURE 6-20 ESF07-0002 The relays’ hardware jumpers NOTE: In the Commissioning stage, no jumper setting can be changed without breaking the compartment screw sealing. 6.6.3.
Commissioning The option is used for fail-safe operation whereas the 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).
Commissioning 6.6.4.1.1 Monitor Mode The [Monitor Mode] entity can either be set to [Remote] or [Local]. If the [Monitor Mode] is set to [Remote], the alarm status of the scanned PV or SV is monitored. The alarm status is compared against the value set in the [Remote Threshold Source] entity. The [Remote Threshold Source] entity can be set to , , , or . Example: If the [Remote Threshold Source] is set to and a High High Alarm occurs, the relay will be activated.
Commissioning NOTE: This behavior takes priority over the [Remote] or [Local] monitoring. For example: If the [Status Behavior] is set to , and the scanned PV or SV health is Bad, the respective relay will be activated regardless of the [Monitor Mode] entity settings. The [Remote] or [Local] option PV or SV checks will then not affect the relay status. 6.6.4.
Commissioning Activate Deactivate Acknowledge 6.6.5.1 Activate The !Activate! command will cause the specified relay to become . This command is only available in [Remote Control] mode; see 6.6.4.2. The !Activate! command behavior is modified by the [Time Setting] entity. If the [Time Setting] entity is set to zero, the relay will stay permanently activated until a !Deactivate! command is given.
Commissioning NOTE: The LEDs do not indicate the physical relay state (coil state or contacts state), as this depends on the software settings and the physical settings (jumper), see 6.6.3. ☛ Set the value of the [LED Association] entity as desired (optional). For an example, see table below. LED Association 1+2 3+4 LED Number Relay Number LE2 1 LE3 2 LE2 3 LE3 4 6.6.
Commissioning 6.6.8 Commissioned Entities ☛ By using the table below, make sure all entities are commissioned. The [Commissioned] entity will display either if the function is commissioned or if the function is not commissioned. To commission the function, the entities must be set in accordance with the table below.
Commissioning 6.6.9 Board Commissioned Entity The [Board Commissioned] entity will display either if all functions are commissioned or if any of the functions are not commissioned. ☛ If the [Board Commissioned] entity displays , check each function parameter again. Use the table from 6.6.8. 6.6.10 Fail-safe Level Application Following steps include all commissioning-aspects settings for the Failsafe level application.
Commissioning FII-DO Operation Mode Energized/ De-Energized Relay Mode Alarm Mode monitoring PV Monitor Status Behavior Remote Mode Alarm status (HH/HA/LA/LL) Fallback Mode ☛ Activate / Deactivate commands Remote Control Not In Use Bad / Bad-Uncertain / Not used Not Restricted Restricted Local Mode PV/SV data FIGURE 6-21 FII-DO operation mode survey 6 - 90 SmartRadar FlexLine Service Manual ESF07-0004 Part No.: 4417.
Commissioning 6.6.11 Overfill Protection Application 6.6.11.1 Introduction Because of some tank storage overfill accidents in the past, there is an increased need for a qualified overfill-protected level measuring system. The SmartRadar FlexLine can be configured such that an adequate overfill protection level is achieved. As such it is qualified as a Safety Instrumented Function (SIF) for overfill protection of storage tanks in the oil and gas industry, to a SIL1 2 level.
Commissioning The relays must be set to Normally Open (jumper, see 6.6.3.1) and Normally Energized (configuration parameter, see 6.6.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 6-23). The relays typically can stop a pump or close a valve that is used filling a storage tank. See FIGURE 6-23.
Commissioning 85 - 240 VAC, 3A 250 VAC, 3A (ca. 40 VDC, 3A) PSX power 49 FII-DO 1 applicationcontrolled R3 TII-XR ART2A R4 FII-DO 2 R3 diagnostics product level R4 overfill threshold HH product level 48 OR LL underfill threshold pump valve product flow storage tank FIGURE 6-23 Overfill protection application using 2 FII-DO boards Part No.: 4417.
Commissioning An individual board relay contact is closed if all following conditions are met: • Level = 1 (product level < threshold, product level TV = GOOD, valid communication with TII-XR) • Voltage = 1 (board voltages within ranges) • Board diagnostic = 1 (board status = GOOD) • Board diagnostic counter part = 1 (board status = GOOD) • Counter part = 1 (other relay board responds) • Relay (Rn) diagnostic = 1 (function status = GOOD) • Relay (Rn) diagnostic counter part = 1 (function status = GOOD)
Commissioning 6.6.11.5 Merging the Status to GPU-level status The TII-XR firmware implements an alarm for the operator by merging the output status of each board with the GPU level status, in order to communicate shut down information to the control room. See following matrix. NOTE: For field installations upgraded with the Overfill Protection functionality, the TII-XR firmware must be upgraded.
Commissioning 6.6.11.6 Overfill Protection Application Wiring ☛ Connect the external wiring (see illustrations below): • Connect terminal 48 to the pump or to the valve. • Connect terminal 49 to the mains. 49 Ofp_b FII-DO 1 FII-DO 2 14 15 16 17 14 15 16 17 CN2 (R1 + R2) 19 CN3 FII-DO 1 CN3 FII-DO 2 21 Ry3_b R3 Ry4_b 18 19 20 21 R4 18 Ry3_a 20 Ry4_a 19 Ry3_b 21 Ry4_b R3 18 19 20 21 CN3 (R3 + R4) R4 18 Ry3_a 48 Ofp_a 20 Ry4_a 49 Ofp_b 48 Ofp_a 6.6.11.
Commissioning ☛ Set the [Relay Mode] entity of R3 and R4 relay to for both FII-DO boards. the [Alarm Mode] entity of R3 and R4 relay to for both FII-DO boards. ☛ Set ☛ Set the [Monitor Mode] entity of R3 and R4 relay to for both FIIDO boards. ☛ Set the [Threshold] entity and [Hysteresis] entity of R3 and R4 relay to the application-specific desired values, for both FII-DO boards identically.
Commissioning In other words, this means: In case an anomaly is deteced by the internal gauge diagnostics, the gauge needs service within the time set by this timer. Typical value: <72> hours. If the Safety shut down time is disabled, so value = <0>, then the customer wants to continue permanently with the other branch. NOTE: When the "Safety shut down timer" is active or running, the remaining time until shutdown can be inspected by reading the [Safety shut down timer left] entity. 6.6.11.7.
Commissioning 6.6.11.8 Proof Testing By activating the command [Start Proof test] entity, the FII-DO simulates an overfill or underfill. The remainder of the SIF should work as expected (e.g. close a valve, stop a pump, generate an alarm) this should be validated. NOTE: This test must only be performed in a healthy situation when the product level in the tank is below the overfill threshold or above the underfill threshold.
Commissioning 6.7 SmartView Display Interface (FII-SMV) 6.7.1 Introduction FIGURE 6-24 < < The Field Interface Instrument - SmartView (FII-SMV) board is a module that communicates with SmartView. MAIN < > ESF07-0013 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.
Commissioning So, for example, if a stand-alone SmartView (address 3) and an integrated SmartView (address 2) are connected, the stand-alone SmartView (address 3) will be served as soon as the integrated SmartView (address 2) is closed (set to idle). 6.7.2 Commissioning the FII-SMV For a correct functioning of the FII-SMV module in an instrument the following entities can be set by using either Engauge or SmartView. ☛ By using the following table, check each entity for correctness.
Commissioning 6.8 Pressure & Density Measurement and Other HART Inputs (FCI-HT) 6.8.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.
Commissioning 20 mA analog signal digital FSK signal 4 mA Time The analog and digital signals within the HART® communication FIGURE 6-26 ESF07-0015 6.8.2 Software Description The FCI-HT board, being a functional module of the SmartRadar FlexLine, contains embedded software which enables it to collect data input from sensors via both the HART bus and the FlexConn CAN bus. Moreover the FCI-HT module can calculate the HIMS1 product density.
Commissioning For HIMS density measurement system diagrams, see FIGURE 6-27 and FIGURE 6-28.
Commissioning As an alternative function, the FCI-HT board also allows the connection of up to 5 generic HART sensors operating in multi-drop digital mode or one generic HART sensor operating in analog mode. In the multi-drop digital mode situation, one or two of the generic HART sensors can be [P1 Pressure] or [P3 Pressure], providing product pressure and vapour pressure respectively, but no HIMS density calculation will be available.
Commissioning 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 5 Generic HART 4 Generic HART 3 Generic HART 2 Generic HART 1 Generic HART HART-Bus FCI-HT CAN-Bus FIGURE 6-29 Alternate system diagram multi-drop digital mode 6 - 106 SmartRadar FlexLine Service Manual Part No.: 4417.
Commissioning In analog mode, the connected HART device will be allocated to Function 1 through 7, depending on the type of HART device connected. 1 Generic HART FCI-HT CAN-Bus FIGURE 6-30 Analog mode system diagram 6.8.3 Software Specifications 6.8.3.
Commissioning TABLE 6-2 HART Address Function 05 HART generic sensor 06 HART generic sensor 07 HART generic sensor 08 HART generic sensor 09 HART generic sensor 10 HART generic sensor 11 HART generic sensor 12 HART generic sensor 13 HART generic sensor 14 HART generic sensor 15 HART generic sensor Accepted HART addresses ☛ Before proceeding with commissioning, first check the maximum start-up current of all connected HART devices.
Commissioning 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.
Commissioning The PV of the P3 pressure HART device is read and converted into SI Units Pascals (Pa) within the FlexConn function PV. The value is filtered, and the filtering factor depends on the value set in the entity [P3 Integration time]. A higher value gives more filtering, and a lower value gives less filtering. The correction factor stored in the [P3 PV offset] entity is then subtracted from the filtered value. If the [P3 PV offset] entity = 0 no offset is applied.
Commissioning The Secondary and Tertiary values of a P3 pressure HART device are not converted, and they are simply translated from the HART device to the FlexConn environment. 6.8.3.4 HIMS Density To make HIMS density calculation possible, the relevant entity values must be available. See also FIGURE 6-31. ☛ Read also the Instruction Manual HIMS pressure measurement.
Commissioning 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 , 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.
Commissioning Sensor Type Temperature Distance Density TABLE 6-7 HART Unit Code Accepted HART Units Abbreviation Degrees Celsius °C 32 Degrees Fahrenheit °F 33 Feet ft 44 Meters m 45 Inches in 47 Kilograms per cubic meter kg/m3 3 92 Pounds per cubic foot lb/ft 94 Degrees API API 104 Accepted units for generic HART devices If an accepted HART PV unit code is found, the HART device is allocated to the relevant FlexConn function as detailed in TABLE 6-8.
Commissioning A HART temperature sensor may have a PV unit code Ohms, and a SV unit code Celsius. The required sensor value is temperature in Celsius, and this is translated into the FlexConn PV, and the Ohms value is translated into the FlexConn SV. Translation is performed in the order: PV (Distance, Temperature, Pressure, and Density), SV (Distance, Temperature, Pressure, and Density), TV (Distance, Temperature, Pressure, and Density).
Commissioning TABLE 6-10 Function Category Function Type Function Sub-type Function Allocation 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) Default function category, type, and sub-type The function type entity for Functions 3 through
Commissioning Function TABLE 6-12 Allocation Function Identification PV Unit Type Function 1 P1 Pressure UNIT_TYPE_PRESSURE Function 2 P3 Pressure UNIT_TYPE_PRESSURE Function 3 Distance UNIT_TYPE_LENGTH Function 4 Temperature UNIT_TYPE_TEMPERATURE Function 5 Pressure UNIT_TYPE_PRESSURE Function 6 Density UNIT_TYPE_DENSITY Function 7 Other UNIT_TYPE_UNDEFINED Function 8 HIMS Density UNI
Commissioning PV Unit Type Other Displayed Units PV Selected Unit Milli 1 - (none) <-> 2 - Kilo 3 - Mega 4 - Display Unit Type Range SmartView displayed unit types TABLE 6-13 The following PV types are supported on the SmartView display for P1 pressure and P3 pressure only. These are available changed by setting the [PV selected type] entity. This is detailed in TABLE 6-14.
Commissioning HIMS Density P1 Pressure Sensor Detected Yes No TABLE 6-15 P1 Ambient Air Pressure and P1 Installed Commissioned [P1 ambient air pressure] z AND [P1 installed] = [P1 ambient air pressure] = OR [P1 installed] = N/A Function 1 commissioning entities 6.8.4.2 Function 2 Commissioning ☛ Set all Function 2 entities according to TABLE 6-16 requirements, to commission P3.
Commissioning Function 3 4 HART Sensor Detected User Function Type = OR Yes Commissioned z OR No N/A Yes = OR No z OR N/A 5 N/A N/A 6 N/A N/A 7 N/A N/A TABLE 6-17 Function 3 through 7 commissioning entities 6.8.4.
Commissioning HIMS Density Enabled Disabled Function 8 Commissioning Entities Commissioned z AND z AND z AND z AND z AND z AND z AND z = OR =
Commissioning 6.8.5 Hardware Configuration 6.8.5.1 Terminal Allocation Terminal Number Name Function 24 V_Loop HART Bus power 25 GND_Loop HART Bus ground 6.8.5.2 LED Allocation LED Number Part No.: 4417.
Commissioning 6.9 HART Analog Outputs (HCI-HAO) 6.9.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 FIGURE 6-32 The HCI-HAO board ESF09-0005 The HART protocol is a bi-directional master-slave communication protocol, which is used to communicate between intelligent field instruments and host systems.
Commissioning 6.9.2 Functional Description HCI-HAO is a HART slave module, which uses standard HART communication to communicate with HART-devices. This module makes use of the Bell 202 Frequency Shift Keying (FSK) standard to superimpose digital signals at a low level on the 4–20 mA analog signal.
Commissioning All the HART universal commands and some common practice commands are supported by HCI-HAO. These are listed in the below tables. HART Universal Ccommands Command no.
Commissioning 6.9.3 Other HCI-HAO features Planar transformer for galvanic isolation from HART bus. Malfunctioning of the HCI-HAO card (or any linked cards) is reveiled on the HART bus by means of the device status. If any fatal errors occur during operation - which will run the program into an undesired situation - then a software reset (Warm Reset) is given to the HCI-HAO software. During this situation, the output of the module remains at the desired level till the software starts normal working.
Commissioning All the HART-compatible devices connected over the HART bus must have different polling addresses. Multi-drop mode is supported only in Passive mode of loop configuration. When the output current mode is set to Standard_4_20_MA, the polling address of the device must be made zero. When the device is not in multi-drop mode (STANDARD_4_20_MA mode selected) then the output current follows the changes in linked PV value.
Commissioning ☛ Give command [Enter Calibration Mode] ☛ Give command [Calibrate Analog Output at 4mA] ☛ Measure actual output current through the loop resistor, using a current meter ☛ Enter this value in the [Analog Output at 4mA] entity ☛ Give command [Calibrate Analog Output at 18mA] ☛ Measure actual output current through the loop resistor, using a current meter ☛ Enter this value in the [Analog Output at 18mA] entity ☛ Give command [Exit Calibration Mode], to exit the calibration mode These cali
Commissioning 6.9.5 Board Commissioning 6.9.5.1 Basic Configurable Entities Overview Basic configuration entities of the HCI-HAO board, which are configurable by using SmartView, are listed in the following table.
Commissioning Entity SmartView Display Data Type Type [PV Lower range value] Lw Range Value Float Non-Volatile <0> Default [PV Upper range value] Up Range Value Float Non-Volatile <0> [Analog Output mode] HART Mode Enumeration Non-Volatile [Burnout Value] Burnout Value Float Non-Volatile <3.
Commissioning Name Explanation Default Value Function Part [HART PV unit code] Unit code for linked PV Function 1 [HART Upper Transducer Limit] Upper transducer limit for connected sensor of linked PV board <0> Communication (HART communication) [HART Lower Transducer Limit] Lower transducer limit for connected sensor of linked PV board <0> [Polling Address] Polling address of the device, which is used for poll-based addressing <0> [Transducer Serial Number] Transduce
Commissioning following entities can be set by Engauge or SmartView for a correct functioning of the HCI-HAO module in an instrument. ☛ The If one needs to assign SV, TV, QV to HCI-HAO then the corresponding unit codes also needs to be set properly so that the value read from other FlexConn board will be proper.
Commissioning Name Explanation Default Value Function Part [HART SV unit code] Unit code for linked SV Function 1 [HART TV unit code] Unit code for linked TV Communication (HART communication) [HART QV unit code] Unit code for linked QV [Configuration changed Counter] Increments every time the configuration is changed <0> [Device ID] Same as Enraf Serial number. This is a unique number to every board.
Commissioning 6.9.6 Hardware Configuration 6.9.6.1 Jumper Allocation The following are typical jumper settings done on the HCI-HAO board.
Commissioning 6.10 Average Temperature & Water Level Measurement (FII-VT) 6.10.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 FIGURE 6-34 The FII-VT board with its planar transformer ESF07-0016 By using the HART® protocol (see also 6.8.
Commissioning 6.10.2 VITO Interface Types For temperature and/or water level measurement, a proper VITO probe must be connected to the FII-VT module, using a VITO interface.
Commissioning > 700 mm x x x x x x 25 15 S L x 65 S X 15 lowest element offset x X 25 L lowest element offset x lowest element offset x sensor length overall length . sensor length/14 > 700 mm . sensor length sensor length/15 overall length x x x 1000 mm L x H x x lowest element offset product immersion depth 1000 mm x hysteresis L . x x x sensor length/14 x x . sensor length x level . H 65 x x . overall length . H sensor length .
Commissioning > 700 mm x x x x x x x x 1000 mm L x 25 65 x lowest element offset L L 1000 mm x lowest element offset x 1000 mm x sensitive length 0.5 / 1.0 / 1.5 / 2.0 m x lowest element offset x sensor length . overall length x . sensor length sensor length/8 overall length x 762 VITO LT interface x sensor length/7 > 700 mm x H x 1000 mm L . x 762 VITO LT interface x . sensor length x overall length x . lowest element offset overall length . H x .
Commissioning 6.10.3.1.1 Product Temperature following entities must be set by Engauge or SmartView for a correct functioning of the FII-VT module in an instrument. ☛ The NOTE: Using Engauge, following entities are set within the Engauge Product temperature tab. Name Explanation Value Range Default [Lowest element offset] The distance from tank zero till the lowest element position in the temperature probe floating point number: <-x.x .. +x.x> <80.
Commissioning Name Explanation Value Range Default [Alarm test enable] Enables (if activated, see next listed entity) the simulation of one of the 4 alarms for a minute, by simulating the actual measured Primary Value is below or above the alarm threshold. [Alarm test] Activates and selects at the same time the Alarm test (if enabled with the [Alarm test enable] listed before, and the 4 alarm thresholds are properly set).
Commissioning Name Explanation Value Range Default [Alarm test enable] Enables (if activated, see next listed entity) the simulation of one of the 4 alarms for a minute, by simulating the actual measured Primary Value is below or above the alarm threshold. [Alarm test] Activates and selects at the same time the Alarm test (if enabled with the [Alarm test enable] listed before, and the 4 alarm thresholds are properly set).
Commissioning following entities can be set by Engauge or SmartView for a correct functioning of the FII-VT module in an instrument. ☛ The Name Explanation Value Range Default [Water probe length] The length of a water probe floating point number: <-x.x .. +x.x> <0.5> [High High alarm] [High Alarm] [Low Alarm] [Low Low alarm] 4 thresholds for activating a related alarm status in the Primary Value floating point numbers: <-x.x .. +x.x> <+1.
Commissioning 6.10.3.2 Commissioning Parameters for MRT or RTD Enraf Model VITO Type Description MRT Multiple Resistance Thermometer MRT with up to 13 temperature elements with one spot element RTD 3-spot Resistance Temperature Detector 1..3 RTD spots in a 3-wire connection multi-spot Resistance Temperature Detector 1..14 RTD spots in a 2-wire connection See FIGURE 6-37 and FIGURE 6-38.
Commissioning flying leads extension tube hysteresis ** product immersion depth lowest point of all elements anchor eye lowest element offset Zero level of tank FIGURE 6-38 Multiple Resistance Thermometer (MRT) parameters ESF07-0019 6.10.3.2.1 Product Temperature following entities must be set by Engauge or SmartView for a correct functioning of the FII-VT module in an instrument. ☛ The NOTE: Using Engauge, following entities are set within the Engauge Product temperature tab. Part No.
Commissioning RTD 3 spots (see FIGURE 6-37 left side) Name Explanation Value Range Default [Element type] The supported element type is: SPL 3 characters <---> [Number of elements] The number of elements a RTD probe has <1 .. 3> <0> [Lowest element offset] The distance from tank zero till the lowest position of the multi-RTD probe. So not used for the 3-wire version and it must be 0. floating point number: <-x.x .. +x.x> <80.
Commissioning MRT (see FIGURE 6-38) Name Explanation Value Range Default [Element type] See Table TABLE 6-19 below. 3 characters <---> [Number of elements] The number of elements (resistors) an MRT probe has <1 .. 14> <0> [Lowest element offset] The distance from tank zero till the lowest position of the MRT probe floating point number: <-x.x .. +x.x> <80.
Commissioning The following entities can be set by Engauge or SmartView for a correct functioning of the FII-VT module in an instrument. ☛ Check each entity for its correctness. Name Explanation Value Range Default [Product immersion depth] The minimum required product level distance above an element before this element is taken into account in the average product temperature calculation floating point number: <-x.x .. +x.x> <0.
Commissioning 6.10.3.2.2 Vapour Temperature NOTE: Using Engauge, following entities are set within the Engauge Vapour temperature tab. Some Vapour temperature settings are shared with Product temperature settings. The following entities can be set by Engauge or SmartView for a correct functioning of the FII-VT module in an instrument. ☛ Check each entity for its correctness.
Commissioning 6.10.3.3 Commissioning Parameters for the 765 VITO Water Probe For the entities to be set for the stand-alone 765 VITO water probe (see FIGURE 6-39), see 6.10.3.3.1. 15 25 sensitive length 0.5 / 1.0 / 1.5 / 2.0 m 762 VITO LT interface Model 765 VITO water probe FIGURE 6-39 The model 765 VITO water probe 6 - 148 SmartRadar FlexLine Service Manual ESF07-0042 Part No.: 4417.
Commissioning 6.10.3.3.1 Water Level following entities must be set by Engauge or SmartView for a correct functioning of the FII-VT module in an instrument. ☛ The Name Explanation Value Range Default [Maximum water capacity] The maximum capacity when the probe is fully submerged in water (in pF) floating point number: <-x.x .. +x.x> <20000> [Minimum water capacity] The minimum capacity when the probe is not submerged in water (in pF) floating point number: <-x.x .. +x.
Commissioning Name Explanation Value Range Default [Alarm test] Activates and selects at the same time the Alarm test (if enabled with the [Alarm test enable] listed before, and the 4 alarm thresholds are properly set). [No Alarm] [High High alarm] [High Alarm] [Low Alarm] [Low Low alarm] [Function identification] The current module’s function name. This function is visible on the SmartView display. 13 characters 6.10.
Commissioning 6.11 Average Temperature Measurement (FII-RTD) 6.11.1 Introduction The Field Interface Instrument - Resistance Temperature Detector (FIIRTD) board is a sensor module for the instrument (gauge) and calculates average product- , vapour- and ambient temperatures. For realizing this, RTDs or MRTs must be directly connected to the FIIRTD module.
Commissioning 6.11.2 Some Important Settings The FII-RTD can be tailored to the need of the customer by a lot of settings. See 6.11.4 - Commissioning. Some important settings of the FII-RTD are listed below.
Commissioning checking range if [Temperature range check] is enabled permanent check spot element in fail (3 retries) spot element in fail*) range check result = OK *) if [Element skipping] is enabled, “spot element in fail” can be skipped upper shortcut range FIGURE 6-41 lower temperature range Temperature range check feature permanent check spot element in fail*) spot element in fail (3 retries) *) if [Element skipping] is enabled, “spot element in fail” can be skipped upper temperature ran
Commissioning ow element usage O O O O (default) s s and roduct le el = elements s roduct le el = 3 elements roduct le el = lowest element = lowest element empe rature element e clude one empe rature element e clude one = = smoothing le el smoothing le el pos AND AND pos AND = pos AND pos all submerged elements with low element beha iour temperature fail e cluded all submerged elements with moothing (o errules selected temperature calculation method) e cluded pos empera
Commissioning W&M Sealing1: This board can be electronically sealed via the software. A Notified Body can set his password via [W&M notified body seal password]. He can apply the seal by setting [W&M seal]. Here some data logging is filled in and the related password. This requires a W&M module for Engauge. If the primary value of the product temperature is completely valid, then a W&M indication will be set (e.g. visible in SmartView).
Commissioning Name Explanation Value Range Default [RTD configuration] Selects how the RTDs are positioned. 6.11.4.2 Commissioning Parameters for MPT Temperature Calculations NOTE: Make sure the RTD/MPT jumper is set to MPT. ☛ The following entities must be set set by Engauge or SmartView for a correct functioning of the FII-RTD module in an instrument.
Commissioning Name Explanation Value Range Default [Lowest element offset] The distance from tank zero till the bottom of the probe floating point number: <-x.x .. +x.x> <80.0> [Number of elements] The number of elements used <1..6> <0> [Element type] The type (material) of the used RTDs [Measurement type] Selects RTDs, MPT, or MRT.
Commissioning Name Explanation Value Range Default [High High alarm] [High Alarm] [Low Alarm] [Low Low alarm] 4 thresholds for activating a related alarm status in the Primary Value floating point numbers: <-x.x .. +x.x> <1.0E22> [Alarm test enable] Enables (if activated, see next listed entity) the simulation of one of the 4 alarms for a minute, by simulating the actual measured Primary Value is slightly below or above the alarm threshold.
Commissioning Name Explanation Value Range Default [Smoothing level] See FIGURE 6-42 floating point numbers: <-x.x .. +x.x> <0.0> [MPT element position mode] [Only for MPT] Determines whether the element positions are automatically calculated (based on sensor length) or manually entered. [RTD element positions] [Only for MPT] If MPT element position mode is MANUALLY then here the positions can be filled in. floating point numbers: <-x.x .. +x.x> <0.
Commissioning Name Explanation Value Range Default [MRT length table] [Only for MRT] Specifies whether a fixed range of MRT resistors is used (= ) or user configured lenghts (= ). Fixed lengths are: 0.65, 1.25, 1.95, 2.85, 4.15, 5.65 1 character [MRT element length used if MRT length table is 'T'] [Only for MRT] The lengths of the MRTs including anchor eye floating point numbers: <-x.x .. +x.x> <0.0> 6.11.4.4.
Commissioning Name Explanation Value Range Default [Alarm test] Activates and selects at the same time the Alarm test (if enabled with the [Alarm test enable] listed before, and the 4 alarm thresholds are properly set). [No Alarm] [High High alarm] [High Alarm] [Low Alarm] [Low Low alarm] [Function identification] The name of the current function of this module. This name is visible on the SmartView. 13 characters 6.11.4.4.
Commissioning 6.11.5 Commissioning Check ☛ After having checked/set all before listed entities, make sure the [Board Commissioned], the [Product temperature Commissioned], the [Vapour temperature Commissioned], and the [Ambient Temperature Commissioned] entities are ; the [Board Health], the [Product temperature Health], the [Vapour temperature Health], and the [Ambient Temperature Health] entities are .
Honeywell Enraf Delftechpark 39 2628 XJ Delft The Netherlands Tel: +31 (0)15-2701 100 www.honeywell.com/ps 4417762 - Revision 6HSWHPEHU © 20 Honeywell International Inc.
