SLG 700 SmartLine Level Transmitter Guided Wave Radar FOUNDATION TM Fieldbus Option Manual

Transcription

1 SLG 700 SmartLine Level Transmitter Guided Wave Radar FOUNDATION TM Fieldbus Option Manual 34-SL Revision 5.0 September 2017 Honeywell Process Solutions

2 Copyrights, Notices and Trademarks Copyright 2017 by Honeywell, Inc. Revision 5.0, September 2017 While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written agreement with and for its customers. In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The information and specifications in this document are subject to change without notice. Honeywell, PlantScape, Experion PKS, and TotalPlant are registered trademarks of Honeywell International Inc. Other brand or product names are trademarks of their respective owners. Honeywell Process Solutions 1250 W Sam Houston Pkwy S Houston, TX Page ii FOUNDATION Fieldbus Option User's Manual Rev 3.0

3 About This Document This guide provides the details of programming Honeywell SLG 700 SmartLine Level Transmitters for applications involving FOUNDATION Fieldbus protocol. For installation, wiring, and maintenance information, refer to the SLG 700 SmartLine Level Transmitter User s Guide. The configuration of your transmitter depends on the mode of operation and the options selected for it with respect to operating controls, displays and mechanical installation. An SLG 700 FF Level transmitter can be digitally integrated with any FF compliant Host. Among Honeywell systems, it can be integrated with Experion PKS DCS and also use Field Device manager (FDM) for asset management and configuration. Release Information SmartLine Level Transmitter Guided Wave Radar FOUNDATION Fieldbus Option Manual Document # 34-SL Rev 1.0 April 2015 First release Rev 2.0 July 2015 Security Vulnerability section added. Rev 3.0 July 2016 Updates for R101 release. Rev 4.0 February 2017 Updates for R102 release. Rev 5.0 September 2017 DTM updates References The following list identifies all documents that may be sources of reference for material discussed in this publication. SLG 700 SmartLine Level Guided Wave Radar, User s Guide, Document #34-SL SLG Pocket Configuration Guide, SmartLine Level Guided Wave Radar, Document #34-SL SLG 700 SmartLine Level Guided Wave Radar Quick Start Guide, Document #34-SL SLG 700 Smart Guided Wave Radar Level Transmitter with HART Communications Options Safety Manual, Document #34-SL SLG 700 SmartLine Level Guided Wave Radar Specification, Document #34-SL MC Tookit User Manual, for 404 or later, Document #34-ST Smart Field Communicator Model STS 103 Operating Guide, Document # 34-ST Links to documentation SmartLine Level Transmitters: Experion: Rev.5 FOUNDATION Fieldbus Option User's Manual Page iii

4 Patent Notice The Honeywell SLG 700 SmartLine Level Transmitter family is covered by one or more of the following U. S. Patents: 6,055,633. Support and Contact Information For Europe, Asia Pacific, North and South America contact details, refer to the back page of this manual or the appropriate Honeywell Solution Support web site: Honeywell Corporate Honeywell Process Solutions SmartLine Level Transmitters Training Classes Telephone and Contacts Area Organization Phone Number United States and Canada Global Support Honeywell Inc. Honeywell Process Solutions Customer Service Global Technical Support Page iv FOUNDATION Fieldbus Option User's Manual Rev.5

5 Symbol Definitions The following table lists those symbols used in this document to denote certain conditions. Symbol Definition ATTENTION: Identifies information that requires special consideration. TIP: Identifies advice or hints for the user, often in terms of performing a task. REFERENCE -EXTERNAL: Identifies an additional source of information outside of the bookset. REFERENCE - INTERNAL: Identifies an additional source of information within the bookset. CAUTION Indicates a situation which, if not avoided, may result in equipment or work (data) on the system being damaged or lost, or may result in the inability to properly operate the process. CAUTION: Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury. It may also be used to alert against unsafe practices. CAUTION symbol on the equipment refers the user to the product manual for additional information. The symbol appears next to required information in the manual. WARNING: Indicates a potentially hazardous situation, which, if not avoided, could result in serious injury or death. WARNING symbol on the equipment refers the user to the product manual for additional information. The symbol appears next to required information in the manual. WARNING, Risk of electrical shock: Potential shock hazard where HAZARDOUS LIVE voltages greater than 30 Vrms, 42.4 Vpeak, or 60 VDC may be accessible. ESD HAZARD: Danger of an electro-static discharge to which equipment may be sensitive. Observe precautions for handling electrostatic sensitive devices. Protective Earth (PE) terminal: Provided for connection of the protective earth (green or green/yellow) supply system conductor. Functional earth terminal: Used for non-safety purposes such as noise immunity improvement. NOTE: This connection shall be bonded to Protective Earth at the source of supply in accordance with national local electrical code requirements. Rev.5 FOUNDATION Fieldbus Option User's Manual Page v

6 Symbol Definition Earth Ground: Functional earth connection. NOTE: This connection shall be bonded to Protective Earth at the source of supply in accordance with national and local electrical code requirements. Chassis Ground: Identifies a connection to the chassis or frame of the equipment shall be bonded to Protective Earth at the source of supply in accordance with national and local electrical code requirements. Page vi FOUNDATION Fieldbus Option User's Manual Rev.5

7 Terms and Acronyms Term Alarm AI - Analog Input (function block) Application Block Configuration (of a system or device) Device Device Description (DD) Device Description Language (DDL) Device Tag DTM EEPROM EMI Event Field Device FOUNDATION Fieldbus FDM FDT FISCO FTA Function Block Function Block Application Process Hz Definition The detection of a block leaving a particular state and when it returns back to that state. One of the standard function blocks define by the Foundation Fieldbus A software program that interacts with blocks, events and objects. One application may interface with other applications or contain more than one application. A logical software unit that makes up one named copy of a block and the associated parameters its block type specifies. It can be a resource block, transducer block or a function block. A step in system design: selecting functional units, assigning their locations and identifiers, and defining their interconnections. A physical entity capable of performing one or more specific functions. Examples include transmitters, actuators, controllers, operator interfaces. Description of FBAPs within a device. Files that describe the software objects in a device, such as function blocks and parameters. The DD binary are created by passing DD source files through a standard tool called a tokenizer. A standardized programming language (similar to C) used to write device description source files. The Physical Device Tag of the device as specified in the Foundation Fieldbus specifications. Device Type Manager Electrically Erasable Programmable Read Only Memory Electromagnetic Interference An instantaneous occurrence that is significant to scheduling block execution and to the operational (event) view of the application. A fieldbus-compatible device that contains and executes function blocks. Communications protocol for a digital, serial, two-way system which interconnects industrial field equipment such as sensors, actuators and controllers. Field Device Manager Field Device Tool Foundation Fieldbus Intrinsically Safe Concept Field Termination Assembly An executable software object that performs a specific task, such as measurement or control, with inputs and outputs that connect to other function blocks in a standard way. The part of the device software that executes the blocks (function, transducer, or resource blocks). Hertz Rev.5 FOUNDATION Fieldbus Option User's Manual Page vii

8 Term Link Active Scheduler LRV Macrocycle madc Manufacturer's Signal Processing mv Network Management Network Management Agent Network Management Information Base Nm NVM Object Dictionary Objects OOS Parameters PKS PM Proportional Integral Derivative control PV RFI SFC Stack Status System Management System Management Agent Definition A device which is responsible for keeping a link operational. The LAS executes the link schedule, circulates tokens, distributes time messages and probes for new devices. Lower Range Value The least common multiple of all the loop times on a given link. Milliamperes Direct Current A term used to describe signal processing in a device that is not defined by FF specifications. Millivolts A part of the software and configuration data in a Foundation Fieldbus device that handles the management of the network. Part of the device software that operates on network management objects. A collection of objects and parameters comprising configuration, performance and fault-related information for the communication system of a device. Newton. Meters Non-Volatile Memory Definitions and descriptions of network visible objects of a device. There are various object dictionaries within a device. The dictionaries contain objects and their associated parameters which support the application in which they are contained. Entities within the FBAP, such as blocks, alert objects, trend objects, parameters, display lists, etc. Out of Service A value or variable which resides in block objects Process Knowledge System Process Manger A standard control algorithm. Also refers to a PID function block. Process Variable Radio Frequency Interference Smart Field communicator The software component that implement the Foundation Fieldbus communications protocol specifications, including FMS, FAS, DLL, SM and NM. A coded value that qualifies dynamic variables (parameters) in function blocks. This value is usually passed along with the value from block to block. Status is fully defined in the FF FBAP specifications. Provides services that coordinate the operation of various devices in a distributed fieldbus system. Part of the device software that operates on system management objects. Page viii FOUNDATION Fieldbus Option User's Manual Rev.5

9 Term System Management Information Base TAC TB URV US Vac Vdc Virtual Communication Relationship Virtual Field Device Definition A collection of objects and parameters comprising configuration and operational information used for control of system management operations. Technical Assistance Center Transducer Block Upper Range Value Universal Station Volts Alternating Current Volts Direct Current A defined communication endpoint. Fieldbus communications can primarily only take place along an active communications "path" that consists of two VCR endpoints. A logical grouping of "user layer" functions. Function blocks are grouped into a VFD, and system and network management are grouped into a VFD. For example, to establish communications between a transducer block and a function block, a VCR must be defined at the transducer block and a VCR must be defined at the function block. Rev.5 FOUNDATION Fieldbus Option User's Manual Page ix

10 Contents COPYRIGHTS, NOTICES AND TRADEMARKS... II 1. INTRODUCTION About the SLG 700 FOUNDATION Fieldbus Level Transmitter Transmitter Components... 2 Overview of components Features of the transmitter GETTING STARTED Verifying the installation Verifying communication with the transmitter Establishing communication with host systems SLG 700 FF LEVEL TRANSMITTER CONFIGURATION Importing the SLG 700 FF Device Description (DD) files... 7 Importing the DD to Experion PKS...7 Control strategy Creating control strategy Device replacement Configuring the function block application process Resource block Execution Parameter List Attributes Level Transducer block Execution Parameter List Attributes Auxiliary Transducer Block Parameter List Attributes Diagnostic Transducer block Execution Sensor Detailed Status Critical Status Critical Status Non-Critical Status Non-Critical Status DEVICE MODEL DETAILS: Device Diagnostics: Power Cycle Track Operating Voltage Track Parameter List Attributes Page x FOUNDATION Fieldbus Option User's Manual Rev.5

11 3.8 LCD Transducer block Execution Attributes Analog Input block Execution Parameters List Attributes Proportional Integral Derivative (PID) block with auto tune Execution Auto tuning procedure Parameter list Attributes Input Selector block Execution Parameters List Attributes Integrator block Execution Parameters List Attributes Arithmetic block Execution Parameter List Attributes Signal Characterizer block Execution Parameter list Attributes Output Splitter block Execution Parameter list Attributes Configuring the transmitter using Field Device Manager system SLG 700 FF LEVEL TRANSMITTER OPERATION Operational considerations LAS Capability Special Non-volatile parameters and NVM Wear-out Mode Restricted Writes to Parameters Configuration of the transmitter using Handheld (HH) Performing block instantiation About block instantiation Block instantiation using Experion PKS SLG 700 FF LEVEL TRANSMITTER MAINTENANCE Replacing the Local Display and Electronic Assembly Downloading the firmware About firmware download feature Class Recommendations Downloading the File Rev.5 FOUNDATION Fieldbus Option User's Manual Page xi

12 6. USING THE DTM Introduction Components Downloads to Install and launch the DTM DTM Help Level Transducer block configuring Diagnostics Transducer block configuration LCD Transducer block configuration Auxiliary Transducer block configuration Diagnostics Resource block configuration Analog input block configuration SLG 700 FF LEVEL TRANSMITTER TROUBLESHOOTING Troubleshooting overview Troubleshooting the transmitter Device not visible on the network Incorrect or non-compatible tools Troubleshooting blocks Non-functioning blocks Troubleshooting block configuration errors Troubleshooting the Resource block Troubleshooting the Level Transducer block Troubleshooting the Diagnostics Transducer block Troubleshooting the Diagnostics Transducer block Troubleshooting the LCD Transducer block Troubleshooting the Analog Input (AI) block Troubleshooting the Proportional Integral Derivative (PID) block Troubleshooting the Input Selector block Troubleshooting the Arithmetic block Troubleshooting the Output Splitter block Troubleshooting the Signal Characterizer block Resolving the block configuration errors Device Diagnostics SLG 700 FF level transmitter memory Performing diagnostics in the background BLOCK_ERR parameter Transmitter Diagnostics Function Block Faults Understanding simulation mode About the simulation mode jumper Setting the simulation jumper Enabling simulation mode Simulation mode truth table Setting Al block mode Understanding write protection Page xii FOUNDATION Fieldbus Option User's Manual Rev.5

13 8. SECURITY How to report a security vulnerability Rev.5 FOUNDATION Fieldbus Option User's Manual Page xiii

14 Tables Table 1: Transmitter installation verification tasks... 4 Table 2: Transmitter parameters... 5 Table 3: Bit mapping of the BLOCK_ERR Table 4: Priority for Alarms Table 5: Diagnostic Definitions Table 6: Resource block parameters Table 7: Level Transducer block parameters Please refer Table 8: Auxiliary Transducer block parameters for more details on Linearization Table 8: Auxiliary Transducer block parameters Table 9: Sensor Detailed Status Table 10: Diagnostic Transducer block parameters Table 11 LCD parameters Table 12: LCD Transducer block parameters Table 13: Analog Input block parameters Table 14: PID Tuning parameters Table 15: PID block parameters Table 16: Input Selector block parameters Table 17: Integrator block parameters Table 18: Arithmetic block parameters Table 19: Signal Characterizer block parameters Table 20: Output Splitter block parameters Table 40 - Dielectric Constants Required by Application Table 41 - Minimum blocking distances and transition zones for the various probe types Table 21: Resource block Table 22: Level Transducer block Table 23: Auxiliary Transducer block Table 24: Diagnostics Transducer block Table 25: LCD Transducer block Table 26: Analog Input block Table 27: PID block Table 28: Input Selector block Table 29: Arithmetic block Table 30: Output Splitter block Table 31: Signal Characterizer block Table 32: Resolving block configuration errors Table 33: Diagnostics Table 34: Identifying Critical and Non-critical Function block faults Table 35: Summary of Function blocks Non-critical Faults Table 36: Summary of Function blocks Critical Faults Table 37: Setting the Simulation Jumper Table 38: Simulation Mode Truth Table Table 39: Write Lock Page xiv FOUNDATION Fieldbus Option User's Manual Rev.5

15 Figures Figure 1 Components of SLG Figure 2: Level Transducer Block Figure 3: Windowed Echo Curve Figure 4: Full Echo Curve Figure 5: Processed (Full) Echo Curve Figure 6: Background Subtraction Array Figure 7: Adjusting the Correlation Algorithm Figure 8 Zoom View Figure 9: Adjusting the Gain Parameter Figure 10: Adjusting the Width and Attenuation Parameters Figure 11: LCD Transducer Block Figure 12: Analog Input Block Figure 13: Analog Input Block Schematic Diagram Figure 14: PID Block Figure 15: PID Block Schematic Diagram Figure 16: Input Selector Block Figure 17: Input Selector Schematic Diagram Figure 18: Integrator Block Figure 19: Two Rate Inputs Figure 20: Arithmetic Block Figure 21: Arithmetic Schematic Diagram Figure 22: Signal Characterizer Block Figure 23: Signal Characterizer Curve Figure 24: Output Splitter Block Figure 25: Output Splitter Schematic Figure 26: Split Range and Sequence Operation Figure 27: OUT with LOCKVAL LOCK Figure 28: OUT with LOCKVAL NO LOCK Figure 29: Connecting the transmitter to the handheld Figure 30: Single Liquid Figure 31: Two Liquids Flooded Figure 32: Two Liquids Non-Flooded Figure 33- Reference plane R for flanged and threaded connections Figure 34 Attenuation model Figure 35 - Radar Impulse Reflection Model Figure 36 - Analog Input Block Figure 37: Simulation Jumper Location on Communication Board Rev.5 FOUNDATION Fieldbus Option User's Manual Page xv

16 Page xvi FOUNDATION Fieldbus Option User's Manual Rev.5

17 1. Introduction 1.1 About the SLG 700 FOUNDATION Fieldbus Level Transmitter The Honeywell SLG 700 is a SmartLine Level transmitter that has a wide range of additional features along with supporting the FOUNDATION Fieldbus (FF) communication protocol. The SLG 700 level transmitter with FF protocol provides a FOUNDATIONTM Fieldbus interface to operate in a compatible distributed Fieldbus system. The transmitter includes FOUNDATION Fieldbus electronics for operating in a Kbit/s Fieldbus network and can interoperate with any FOUNDATION Fieldbus registered device. The Honeywell SmartLine SLG 700 is a high performance transmitter offering high accuracy, reliability and resolution over a wide range of process conditions. The SLG 700 Fieldbus device is fully tested and compliant with Honeywell Experion PKS providing the highest level of compatibility assurance and integration capabilities. Integration with Honeywell s Experion PKS offers the following unique advantages through Smart Connection suite. Transmitter messaging To enhance safety and productivity through clear identification and assignment of maintenance tasks in the local transmitter display Maintenance mode indication To enhance safety through system initiated command to identify that the device is available for maintenance FDM Plant Area Views with Health summaries To reduce the time to identify, diagnose and fix device problems by providing an overview of device health based on user defined groups in the Honeywell Field Device Manager. SmartLine easily meets the most demanding needs for level measurement applications including interface measurements. SmartLine Level features include the following: Best-in-Class performance +/- 3mm accuracy or 0.03% measured distance 1mm resolution +/- 1mm repeatability Support for materials with dielectric constant of 1.4 Lowest Cost of Ownership Polarity-insensitivity terminations Modular construction Field replaceable modules Multiple local display capabilities 3 button local configuration Smart Connection Suite Transmitter messaging Maintenance mode indication Tamper alerts Advanced diagnostics Comprehensive integration testing Rev.5 FOUNDATION Fieldbus Option User's Manual Page 1

18 1.2 Transmitter Components Overview of components As shown in Figure 1 the transmitter consists of: Electronics housing containing Display module (optional) Buttons module (optional) Communications module Electrical terminal block assembly Sensor housing Process connector Probe, also known as a waveguide These components are described below. Additional mounting and optional accessories are available, such as centering discs for the waveguide. For list of all options and accessories please refer to purchasing specifications. Representational Electronics housing (display, buttons, communications terminal) Sensor housing Process connector Probe (waveguide) Figure 1 Components of SLG 700 Page 2 FOUNDATION Fieldbus Option User's Manual Rev.5

19 1.3 Features of the transmitter The transmitter is a configurable intelligent field device that acts as a guided wave radar sensor, and is capable of performing control algorithms on process variables. The core functionalities of the field device include: Process Variable (PV) measurement Function Block Application Process (FBAP) Device diagnostics The SLG 700 features standard fieldbus function blocks with manufacturer-specific additions for enhanced operation. The transmitter can function as a Link Active Scheduler (LAS) in a Fieldbus network. It supports the following features: Link-master capability Supports the following standard function blocks apart from the Resource and Transducer blocks: Analog Input block Input Selector block Signal Characterizer block PID with auto tune block Arithmetic block Output splitter Integrator block Function block instantiation is supported by the following blocks: Analog Input block PID with auto tune block Arithmetic block Input Selector block Signal Characterizer block Supports the following Transducer blocks: Level Transducer block Auxiliary Transducer Block LCD Transducer block Diagnostic Transducer block Supports class 3 type firmware download through commercial hosts. DD and EDDL Features The SLG 700 supports DD and EDD file formats, and the data is displayed using the EDDL features in the form of menus, graphs, charts, and pictures. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 3

20 2.1 Verifying the installation 2. Getting started Verifying transmitter installation tasks After the transmitter is installed and powered up, you can verify communication between the transmitter and the field devices on the network. Table 1 outlines the steps for identifying and checking the transmitter on a Fieldbus network. Table 1: Transmitter installation verification tasks Task Description Comment Verify device location Verify device identification Verify connection with host computer to device Verify or assign Device Tag and address Configure device ATTENTION The transmitter is shipped at a temporary (248) address. This will enable FOUNDATION Fieldbus host system to automatically recognize the device and move it to a permanent address. Verify device operation Check that the device is installed in the correct physical location. Match the device identification with the physical location. The device serial number is stamped on the transmitter housing top nameplate. On the operator interface, check and make sure communications are established with the device on the Fieldbus network. Check that the Device Tag and node address are set. If not, assign the Device Tag and the correct node address. The Device Tag and address can be set and viewed using the Fieldbus device configurator application. Use a Device Tag name (up to 16 characters) that does not contain spaces. Using a Fieldbus configuration program, create a function block application as part of the device configuration and process control strategy. Bring the network online, verify operation, tune loops, and so on. ATTENTION It is recommended to wait for 40 seconds when the transmitter is power cycled. Page 4 FOUNDATION Fieldbus Option User's Manual Rev.5

21 2.2 Verifying communication with the transmitter On the operator interface, establish communication with the device on the Fieldbus network. If the device is not visible on the network, verify that the device has been installed properly Identify the transmitter Verify the device identification of the transmitter by checking the device parameters. The parameters contain the following information: Transmitter type ( temperature transmitter, pressure transmitter, level transmitter and remote meter) Device Tag (tag description of the transmitter) Sensor serial number Firmware revision level (revision level of the firmware elements) Check the transmitter parameters listed in Table 2 and note down the values to identify the transmitter. ATTENTION It is recommended to verify the correct version of the Device Description file is present on the host computer. This helps in getting the correct parameter names and its corresponding descriptions, while viewing the device parameters. Table 2: Transmitter parameters Parameter To verify Resource block DEV_TYPE Device Tag (Physical device tag name of the transmitter) Resource Block SERIAL_NO ATTENTION The Device Tag name can be set and viewed using the Fieldbus device configurator application. Use a device tag name (up to sixteen characters) that does not contain spaces. That the transmitter is of the proper device type. For all the SLG 700 SmartLine Guided Wave Radar Level Transmitter, the value is 0007 The Device Tag is correct. Device Tag name SMARTLINE_GWR_FF This is the serial number of the FF Transmitter which is obtained from the Sensor housing. Check that the module has a valid serial number. Resource Block SOFTWARE_REV This is the Software revision of the Communication board. This may be checked when instructed by Honeywell TAC for troubleshooting. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 5

22 2.3 Establishing communication with host systems The transmitter establishes communication with the host systems using DD or DTM Device Description (DD) The DD is a binary file that provides the definition for parameters in the FBAP of the transmitter. For example, DD refers to the function blocks that a transmitter contains, and the corresponding parameters in the blocks that are critical to the interoperability of Fieldbus devices. They define the data required to establish communications between different Fieldbus devices from multiple vendors with control system hosts. The DD provides an extended description of each object in the Virtual Field Device (VFD). The Fieldbus Foundation provides the DD for all registered devices on its website, stered&itemid= Enhanced Device Description (EDD) There are two types of EDDs are available, namely.ff5/.sy5 and.ffo/sym. The.ffo/.sym binary files are generated for the legacy hosts to load the device DD that is generated using latest tokenizer. A few constructs, such as Images that are supported in.ff5/.sy5 binaries, are not supported in.ffo/.sym binary files Device Type Manager (DTM) The DTM is similar to a device driver that enables usage of devices in all the asset management and device configuration software such as FDM or PACTware, with the help of the FDT-DTM technology. The DTM has the following primary functions: Provides a graphic user interface for device configuration. Provides device configuration, calibration, and management features for the particular device. The DTM provides functions for accessing device parameters, configuring and operating the devices, calibrating, and diagnosing problems. Download the current version of the FF DTMs from the software tab at Page 6 FOUNDATION Fieldbus Option User's Manual Rev.5

23 3. SLG 700 FF Level Transmitter Configuration 3.1 Importing the SLG 700 FF Device Description (DD) files Importing the DD to Experion PKS ATTENTION Experion release compatibility Experion Release DD Compatibility Yes Yes Yes The steps in the following procedure are specific to Experion only. Step Action 1 From the Control Builder main screen, click Fieldbus Device Description Import. OR Select File > New > Type >Fieldbus Device You can Import the DD using one of the following steps: 2 Choose Browse to locate the folder where you have stored the DD file. Select the required folder, and click OK. Select the DD from the Device List, and click OK. The following dialog box appears, 3 Click OK. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 7

24 4 Enter the Device Type Name, and then click Save As. ATTENTION In some versions of Experion, the user must select the capability level 1 for all function blocks. 5 The following dialog box appears, Click OK. 6 The following dialog box appears Click OK. ATTENTION The device type - SLGWRFF_0101_1 is used as an example. 7 The device is created in the Library-Containment window under the folder named Honeywell. 8 From the Library-Containment window, drag and drop the device into the corresponding FF link on the Project-Assignment window. The fallowing window opens: Page 8 FOUNDATION Fieldbus Option User's Manual Rev.5

25 You are prompted to name the new function block. If you want to change the name in the destination column, type the new name or if you want to use the default name, click Finish. The device is added on the FF link on the Project-Assignment window. Double click the device link on Monitoring-Assignment, the following window opens: 9 Update the capability level as 1 under uncommisioned devices menu. Match the device by clicking on either Rev.5 FOUNDATION Fieldbus Option User's Manual Page 9

26 or After that click on ok.. 10 Right-click the new device on Project side and then select Load option The following WARNING appears. 11 Click Continue. The following dialog box appears, 12 Select the Automatically change ALL control elements to the state selected in Post Load State after load is completed checkbox and click OK. 13 On the Monitoring-Assignment window, you can notice that device on the Project- Assignment window has been loaded to the corresponding FF link. Page 10 FOUNDATION Fieldbus Option User's Manual Rev.5

27 Right-click the device, and then click Activate >> Selected Item(s) and Content(s). The device is commissioned. 14 ATTENTION Note that after importing the DD, you have to create control strategies. Control strategy A control strategy is an organized approach to define a specific process using detailed information to: Create control modules in an associated controlled environment Configure function blocks to enable control applications, and Runs in a control software infrastructure To build a control strategy, a Control Module (CM) must be created where function blocks are inserted and connected with other function blocks. Creating control strategy For information on creating control strategy, refer to the corresponding DCS document. ATTENTION When control strategy is loaded by deselecting the partial download option in the Experion, parameter check errors will appear. Ignore the errors and continue the loading of control strategy. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 11

28 3.2 Device replacement Device replacement is a common plant operation, where an old or defective device is replaced with a functional device. However, the new device that is used may not be from the same manufacturer or may not have the same device type and revision as the device being replaced. The Honeywell Experion PKS DCS gives the user a simple and easy procedure to replace FF devices called Unlike Device Replacement. This procedure can be used in situations like replacing a non-honeywell FF device with a Honeywell FF device such as the SLG 700 FF Level Transmitter in the Experion system. The Unlike Device Replacement report option in the control builder menu can be selected after clicking on the failed device in the monitoring (On-line) side. This report contains the steps to perform the device replacement procedure. The user can refer to Knowledge Builder in Experion PKS for more detailed steps Configuring the function block application process About the Function Block Application Process (FBAP) The transmitter has one resource block, four transducer blocks, and seven function blocks respectively. The DD-View feature supports all the blocks. The FBAP provides the block related information in a much more organized way. The FBAP defines blocks to represent different types of application functions. In addition, the blocks have a static revision parameter. The revision level of the static data is associated with the function block. To support tracking changes in static parameter attributes, the associated block s static revision parameter is incremented each time a static parameter attribute value is changed. In addition, the associated block s static revision parameter is incremented, if a static parameter attribute is written but the value is not changed. The FBAP supports two types of alarms: block alarms and process alarms. A block alarm is generated whenever the BLOCK_ERR has an error bit set. The types of block error for the AI block are shown in Table 3. The following alarms are supported by each function block: Block Alarms Table 3: Bit mapping of the BLOCK_ERR Block_ERR Bit Block Alarms Description 0 Other Least significant bit (LSB). NOTE: It is not supported by the transmitter. 1 Block Configuration error A feature in FEATURES_SEL is set that is not supported by features or an execution cycle in CYCLE_SEL is set that is not supported by CYCLE_TYPE. 2 Link Configuration error If the link is not configured properly. 3 Simulation Active The jumper or switch that enables simulation within the resource is ON. The individual I/O function blocks disable the simulation. Page 12 FOUNDATION Fieldbus Option User's Manual Rev.5

29 Block_ERR Bit Block Alarms Description 4 Local Override The block output is being set to track the value of the track input parameter. NOTE: It is not supported by the transmitter. 5 Device Fault State Set If the Device Fault State condition is True. NOTE: It is not supported by the transmitter. 6 Device Needs Maintenance Soon A diagnostic algorithm has found a warning condition. The NV memory is approaching the maximum number of reliable writes. NOTE: It is not supported by the transmitter. 7 Input Failure When a sensor failure (open thermocouple) or sensor conversion not accurate. 8 Output Failure Output Failure detected by this block/back calculation input has a status of Bad or Device Failure. NOTE: It is not supported by the transmitter. 9 Memory Failure A diagnostic algorithm has found a failure in memory (includes all types) and the device is still able to communicate that condition. 10 Lost Static data If the object s static data is Bad, then the object s database is set to its default values. 11 Lost NV data The NV and static parameters are saved periodically. This alarm occurs, if new data was supposed to be saved to NV at the next NV write cycle, but prevented the write due to power failure. 12 Readback Check failed This indicates the readback of the actual continuous valve or other actuator position in transducer units has failed. 13 Device needs maintenance now A diagnostic algorithm has found an invalid condition, but the device is still able to operate and communicate. The NV memory has reached the maximum number of reliable writes. NOTE: It is not supported by the transmitter. 14 Power-up The resource is performing its first normal execution, after power was applied to the device. It is not an error but generates an alarm that says that normal operation was interrupted and is now being restored. NOTE: It is not supported by the transmitter. 15 Out-of-Service The actual mode is OOS. No control function blocks are being processed. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 13

30 Process Alarms A set of alarms that indicates a process variable has exceeded a certain threshold. Process Alarm detection is based on the OUT value. The alarm limits can be configured for the following standard alarms: High (HI_LIM) High High (HI_HI_LIM) Deviation High Limit (DEV_HI_LIM) Deviation Low Limit (DEV_LO_LIM) Low (LO_LIM) Low Low (LO_LO_LIM) When the value OUT oscillates, ALARM_HYS is used to avoid alarm triggering. The priority of each alarm is set by the following parameters: HI_PRI HI_HI_PRI DV_HI_PRI DV_LO_PRI LO_PRI LO_LO_PRI The following is the order of priority for alarms. Table 4: Priority for Alarms Priority Description 0 To disable the triggered alarm, the priority of an alarm condition is changed to 0. 1 Alarm condition with a priority 1 is reported to the system, but not reported as an event and alarm 2 Alarm condition with priority of 2 is reported to the system and event, but not reported as an alarm. 3-7 Alarm conditions of priority 3 to 7 are reported as advisory alarms Alarm conditions of priority 8 to 15 are reported as critical alarms. ATTENTION Process alarms are not supported by all blocks. Page 14 FOUNDATION Fieldbus Option User's Manual Rev.5

31 3.4 Resource block The Resource block is used to describe characteristics of the Fieldbus device such as the device name, manufacturer, and serial number. The block does not contain any input or output parameters. The block contains data that is specific to the hardware associated with the resource. The resource block monitors and controls the general operation of the device hardware. For example, if the resource block is in out of service mode, it affects all the other blocks. The ITK_VER parameter is used to identify the version of the Interoperability Tester. The transmitter s Revision and Versions, and Model Number can be obtained by executing the methods available in the resource block. The block modes are used to control major states of the resource: The OOS mode stops all function block execution. The user selects the desired mode as the target. Current mode of the block is shown as the Actual mode. The AUTO mode allows normal operation of the resource Configuring the Resource block The Resource block supports scalar input and discrete input as HARD_TYPES. This parameter is a read only bit string that indicates the types of hardware that are available for this resource. The RS_STATE parameter contains the operational state of the Function Block Application for the data containing that resource block. RESTART The RESTART parameter allows degrees of initialization of the resource. Restart Operation Run (1) Restart resource (2) Restart with defaults (3) Restart processor (4) The passive state of the parameter. Discards unnecessary alarms, and also discards the resource dynamic values. Resets all configurable function block application objects to their initial value, which is their value before any configuration is done. Provides a way to press the reset button on the processor associated with the resource. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 15

32 Execution CYCLE TYPE The parameter CYCLE_TYPE is a bit string that defines the types of cycles that are available for the resource and supports scheduled and block execution. CYCLE_SEL allows the person doing the configuration to indicate that one or more of these execution types can be used by the device. MIN_CYCLE_T is the minimum time to execute a cycle; the minimum cycle time supported is 100ms. MEMORY MEMORY_SIZE is the size of the resource for configuration of function blocks; it is represented in kilobytes. SHED_RCAS and SHED_ROUT set the time limit for loss of communication from a remote device. These constants are used by each function block and are configurable values. MAX NOTIFY The MAX_NOTIFY parameter value is the maximum number of alert reports that this resource can send without getting a confirmation, and to control alert flooding, adjust the LIM_NOTIFY parameter to a lower value. If LIM_NOTIFY is set to zero, no alerts are reported. The CONFIRM_TIME parameter is the time for the resource to wait for confirmation of receipt of a report before trying again. FEATURES The bit strings FEATURES and FEATURE_SEL determine optional behaviour of the resource. FEATURES bit string defines the available features; it is read only. FEATURE_SEL is used to turn on an available feature by configuration. REPORTS If the Reports option is set in the Features bit strings, the transmitter actively sends alerts to host/master. If it is not set, the host/master must poll for alerts. Page 16 FOUNDATION Fieldbus Option User's Manual Rev.5

33 SOFTWARE and HARDWARE WRITE LOCKS There are two types of write locks: Hardware write lock and Software write lock. The software write lock is used to lock the device. The software write lock does not need a jumper. A hardware write lock is provided with a jumper in the device to perform the write lock operation. If the WRITE_LOCK parameter is set, it prevents any external change to the static or non-volatile database in the Function Block Application of the resource. Block connections and calculation results proceeds normally but the configuration is locked. A hard write lock is provided by a jumper in the device as indicated in the FEATURES bit string. Clearing WRITE_LOCK generates the discrete alert WRITE_ALM at the WRITE_PRI priority. Software write lock To activate write lock, the soft write lock supported bit in FEATURE_SEL must be set, and then set the WRITE_LOCK to locked. To deactivate write lock, set the WRITE_LOCK to unlocked. Hardware write lock To activate write lock, the hard write lock supported bit in FEATURE_SEL must be set, and additionally the write lock jumper must be in the correct position as determined by the manufacturer. Refer to the SLG700 level transmitter user s manual, 34-SL for mor information. When this is detected by the device, WRITE_LOCK is set to locked. If hard write lock is enabled in FEATURE_SEL, the configured value of soft write lock has no impact on device operation. To deactivate write lock, the jumper must be changed as FEATURE_SEL is not writeable during write lock. Once the device detects the change in jumper position, the write-lock is disabled and WRITE_LOCK is set to 1. Install Date When the device is first connected to the master/host, the time at which the device is powered up is taken as the install date. It is a read only parameter. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 17

34 Field Diagnostics The Resource block acts as a coordinator for alarms. There are four alarm parameters: Fail alarm, Offspec alarm, Maintenance alarm, and Check alarm. It contains information of device errors that are detected by the transmitter. Based on the error detected, the device provides the recommended actions; it is a read only parameter. It displays the recommended action text for the reported alarms. Table 5: Diagnostic Definitions Name Maintenance Off Specification Check Function Failed Description Although the output signal is valid, the wear reserve is nearly exhausted or a function is soon restricted due to operational conditions. For example, buildup of deposits. Indicates if the device is operating outside its specified range or internal diagnostics indicate deviations from measured or set values due to internal problems in the device or process characteristics. Output signal temporarily invalid due to on-going work on the device. Output signal invalid due to malfunction in the field device or its peripherals. FAILED_ALARMS Failed alarms indicate a failure within a device that makes the device or some part of the device nonoperational. This implies that the device needs repair and must be fixed immediately. FAILED_MAPPED parameter contains a list of failures in the device which makes the device non-operational that causes an alarm. These parameters are mapped by default with FAILED_MAPPED: Sensor Board Fault, Communication Board Fault, Sensor Communication Fault, Reference reflection not found, model number mismatch, Measurement failure/fault. FAILED_MASK parameter masks any of the failed conditions listed in FAILED_MAPPED. A bit on means that the condition is masked out from alarming and is not reported. FAILED_PRI parameter designates the alarming priority of FAILED_ALM. The default is 0. FAILED_ACTIVE parameter displays the alarms that are active. FAILED_ALM parameter indicates a failure within a device which makes the device nonoperational. Page 18 FOUNDATION Fieldbus Option User's Manual Rev.5

35 MAINT_ALARMS A maintenance alarm indicates either the device or some part of the device needs maintenance. If the condition is ignored, the device eventually fails. MAINT_MAPPED parameter contains a list of conditions indicating either the device or some part of the device needs maintenance soon. If the condition is ignored, the device eventually fails. The following are the seven parameters mapped by default with MAINT_MAPPED: Field background load error Surface Signal Strength Fault Surface Signal Quality Fault Interface Signal Strength Fault Interface Signal Quality Fault Sensor Param Write Failure Background Not Set Field Background not compatible Un-reliable Sensor Communication MAINT_MASK parameter masks any of the failed conditions listed in MAINT_MAPPED. A bit on means that the condition is masked out from alarming and is not reported. MAINT_PRI designates the alarming priority of the MAINT_ALM. The default is 0. MAINT_ACTIVE parameter displays the alarms that are active. MAINT_ALM parameter indicates that the device needs maintenance. If the condition is ignored, the device fails. CHECK_ALARMS It indicates that the output signal is temporarily invalid due to on-going work on the device. CHECK_MAPPED parameter contains a list of informative conditions that do not have a direct impact on the device's primary functions. CHECK_MASK parameter masks any of the failed conditions listed in CHECK_MAPPED. a bit on means the condition is masked out from alarming and is not reported. CHECK_PRI parameter designates the alarming priority of the CHECK_ALM. The default is 0. CHECK_ACTIVE parameter displays the check alarms that are active. CHECK_ALM parameter indicates check alarms. These conditions do not have a direct impact on the process or device integrity. DEVICE_RESTART_REQUIRED parameter is used to ensure that all tuning parameter modifications have been activated in the sensor board, a reset is required. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 19

36 OFFSPEC_ALARMS Indicates if the device is operating outside its specified range or internal diagnostics indicates deviations from measured or set values due to internal problems in the device or process characteristics. OFFSPEC_MAPPED parameter contains a list of informative conditions that do not have a direct impact on the device's primary functions. Following are the OFFSPEC_MAPPED conditions: Low Supply Voltage High Supply Voltage PV out of Range Comm. Board Over Temperature Sensor Over Temperature Surface Blocking Distance High Surface Blocking Distance Low Interface Blocking Distance high Interface Blocking Distance low OFFSPEC_MASK parameter masks any of the failed conditions listed in OFFSPEC_MAPPED. A bit on means the condition is masked out from alarming and is not reported. OFFSPEC_PRI parameter designates the alarming priority of the OFFSPEC_ALM. The default is 0. OFFSPEC_ACTIVE parameter displays the offspec alarms that are active. OFFSPEC_ALM parameter indicates offspec alarms. These conditions do not have a direct impact on the process or device integrity. If connect R101 sensor with R102 FF comm then for two liquid flooded application host side user can observe only surface blocking distance high/low alarm even if interface blocking distance high/low alarms generated. Page 20 FOUNDATION Fieldbus Option User's Manual Rev.5

37 RECOMMENDED_ACTIONThe RECOMMENDED_ACTION parameter displays a text string that gives a recommended course of action to take based on which type and which specific event of the alarms is active. FD_SIMULATE When simulation is enabled the Field Diagnostics conditions are taken from the Diagnostic Simulate Value, or else the conditions are taken from Diagnostic Value, and the RECOMMENDED_ACTION parameter displays the text Simulation Active. ATTENTION Note that FD_SIMULATE can be enabled only if the simulation jumper is enabled in the device. For more information refer section 7.6 MAINTENANCE_MODE It indicates if the device is available for maintenance. When the resource block is in OOS mode, MAINTENANCE_MODE parameter displays the text as 'Chk with Oper' i.e., the device is in process and is not available for maintenance. When the resource block is in AUTO mode, MAINTENANCE_MODE parameter displays the text as Avail for Maint' i.e., the device is out of process and is available for maintenance. The same text is displayed on the Advanced Display. 'Chk with Oper'- Check with operator to determine availability. Avail for Maint'- The device is available for maintenance. SERIAL_NO The SERIAL_NO parameter shows the device serial number as obtained from the Sensor housing. COMM_SERIAL_NO The COMM_SERIAL_NO parameter is the serial number of the Communication board. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 21

38 Parameter List Parameter ST_REV TAG_DESC STRATEGY ALERT_KEY MODE_BLK BLOCK_ERR RS_STATE TEST_RW DD_RESOURCE MANUFAC_ID DEV_TYPE DEV_REV CAPABILITY_LEV DD_REV GRANT_DENY HARD_TYPES RESTART FEATURES FEATURE_SEL CYCLE_TYPE CYCLE_SEL MIN_CYCLE_T MEMORY_SIZE Table 6: Resource block parameters Description The revision level of the static data associated with the function block. The user description of the application of the block. Used to identify grouping of blocks. The identification number of the plant unit. The actual, target, permitted, and normal modes of the block. Reflects the error status associated with the hardware or software components associated with a block. It is a bit string, so that multiple errors may be shown. Indicates the State of the function block application state machine. Read/write test parameter is used only for conformance testing. String identifying the tag of the resource, which contains the Device Description for the resource. Manufacturer identification number is used by an interface device to locate the DD file for the resource. Manufacturer model number associated with the resource. It is used by interface devices to locate the DD file for the resource. Manufacturer revision number associated with the resource. It is used by an interface device to locate the DD file for the resource. The Capability Level of the Device. Revision of the DD associated with the resource. It is used by the interface device to locate the DD file for the resource. Options for controlling access of host computer and local control panels to operating, tuning and alarm parameters of the block. The types of hardware available as channel numbers. The supported hardware types are scalar input and discrete input. Allows a manual restart to be initiated. Used to show supported resource block options. The supported features are: REPORT, SOFT_WRITE_LOCK, HARD_WRITE_LOCK, and MULTI_BIT_ALARM. Used to select resource block FEATURE_SEL options Identifies the block execution methods available for this resource. The supported cycle types are: Scheduled and Block Execution. Used to select the block execution method for this resource. Time duration of the shortest cycle interval of which the resource is capable. Available configuration memory in the empty resource. It must be checked before starting a download. Page 22 FOUNDATION Fieldbus Option User's Manual Rev.5

39 Parameter NV_CYCLE_T FREE_SPACE FREE_TIME SHED_RCAS SHED_ROUT FAULT_STATE SET_FSTATE CLR_FSTATE MAX_NOTIFY LIM_NOTIFY CONFIRM_ TIME WRITE_LOCK UPDATE_EVT BLOCK_ALM ALARM_SUM ACK_OPTION WRITE_PRI WRITE_ALM ITK_VER Description Minimum time interval specified by the manufacturer for writing copies of NV parameters to non-volatile memory. Zero implies it is never automatically copied. At the end of NV_CYCLE_T, only those parameters that have changed need to be updated in NVRAM. Percent of memory available for further configuration. Zero in preconfigured resource. Percent of the block processing time that is free to process additional blocks. Time duration at which to give up on computer writes to function block RCas locations. Shed from RCas does not happen, if SHED_RCAS = 0. Time duration at which to give up on computer writes to function block ROut locations. Shed from Rout does not happen, if SHED_ROUT = 0. Condition set by loss of communication to an output block, fault promoted to an output block or a physical contact. When Fault State condition is set, output function blocks perform their FSTATE actions. Allows the Fault State condition to be manually initiated by selecting Set. Writing a Clear to this parameter removes the device fault state if the field condition, if any has cleared. Maximum numbers of unconfirmed notify messages possible. Maximum numbers of unconfirmed alert notify messages allowed. The time the resource waits for confirmation of receipt of a report before trying again. Retry does not happen when CONFIRM_TIME=0. If set, no writes from anywhere are allowed, except to clear WRITE_LOCK. Block inputs continues to be updated. This alert is generated by any change to the static data. The BLOCK_ALM is used for configuration, hardware, and connection failure or system problems in the block. The cause of the alert is entered in the subcode field. The first alert to become active sets the Active status in the Status attribute. When the Unreported status is cleared by the alert reporting task, another block alert is reported without clearing the Active status, if the subcode has changed. The current alert status, unacknowledged states, unreported states, and disabled states of the alarms associated with the function block. Selection of whether alarms associated with the block is automatically acknowledged. Priority of the alarm generated by clearing the write lock. This alert is generated if the write lock parameter is cleared. Major revision number of the interoperability test case used in certifying this device as interoperable. The format and range are controlled by the Fieldbus Foundation. The current ITK version is Rev.5 FOUNDATION Fieldbus Option User's Manual Page 23

40 Parameter FD_VER FD_RECOMMEN_ACT FD_FAIL_PRI FD_FAIL_MAP FD_FAIL_MASK FD_FAIL_ACTIVE FD_FAIL_ALM FD_MAINT_PRI FD_MAINT_MAP FD_MAINT_MASK FD_MAINT_ACTIVE FD_MAINT_ALM FD_OFFSPEC_PRI FD_OFFSPEC_MAP FD_OFFSPEC_MASK FD_OFFSPEC_ACTIVE FD_OFFSPEC_ALM FD_CHECK_PRI FD_CHECK_MAP Description A parameter equal to the value of the major version of the Field Diagnostics specification that the device is designed for. Enumerated list of recommended actions displayed with a device alert. Designates the alarming priority of the FAIL_ALM. The valid range is Mapped FAIL_ALM alarm conditions, and corresponds bit for bit to the FAIL_ACTIVE. A bit on means that the corresponding alarm condition is Mapped and it is detected. A bit off means the corresponding alarm condition is disabled and is not detected. Mask of FAIL_ALM. It corresponds to the bit of bit to FAIL_ACTIVE. A bit on means that the condition is masked out from alarming. Enumerated list of failure conditions within a device. Alarm indicating a failure within a device which makes the device nonoperational. Designates the alarming priority of the MAINT_ALM. The valid range is Mapped MAINT_ALM alarm conditions and corresponds bit for bit to the MAINT_ACTIVE. A bit on means that the corresponding alarm condition is Mapped and is not detected. A bit off means the corresponding alarm condition is disabled and is not detected. Mask of MAINT_ALM. It corresponds to the bit of bit to MAINT_ACTIVE. A bit on means that the condition is masked out from alarming. Enumerated list of maintenance conditions within a device. Alarm indicating the device needs maintenance soon. If the condition is ignored, the device eventually fails. Designates the alarming priority of the OFFSPEC_ALM. The valid range is Mapped OFFSPEC_ALM alarm conditions. Corresponds bit for bit to the OFFSPEC_ACTIVE. A bit on implies that the corresponding alarm condition is Mapped and detected. A bit off means the corresponding alarm condition is disabled and is not detected. Mask of OFFSPEC_ALM. It corresponds to the bit of bit to OFFSPEC_ACTIVE. A bit on implies that the condition is masked out from alarming. Enumerated list of offspec conditions within a device. Alarm indicating offspec alarms. These conditions do not have a direct impact on the process or device integrity. Designates the alarming priority of the CHECK_ALM. The valid range is Mapped CHECK_ALM alarm conditions. Corresponds bit for bit to the CHECK_ACTIVE. A bit on means that the corresponding alarm condition is Mapped and is detected. A bit off means the corresponding alarm condition is disabled and is not detected. Page 24 FOUNDATION Fieldbus Option User's Manual Rev.5

41 Parameter FD_CHECK_MASK FD_CHECK_ACTIVE FD_CHECK_ALM FD_SIMULATE HARDWARE_REV SOFTWARE_REV COMPATIBILITY_REV Description Mask of CHECK_ALM. It corresponds to the bit of bit to CHECK_ACTIVE. A bit on means that the condition is masked out from alarming. Enumerated list of check conditions within a device. Alarm indicating check alarms. These conditions do not have a direct impact on the process or device integrity. When simulation is enabled, the Field Diagnostics conditions are taken from Diagnostic Simulate Value, or else the conditions are taken from Diagnostic Value. The hardware revision number of the communications module. The software revision number of the communications module. The compatibility revision number of the communications module. MODEL_KEY The key number of SLG 700 level transmitter (Example: SLG 700). MOD_PART_1 MOD_PART_2 HW_SIMULATE_JUMP ER_STATE INSTALL_DATE MAINTENANCE_MODE SERIAL_NO COMM_SERIAL_NO First part of the Material of Construction Information. Second part of the Material of Construction Information. State of Hardware Simulation Jumper (Enabled / Disabled). The date and time when the device is installed in the field. The date and time is directly acquired from the FF Host. It indicates whether device is ready for maintenance.'chk with Oper'- Check with operator to determine availability. Avail for Maint'- The device is available for maintenance. Serial number of the device. Serial Number of the Communication Module. Attributes Supported Modes Alarm Types The block supports the following modes: AUTO (Automatic) OOS (Out of Service). The block supports standard block alarms (see section 3.2), and added to it, a discrete alarm for write lock. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 25

42 3.5 Level Transducer block The Level Transducer block has all the basic configuration parameters and functions required to measure and calculate the level. The values that are measured and calculated by the transducer block are available as output values and are called as channels. The measured values can be read cyclically from function blocks. See Table 7 for list of parameters. Figure 2: Level Transducer Block Execution The Level Transducer block supports the following process variables: Product Level Product Level % Distance To Product Product Level Rate Vapor Thickness Vapor Thickness % Interface Level Interface Level % Distance To Interface Interface Level Rate Upper Product Thickness Product Volume Vapor Volume Lower Product Volume Upper Product Volume Page 26 FOUNDATION Fieldbus Option User's Manual Rev.5

43 Parameter List Note: To configure level transducer block parameters from the advanced display, keep both level transducer block and auxiliary transducer block in OOS mode. More details of the parameters can be found in 34-SL Table 7: Level Transducer block parameters Parameter Description ST_REV TAG_DESC STRATEGY ALERT_KEY MODE_BLK BLOCK_ERR UPDATE_EVT BLOCK_ALM SENSOR_RANGE PRODUCT_LEVEL PRODUCT_LEVEL_RANGE DISTANCE_TO_PRODUCT PRODUCT_LEVEL_RATE PRODUCT_LEVEL_RATE_RAN GE The revision level of the static data associated with the function block. The user description of the application of the block. Used to identify grouping of blocks. The identification number of the plant unit. The actual, target, permitted, and normal modes of the block. Reflects the error status associated with the hardware or software components associated with a block. It is a bit string, so that multiple errors may be shown. This alert is generated by any change to the static data. The BLOCK_ALM is used for all configuration, hardware, and connection failure or system problems in the block. The cause of the alert is entered in the subcode field. The first alert to become active sets the Active status in the Status attribute. After the Unreported status is cleared by the alert reporting task, another block alert may be reported without clearing the Active status, if the subcode has changed. Display range supported by Level Sensor Displays product level The product level range is the user desired valid range for the level which is limited by the maximum product height value.it also contains the units for Product level, which Is used by all the derived parameters. The supported units are: m cm mm in ft The distance measured from sensor to the top level of the product. The Rate of change of level. The Rate of change of level is limited by -250 m/s to +250 m/s. It also contains unit for Prodcut Level Rate. The supported units are: ft/s m/s in/min m/h ft/min in/s Rev.5 FOUNDATION Fieldbus Option User's Manual Page 27

44 Parameter INTERFACE_LEVEL INTERFACE_DISTANCE INTERFACE_LEVEL_RATE VAPOR THICKNESS PRODUCT_VOLUME PRODUCT_VOLUME_RANGE ELECTRONIC TEMPERATURE VAPOR_VOLUME UPPER_PRODUCT_VOLUME LOWER_PRODUCT_VOLUME UPPER_PRODUCT_THICKNES S TRANSMITTER_MODEL (read only) SENSOR_CONNECTION (read only) Description Displays interface level. The Range and unit selected for Product Level will automatically get reflected for Interface Level. The distance of the interface level from the sensor. The rate of change of the interface level.the Range and unit selected for Product Level rate will automatically get reflected for Interface Level rate. The height of the vapor/air inside the tank. The volume of the product is calculated according to the volume calculation type selected by the RLAUXTB (Transducer Block). The volume calculation may be as per the Ideal Tank Shape or Strapping Table. Refer Table 8 for more details on Volume calculations. The product volume range is the range from 0 to the maximum tank volume size considering maximum product height as the tank height. It also contains unit for product volume. The supported units are: L ft3 in3 gallon ImpGal bbl bbl liquid yd3 m3 The electronic temperature of the communication board. It also contains the unit for temperature. The supported units are: C F The volume of the vapor / air inside the tank. The upper liquid volume which is obtained by subtracting the lower liquid volume from the product volume. The lower liquid volume calculated using the interface level The height of the upper liquid when two liquids option is selected in Measured Product. SLG720: Standard SLG726: High Temperature and High Pressure Direct Remote Page 28 FOUNDATION Fieldbus Option User's Manual Rev.5

45 Parameter MEASURED_PRODUCT Measured product Type 1. Single Liquid 2. Two Liquid Non Flooded 3. Two Liquid Flooded Description Single Liquid 2 Liquid Flooded 2 Liquid Non Flooded LOWER_PRODUCT_DC UPPER_PRODUCT_DC VAPOR_DC SENSOR_HEIGHT Dielectric constant value of Lower Product to be measured if two products exist in the tank Dielectric constant of upper product to be measured. For single liquid this is Product DC. Dielectric constant of the vapor. The height from the reference point at which sensor is mounted A represents Sensor Height MAX_PRODUCT_HEIGHT Maximum Product Height can be equal to or less than the Sensor Height. It is the valid height till which the liquid raised can be measured. B represents Max Product Height/ Max Product Level Rev.5 FOUNDATION Fieldbus Option User's Manual Page 29

46 Parameter LEVEL_OFFSET Description Residual amount of liquid in the tank and the product level is corrected according to this offset C represents Level Offset PROBE_TYPE PROBE_MATERIAL PROBE DIAMETER Choices: 1. Custom 2. Coax 3. Rod 4. Wire 5. Multi twist wire Choices: /316L Stainless Steel 2. PFA Coated Stainless Steel 3. C-276 Nickel Alloy Lists options to choose from like Custom, 8mm, 12mm, 16mm, 22mm etc. PROBE_LENGTH The allowed probe length range is 0-50m A represents Probe Length PROBE_END_TYPE Probe End types: 1. Clamp 2. Weight 3. Loop 4. None Page 30 FOUNDATION Fieldbus Option User's Manual Rev.5

47 Parameter CENTERING_DISK_TYPE CENTERING_DISK_DIAMETER Description Choices: /316L Stainless Steel 2. PTFE 3. C-276 Nickel Alloy 4. None The drop down lists the selection options: PROBE_PROPAGATION 0.9 to 1.1 (refer to Probe Propagation Factor:on page 138) MOUNTING_LOCATION MOUNTING_HEIGHT MOUNTING_DIAMETER MOUNTING_ANGLE BLOCKING_DISTANCE_HIGH Tank Bracket Bypass Nozzle Stillwell Unknown The mounting height can be configured only when the mounting type is selected as Nozzle or Standpipe or Stillwell. The allowed range is 0-75m. The mounting diameter can be configured only when the mounting type is selected as Nozzle or Standpipe or Stillwell. The allowed range is 0-1m. The mounting angle can be configured only when the mounting type is selected as Bracket or Direct or Nozzle. The allowed range is The minimum allowed blocking distance high is configuration dependant (see 34-SL-25-11) and the maximum is 3 m B represents Blocking Distance High Region Rev.5 FOUNDATION Fieldbus Option User's Manual Page 31

48 Parameter BLOCKING_DISTANCE_LOW Description The minimum allowed blocking distance low is configuration dependant. The maximum is 3 m C represents Blocking Distance Low Region MAX_FILL_EMPTY_SPEED LOWER_PRODUCT_ATTENUA TION UPPER_PRODUCT_ATTENUA TION Enter Maximum filling and emptying speed, Range is 0.04m/s- 0.2m/s The value can be between The value can be between VAPOR_ATTENUATION The value can be between PROCESS_CONN_TYPE BACKGROUND_TYPE FIELD_BACKGROUND FIELD_BACKGROUND_CAPTU RE_STATUS FIELD_BACKGROUND_CAPTU RE_PROGRESS Threaded Flanged Factory Field Obstacle Cancel Get Status Capture Get Additional Status Capture Not Available Capture In Progress Capture Cancelled Capture Failed Capture Successful Displays the percent of the Field Background Capture status. Page 32 FOUNDATION Fieldbus Option User's Manual Rev.5

49 Parameter FIELD_BACKGROUND_ADD_S TATUS FULL_TANK_DETECT SENSOR_TYPE SENSOR_SN SENSOR_HW_REV SENSOR_FW_VER ASIC_SLOPE ASIC_OFFSET CHARACTER_DATE MATERIAL_OF_CON_SEAL MATERIAL_OF_CON_PROBE DYNAMIC_BACKGROUND_UP DATE Description Can capture the additional status for the Field Background Add Status parameter. Additional Statuses: Capture completed successfully without any error or warning Capture completed successfully but length had to be trimmed due to short probe length Capture completed successfully but length had to be trimmed due to background buffer size Capture completed successfully but a level peak was included in the background Capture cancelled by the user Capture aborted due to invalid configuration Capture aborted after multiple failed attempts Capture aborted since reference reflection is not found Capture failed due to non-volatile RAM write error Full tank detection: DISABLED ENABLED Displays Type of the Sensor. In this case it will display as Guided wave sensor Displays sensor serial number Sensor Board Hardware Revision number Sensor Board Firmware Version number Displays ASIC_SLOPE Displays ASIC_OFFSET Characterization Date of the Level Sensor Material of Construction of Seal Material of Construction of Probe Dynamic background update: OFF ON BACKGROUND_LENGTH BACKGROUND_LENGTH_TYP E The value can be between 0.0 toprobe length value (depending on background type). The Options are: Level background scan is done considering the Value provided for background length as Product Level Surface background scan is done considering the value provided for background length as distance to product Rev.5 FOUNDATION Fieldbus Option User's Manual Page 33

50 Parameter CAPTURE_BACKGROUND_TY PE ECHO_LOST_TIMEOUT Description Not Used Field background is not used Field Field background is used for background capture Obstacle Obstacle removal is used for background capture The value can be between in seconds Attributes Supported Modes The block supports the following modes: AUTO (Automatic) OOS mode (Out of Service) Alarm Types The block supports standard block alarms (see section 3.2). Page 34 FOUNDATION Fieldbus Option User's Manual Rev.5

51 3.6 Auxiliary Transducer Block Auxiliary Transducer block provides advanced configuration support of Linearization, Volume and Correlation Algorithm. It also provides support to view the Echo curve Linearization When the Linearization option is enabled, the transmitter s measured values are replaced by corresponding user-specified corrected values from the linearization table. The Linearization Table consists of Measured_Level1 Table, Measured_Level2 Table, Corrected_Level1 Table and Corrected_Level2 Table. See Table 9 for more detail. Before enabling Linearization option linearization table must be configured. Tables can be configured either in dry or wet. Wet Linearization: When the measured level for the tank reaches a level where the corresponding corrected level is known then we can use Wet linearization. If Linearization Type is Wet, then it is allowed to enter/correct single entry in the Linearization table at a time using method. While executing Level Wet Linearization Method, Measured Level is cannot be edited by user. Value of Product Level or value of Interface Level (Measured Product Type is Two Liquid Flooded) is copied in the Measured Level table based on the selected Linearization Table Index. Linearization table entry is limited by value of Linearization table Size. If entry exceeds linearization size, the Parameter Check Error is triggered. Dry Linearisation: The user can do manual entry in pairs of Measured Level and a corresponding Corrected Level in Linearisation Table to enable Dry Linearisation. Please refer Table 8: Auxiliary Transducer block parameters for more details on Linearization. Note: The Level Linearization feature does not affect the values reported for the Distance to Product and Distance to Interface device variables. If Level Linearization is enabled, the distance and associated level are no longer described solely by the basic geometry and it is possible that the Product Level will not be equal to (Sensor Height Level Offset Distance to Product). Likewise for the Interface if is being calculated Description of correlation algorithm Each object in the tank (reference, surface, end of probe, interface (for two liquids), process connector (for remote mount) reflects an echo wave with its own signature or model shape. Each model s shape is described with parameters such as width, gain (amplitude), and attenuation. These models are configured at the factory according to the customer s specified configuration. The correlation algorithm searches each part of the captured echo curve looking for the model echo from each object and, if found, reports the distances in the DTM. The models will work as configured in the factory, assuming the customer s ordered configuration is correct. If for some reason the surface or other objects are not being detected correctly try the following steps. Often these steps will fix the problem. 1. Check the basic configuration settings and adjust if necessary. 2. Check advanced configuration settings, especially probe settings and adjust if necessary. 3. Read Echo curve using FDM/DTM for troubleshooting. Based on the Echo signal, required correlation algorithm configuration changes should be adjusted if there is a measurement problem. Refer to section Echo Curve. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 35

52 Echo Curve Types The Honeywell SLG 700 captures four types of echo curves: Windowed Echo Curve Full Echo Curve Processed Full Echo Curve Background Substraction Array Echo Curve ATTENTION When DTM is opened, Echo curve page under RLAUXTB will take about 30 sec to update parameter list during the update time the page will show blank. Windowed Echo Curve: In this echo curve type, data is shown only in the areas where the transmitter is currently searching for reflections. On short probes this will cover the full length of the probe but on longer probes where the transmitter tracks the surface/interface reflections as they move, there will be areas with no data visible. Subtraction of background reflections near the reference plane has been applied to this data array so unwanted reflections, due to a nozzle for instance, will not be visible. This type of echo curve is useful for troubleshooting the Correlation Algorithm settings as it represents the data on which the correlation algorithm works. Figure 3: Windowed Echo Curve Page 36 FOUNDATION Fieldbus Option User's Manual Rev.5

53 Full Echo Curve: This echo curve type includes data collected over the full length of the probe. Subtraction of background reflections near the reference plane is not applied so all physical reflections, due to a nozzle for instance, will be visible. This type of echo curve is useful for troubleshooting problems in the region near the reference plane. Figure 4: Full Echo Curve Note: A Full Echo Curve will likely take much longer to capture than a Windowed Echo Curve. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 37

54 Processed Full Echo Curve: Similar to the Full Echo Curve type, but with subtraction of background reflections near the reference plane applied. This type of echo curve is useful for process and/or algorithm troubleshooting. Figure 5: Processed (Full) Echo Curve Background Subtraction Array: Selecting this echo curve type allows the data array that is used to remove unwanted reflections in the region near the reference plane to be uploaded and viewed. This type of echo curve is useful for troubleshooting problems in the region near the reference plane and checking whether any obstacles (if present) are found at expected locations. Figure 6: Background Subtraction Array Page 38 FOUNDATION Fieldbus Option User's Manual Rev.5

55 Using Echo Curve for Troubleshooting The following sections describe how to use the Echo Curve for troubleshooting. Based on the Echo signal, required correlation algorithm configuration changes should be adjusted if there is a measurement anomaly. Background Subtraction Array: Selecting this echo curve type allows the data array that is used to remove unwanted reflections in the region near the reference plane to be uploaded and viewed. This type of echo curve is useful for troubleshooting problems in the region near the reference plane. Reading Echo Curve SLG 700 Fieldbus models support DTM running on FDT or FDM Host. Either FF DTM or FDM can be used to read the Echo signal. ATTENTION SLG700 FF DTM should be installed before proceeding Echo read. The following section describes reading the echo signal using FF DTM and storing it in text file in the FDT Host environment. Navigate to the Level Auxiliary block and click the Echo Curve tab. Note: It may take few seconds to load the Echo Curve page. Configure the start and end distance of the probe for which the echo signal is required, Resolution and Echo Type. Set the block to Auto mode and click Echo Read button, to read echo signal for the configured distance. Once reading is complete, it will display the Echo wave in the format as shown in the figure below. Note: Echo curves supports a maximum of 1000 points. Echo curve points are calculated based on the start distance, end distance and resolution. Parameter below the echo curve will be updated once echo curve is plotted Rev.5 FOUNDATION Fieldbus Option User's Manual Page 39

56 Export Echo Curve Data The Echo Curve generated from the device using DTM can be exported & stored in Text file format by selelcting Echo curve export opion shown below. ATTENTION This Echo data is stored as Text file with specific format. Don't try to modify the file. ATTENTION FF device Width, Attenuation, Gain value of Surface and Interface should be configured in the HART DTM/Field Set Up Tool (in offline mode) before proceeding model shape adjustment. Page 40 FOUNDATION Fieldbus Option User's Manual Rev.5

57 Import Echo Curve Data in HART DTM and calculate the model. The exported data using FF DTM can be imported in the HART DTM/Field Set up Tool in offline mode to analyze further and adjust the model shapes of the correlation algorithm. Download HART DTM from: US/explore/products/instrumentation/process-level-sensors/Pages/smartline-level-transmitter.aspx Go to Software tab ATTENTION SLG 700 HART DTM/Field Set Up Tool should be installed before proceeding Echo Import feature. How to open the HART DTM in offline mode: Add the HART communication DTM to HOST PC and then add device DTM (approriate Revision) under COM1. Both Com DTM & device DTM should be in disconnected mode. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 41

58 Right click on device DTM, select parameterization under parameter. Once DTM is opened, click on the "Proceed to algorithm tuning" tab. select Open File option to select the Echo data text file exported using FF DTM and enter the correlation algorithm parameter for surface and interface models of FF device before adjusting the model shapes. Page 42 FOUNDATION Fieldbus Option User's Manual Rev.5

59 The following section describes how to do configure the Correletaion Algorthim (model type). Rev.5 FOUNDATION Fieldbus Option User's Manual Page 43

60 How to configure the Correletaion Algorthim (model type) Under normal circumstances, the transmitter will automatically find the level of the surface and interface (if applicable) using the configuration that was shipped from the factory: 1. Step through the basic configuration and make sure that all entries are correct. 2. Review the Probe Parameters under Advanced Configuration and ensure that all entries are correct. 3. Capture an echo curve. 4. Navigate to the Correlation Algorithm page and load the captured echo curve. 5. Select the reflection model (Reference, Surface, Interface or End of Probe). 6. The selected model appears on the upper graph as a brown line to distinguish it from the blue echo curve. 7. Click and drag cursor to move model over relevant part of the curve. The example curve shown in the figure below represents a scenario of a two liquid non-flooded application with oil on top of water. In the example the transmitter has correctly located the surface of the upper oil layer, but has failed to find the interface boundary between the oil and water due to a model miss-match. In this case the Interface model should be selected and dragged to a location to the right of the Surface reflection where the interface is known to be. 8. The closer the model shape matches the curve shape, the lower the Objective Function value, as shown in the lower right-hand corner below the bottom graph. In the example, the brown Interface model does not match the blue curve at the selected position (240 cm) so the Objective Function value is high (greater than 1). Figure 7: Adjusting the Correlation Algorithm Note: The numbers in red circles in the images refer to the step number. Page 44 FOUNDATION Fieldbus Option User's Manual Rev.5

61 9. Zoom view: Use the mouse to draw a zoom box around the model, then click and drag the model position for best match to the curve. Notice that by dragging the model over the similarly shaped blue curve at 338cm, the Objective Function value has decreased from to 0.658, indicating a higher correlation between the shapes. TIP: By slowly dragging the model back and forth over the curve you can home in on the position with the lowest Objective Function value. Figure 8 Zoom View 10. Notice at previous step, the brown model line s amplitude is slightly larger than the blue curve s amplitude. To reduce the model s amplitude to better match the blue curve, decrease the Gain. By gradually decreasing Gain from 5122 to 3322 the model more closely matches the blue curve while the Objective Function value has improved from to TIP: By using the up and down arrows to increase and decrease Gain you can home in on the lowest Objective Function value. 11. In the bottom graph of the Objective Function the red line indicates the Threshold. The brown curve of the Objective Function must dip below this red Threshold line to be recognized. If the Threshold is too low, increase its value to raise the red line slightly above the dip as shown. Note that there should be only one dip that falls below the Threshold line on the graph. If there are more than one, then the transmitter may report incorrect position for the reflection. Note In this example, the model mismatch was exaggerated to better illustrate the process. See step 13 for the final model parameters. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 45

62 Figure 9: Adjusting the Gain Parameter 12. Record the values and go back to Filedbus DTM Comfigure Echo. Check that the correct Reference, Surface and Interface measurements were found. 13. If the algorithm is still not finding a match then the models other parameters, Width and Attenuation, can be adjusted to get an even closer match between the model and the curve. Note that it may be necessary to collect echo curves with various levels of product to ensure that the reflection model provides a good match through the full range. Figure 10 shows the example with the Gain, Width and Attenuation parameters optimized to give and Object Function reading of Figure 10: Adjusting the Width and Attenuation Parameters Page 46 FOUNDATION Fieldbus Option User's Manual Rev.5

63 How to adjust model shapes Measured Products Single Liquid Two Liquid Non-Flooded Two Liquid Flooded Model to be Corrected Surface Surface Interface Interface Refer to the figures and callout descriptions. 1. Select model wave shape (Reference, Surface, Interface). 2. Selected model appears on the graph in brown to distinguish it from the blue echo curve. 3. Click and drag cursor to move the model over the relevant part of the curve. In this example, the Surface model is being used, therefore drag it to the part of the curve where the Surface would be expected (to the right of the Reference). 4. The closer the model shape matches the curve shape, the lower the Objective Function value. In the example, the brown Surface model does not match the blue curve at that position (around 570cm) so the Objective Function value is high (greater than 1). Adjusting the Correlation algorithm based on the new model Adjust the width, gain, attenuation parameters using FF DTM based on the surface and interface the new model(s) data calculated using HART DTM/Field Set up Tool. Read the echo curve again as described above to adjust the objects models further if any object is still not being read correctly. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 47

64 Parameter List Table 9: Auxiliary Transducer block parameters Parameter Name Description ST_REV TAG_DESC STRATEGY ALERT_KEY MODE_BLK BLOCK_ERR UPDATE_EVT BLOCK_ALM PRODUCT_LEVEL LEVEL_RANGE INTERFACE_LEVEL PRODUCT_VOLUME PRODUCT_VOLUME_RANGE LINEARIZATION_TYPE LINEARIZATION_DATE The revision level of the static data associated with the function block. The user description of the application of the block. Used to identify grouping of blocks. The identification number of the plant unit. The actual, target, permitted, and normal modes of the block. Reflects the error status associated with the hardware or software components associated with a block. It is a bit string, so that multiple errors may be shown. This alert is generated by any change to the static data. The BLOCK_ALM is used for all configuration, hardware, and connection failure or system problems in the block. The cause of the alert is entered in the subcode field. The first alert to become active sets the Active status in the Status attribute. After the Unreported status is cleared by the alert reporting task, another block alert may be reported without clearing the Active status, if the subcode has changed. This product level follows the product level of Level Transducer Block This product level Range follows the product level Range of Level Transducer Block This interface level follows the interface level of Level Transducer Blok This product volume follows the product volume of Level Transducer Block This product volume range follows the product volume of Level Transducer Block The user can Linearize the table using following methods 1. Dry 2. Wet The Date of Linearization can be updated whenever Linearization is done, the format is MM/DD/YYYY HH:MM:SS Page 48 FOUNDATION Fieldbus Option User's Manual Rev.5

65 Parameter Name LINEARIZATION LINEARIZATION_TABLE_SIZE CORRECTED_LEVEL1 CORRECTED_LEVEL2 MEASURED_LEVEL1 MEASURED_LEVEL2 Description An option to enable/disable the usage pf Linearization table, When the Linearization Table is under modification, this option should be selected as Disabled. After updating the Linearization Table Size, Measured Level and Corrected Level the Linearization option should be enabled. If all the entries mentioned above are valid then user is allowed to select the Enable option, otherwise it will throw the Parameter Check Error The number of levels user wants to linearize can be updated here. This should match with the number of entries in the Linearization table. It should not be zero and maximum value is 32 This is the first half part of the Corrected Level Linearization Table which supports entries for 16 elements. It can be updated for Linearization type DRY or WET Linearization table entry is limited by the Linearization Table Size. This is the second half part of the Corrected Level Linearization Table which supports entries for 16 elements. It can be updated for Linearization type DRY or WET. The Linearization table entry is limited by the Linearization Table Size. This is the first half part of the Measured Level Table which supports entries for 16 elements. The user can modify it manually when Linearization Type is Dry. If Linearization Type is Wet, then it is allowed to enter/correct single entry in the Linearization table at a time using method. While executing Level Wet Linearization Method, Measured Level cannot be edited by user. Value of Product Level or value of Interface Level (Measured Product Type Two Liquid Flooded) is copied in the Measured Level Table based on the selected Linearization Table Index. Linearization table entry is limited by value of Linearization table Size. If the entry exceeds linearization size, the Parameter Check Error is triggered. This is the second half part of the Measured Level Table which supports entries for 16 elements. The user can modify it manually when Linearization Type is Dry. If Linearization Type is Wet, then it is allowed to enter/correct single entry in the Linearization table at a time using method. While executing Level Wet Linearization Method, Measured Level is cannot be edited by user. Value of Product Level or value of Interface Level (Measured Product Type is Two Liquid Flooded) is copied in the Measured Level table based on the selected Linearization Table Index. Linearization table entry is limited by value of Linearization table Size. If entry exceeds linearization size, the Parameter Check Error is triggered. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 49

66 VOL_CAL_TYPE Parameter Name Description Calculation method for Volume calculation 1. Strapping Table 2. Ideal Tank Shape Note 1: The Strapping Table can be selected only when the Volume Strapping Table size, Level and Volume tables are valid. The strapping size should not be zero and the level & volume tables should be in proper order to select the Strapping Table option. The Ideal Tank Shape can be selected and the relevant tank configurations can be updated. Note 2: Select Volume Calculation Type as None if Volume related device variables (Product Volume) are not required to be measured and monitored by device. Note 3: The SLG 700 directly measures only distance and related quantities (level, percent of range, etc.). The calculation of volume is based on measured level and additional tank geometry measurements. Reliable volume calculation requires correct measurements of tank geometry. Page 50 FOUNDATION Fieldbus Option User's Manual Rev.5

67 Parameter Name IDEAL_TANK_SHAPES Description The supported Ideal Tank Shapes are 1. SPHERE 2. CUBIC 3. HORIZONTAL BULLET 4. VERTICAL CYLINDER 5. HORIZONTAL CYLINDER, 6. RECTANGLE 7. VERTICAL BULLET Sphere Cubic Horizontal Bullet Vertical Cylinder Horizontal Cylinder Rectangle Vertical Bullet TANK_WIDTH TANK_LENGTH Tank width is modifiable only when the tank shape selected is Rectangle or Cubic Tank Length is modifiable only when the tank shape selected is one among the following: 1. Cubic 2. Horizontal bullet 3. Horizontal cylinder 4. Rectangle Rev.5 FOUNDATION Fieldbus Option User's Manual Page 51

68 Parameter Name TANK_HEIGHT TANK_DIAMETER VOLUME_OFFSET STRAPPING_TABLE_DATE VOLUME_STRAPPING_TABLE_SIZE LEVEL_1 LEVEL_2 VOLUME_RD1 VOLUME_RD2 Description Tank height is modifiable only when the tank shape selected is vertical Bullet Tank Diameter is modifiable only when the tank shape selected is one among the below 1. Sphere 2. Horizontal Bullet 3. Vertical Cylinder 4. Horizontal Cylinder 5. Vertical Bullet The volume offset value to be added to all the volume values for correction Date of entry of Strapping Table can be updated whenever the strapping table modification is done. The format is MM/DD/YYYY HH:MM:SS Strapping Table Size. Strapping table consists of Level_1 Table, Level_2 Table, Volume_RD1 Table and Volume_RD2 table. Value of this limit the strapping table entry. Strapping Table maximum size is 50. Note: If the strapping table size is zero or strapping table entry is invalid then device will not use strapping table data. This is the first half part of the Level Table which supports entries for 25 elements. It can be updated when Linearization Type is either in DRY or WET. While executing Volume Wet Calculation Method, Level_1 table cannot be edited by user. Product Level Value or Interface level value (if Measured Product Type is Two Liquid Flooded) is copied in the Level Table based on the selected strapping table index. Level Table entry is limited by the Volume strapping Table Size. If entry exceeds Volume strapping table Size, the parameter check error is thrown. This is the second half part of the Level Table which supports entries for 25 elements. It can be updated when Linearization Type is either in DRY or WET. While executing Volume Wet Calculation Method, Level_2 table cannot be edited by user. Product Level Value or Interface level value (if Measured Product Type is Two Liquid Flooded) is copied in the Level Table based on the selected strapping table index. Level Table entry is limited by the Volume strapping Table Size. If entry exceeds Volume strapping table Size, the parameter check error is thrown. This is the first half part of the volume Table which supports entries for 25 elements. It can be updated when the linearization type is either DRY or WET. This is the second half part of the volume Table which supports entries for 25 elements. It can be updated when linearization type is either in DRY or WET. Page 52 FOUNDATION Fieldbus Option User's Manual Rev.5

69 Parameter Name ECHO_CURVE WINDOW_COUNT WINDOW_START WINDOW_DATA_SIZE ECHO_CURVE_TYPE Read only. Echo curve data Used for Echo curve Used for Echo curve Used for Echo curve Description Windowed Echo Curve: Used by the algorithm to find level measurements. Surface and Interface windows are tracking surface level and interface level respectively. Background subtraction near the reference plane is applied when needed. It is useful for troubleshooting the correlation algorithm. Full Echo Curve: The full raw echo curve, i.e. not windowed and no background removal or other processing done to it. Useful for troubleshooting process. Processed (Full) Echo Curve: Echo curve with background removal. Useful for troubleshooting process or the correlation algorithm. ECHOCURVE_ST_DIST ECHOCURVE_END_DIST ECHOCURVE_RESOLUTION ECHO_UNIT REFERENCE_REFL_ST_CT REFERENCE_REFL_MODEL_WT REFERENCE_REFL_MODEL_GAIN REFERENCE_REFL_MODEL_ATTEN REFERENCE_OBJ_FUN_THRESHOLD Background Subtraction Array: This array contains the echo curve in the reference plane region when the surface level is far from the reference plane. This array can then be subtracted from the echo curve to improve near zone performance. Distance from reference to begin the curve. Distance from reference to end the curve. Distance between samples on the curve. Lower number results in more detail but takes longer to process. Units of distance on curve: Ft m in cm mm Defines the start position (cm) of a 240cm wide search window. This parameter is not used under normal operation as the search window positions are automatically updated by a level tracking algorithm. Determines the width of the Reference wave where it crosses the x axis (one half wavelength). Amplitude (height) of the Reference wave shape. The attenuation parameter governs how fast the sine wave dies off. Increased attenuation results in smaller side lobes. If changing the gain does not help try increasing threshold. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 53

70 Parameter Name SURFACE_REFL_MODEL_WT SURFACE_REFL_MODEL_GAIN SURFACE_REFL_MODEL_ATTEN SURFACE_OBJ_FUN_THRESHOLD INTERFACE_REFL_ST_CT INTERFACE_REFL_MODEL_WT INTERFACE_REFL_MODEL_GAIN INTERFACE_REFL_MODEL_ATTEN INTERFACE_OBJ_FUN_THRESHOLD END_OF_PROBE_REFL_MODEL_WT END_OF_PROBE_REFL_MODEL_GAIN END_OF_PROBE_REFL_MODEL_ATTEN END_OF_PROBE_OBJ_FUN_THRESHOL D PROCESS_CONN_REFL_MODEL_WT PROCESS_CONN_REFL_MODEL_GAIN PROCESS_CONN_REFL_MODEL_ATTE N PROCESS_CONN_OBJ_FUN_THRESHO LD CALIBRATION_OFFSET REFERENCE_PLANE_OFFSET DATA_START_INDEX DATA_END_INDEX HON_RES_4 HON_RES_5 Description Determines the width of the Surface wave where it crosses the x axis (one half wavelength). Amplitude of the wave shape. Increased attenuation results in smaller side lobes of the wave s shape. If changing the gain does not help try increasing threshold. Defines the start position (cm) of a 240cm wide search window. This parameter is not used under normal operation as the search window positions are automatically updated by a level tracking algorithm. Determines the width of the Interface wave where it crosses the x axis (one half wavelength). Amplitude of the wave shape. Increased attenuation results in smaller side lobes of the wave s shape. If changing the gain does not help try increasing threshold. Determines the width of the Probe End wave where it crosses the x axis (one half wavelength). Amplitude of the wave shape. Increased attenuation results in smaller side lobes of the wave s shape. If changing the gain does not help try increasing threshold. Determines the width of the Process Connector where it crosses the x axis (one half wavelength). Amplitude of the wave shape. Increased attenuation results in smaller side lobes of the wave s shape. If changing the gain does not help, try increasing the threshold. Offset to compensate for a change in geometry at the process connector that affects the measurement Distance between the reference radar pulse reflection and the physical reference plane (flange) in the factory Used to read Echo Data Used to read Echo Data Reserved for Honeywell use only. Reserved for Honeywell use only. Page 54 FOUNDATION Fieldbus Option User's Manual Rev.5

71 Parameter Name SURFACE_REF_POS INTERFACE_REF_POS PROBEEND_REF_POS PROBE_LEN_OBS_DIS BLOCKING_DIS_HI_OBS_DIS BLOCKING_DIS_LO_OBS_DIS PROCESS_CONNECTOR_OFFSET LINEARIZATION_TABLE_INDEX REFERENCE_POS REFERENCE_AMP SURFACE_POS SURFACE_AMP INTERFACE_POS INTERFACE_AMP END_OF_PROBE_POS END_OF_PROBE_AMP REFERENCE_ECHO_STATUS PROCESS_CONN_REF_POS PROCESS_CONN_REF_AMP PROCESS_CONN_OFFSET SURFACE_ECHO_STATUS INTERFACE_ECHO_STATUS EP_ECHO_STATUS PROCESS_CONN_STATUS STRAPPING_TABLE_INDEX BLOCKING_DIS_HI_OBS BLOCKING_DIS_LO_OBS AMPLITUDE_TRACK Description Read only. Surface Reflection Position (True Distance). Read only. Interface Reflection Position (True Distance). Read only. Probe and Reflection Position (True Distance). Read only. Probe Length Observed Distance. Read only. Blocking Distance High Observed Distance. Read only. Blocking Distance Low Observed Distance. Read only. Process Connector Offset Observed Distance. Used in Level Wet Calibration Method to correct a value in Linearization Table. Read only. Reference Position Read only. Reference Amplitude Read only. Surface Position Read only. Surface Amplitude Read only. Interface Position Read only. Interface Amplitude Read only. End of Probe Position Read only. End of Probe Amplitude Read only. Reference Echo Status Process Connector Reflection Position (Observed Distance) Process Connector Reflection Amplitude Process Connector Offset Value Read only. Surface Echo Status. Read only. Interface Echo Status. Read only. End of Probe Echo Status. Read only. Process Connection Status. Used in Volume Wet Calibration Method to correct a value in Strapping Table Blocking Distance High (Observed Distance) Blocking Distance Low (Observed Distance) DISABLE ENABLE Enabled: Enables amplitude tracking Rev.5 FOUNDATION Fieldbus Option User's Manual Page 55

72 Attributes Supported Modes The block supports the following modes: AUTO (Automatic) OOS mode (Out of Service) Alarm Types The block supports standard block alarms (see section 3.2). ATTENTION Experion does not support displaying of Echo Curve. To view the Echo Curve, FDM/DTM should be used 3.7 Diagnostic Transducer block The Diagnostics Transducer block is used to monitor the sensor and communication board diagnostics. Execution The block has Sensor and Device diagnostics. The block is executed as follows Sensor Diagnostics: The device processes the diagnostic data such as Sensor MCU temperature, MCU Supply Voltage and Surface and Interface Signal Strength and Signal Quality. Surface and Interface diagnostics are updated along with status. GOOD status is updated if Signal Strength and Quality is good. Signal Quality: This variable indicates the degree of match between the reflection model and the live echo curve data. This value is 1 minus the objective function value (see section 3.6.2) and values close to 1 represent a very good match. If this number drops too low the reflection models should be checked as described in section Signal Strength: This variable indicates the amplitude of the indicated reflection. The level and interface reflections are negative, therefore a lower higher value indicates a larger amount of the radar energy was reflected which should provide a good signal to noise ratio. If this value drops too low the transmitter may not be able to reliably track the associated level. A good reflection should be approximately the same size as the gain for the correlation model peak: the acceptable values are dielectric constant and range dependent. Good values are in the range between -500 and counts. When the tank is empty or nearly empty, the reported Signal Strength and Signal Quality for Surface and Interface will instead be the ones for the End of Probe reflection. Page 56 FOUNDATION Fieldbus Option User's Manual Rev.5

73 Sensor Detailed Status SENSOR_DETAILED_STATUS parameter indicates the various status bits set by the sensor. Table 10 shows the various possible bits that could be set. Critical Status 1 Table 10: Sensor Detailed Status Critical Status 1 Possible Cause Recommended Action Sensor Internal RAM Fault External RAM Fault Flash CRC Fault Sensor Power Supply 2.5 OSC Fault RAM corruption detected. RAM corruption detected. The firmware has been corrupted. Power Accumulator malfunction. Power-cycle and see if the condition re-occurs. If so, replacement of the Sensor housing is required. Power-cycle and see if the condition re-occurs. If so, replacement of the Sensor housing is required. Attempt to reload the firmware. If the problem persists, replacement of the sensor housing will be required. Power-cycle the device and if problem persists replace Sensor housing If problem still persists replace the terminal block assembly. Sensor Power Supply 2.5V Fault Power Accumulator malfunction. Power-cycle the device and if problem persists replace Sensor housing. If problem still persists replace the terminal block assembly. Sensor Power Supply 3.3V Fault Power Accumulator malfunction. Power-cycle the device and if problem persists replace Sensor housing. If problem still persists replace the terminal block assembly. Power Accumulator Fault Power Accumulator malfunction. Power-cycle the device and if problem persists replace sensing housing... If problem still persists replace the terminal block assembly. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 57

74 Critical Status 2 Critical Status 2 Possible Cause Recommended Action Execution Time Error Delta Frequency Error In Factory Test Mode In Low Power Mode Reference Reflection Not Found Sensor NVRAM corrupt Sensor comm. DB CRC mismatch Sensor comm. DB Version mismatch The sensor is detecting that the time between measurements has exceeded the allowed time limit. This is set due to a sensor board fault or power accumulator fault. The unit is in factory / test mode. The sensor is in Low Power Mode. The sensor is unable to detect the reference reflection for level measurement in direct or remote mount transmitters or process connector reflection in remote mount transmitters. Sensor board NVRAM data has been corrupted. Comm sensor database Parameter Inconsistent Communication firmware is not compatible with sensor firmware. Ensure the configuration is correct and restart the device. If the problem persists, replacement of the Sensor housing may be necessary. Power cycle the device if problem persists replace the Sensor housing. Restart the device. The Sensor can be reset through a soft or hard restart. Upload an echo curve and confirm that the reference and process connector (only for remote mounts) model parameters are set for a good match with actual reflections. Perform a soft or hard reset. Use sensor NVRAM corrupt reset method from host to clear the sensor NVRAM error. This method will default the sensor NVRAM data. This will reset the critical NVRAM corruption alarm but the non-critical not characterized/calibrated alarms will stay. If the problem persist then change the sensor module. Check the cable between Communication module and Sensor housing is correct. Power cycle the device if problem still persists load the correct communication and sensor firmware versions. Update communication and sensor boards with compatible version of firmware. Check with Service person/support team for version details. Page 58 FOUNDATION Fieldbus Option User's Manual Rev.5

75 Non-Critical Status 1 Non-Critical Status 1 Possible Cause Recommended Action High Sensor Electronics Temperature Surface in BDH Surface in BDL Sensor Not Characterization Sensor Not Calibration Field Background Not Compatible Background Not Set Field Background Load Error The temperature of the sensor housing is too high. Accuracy and lifespan may decrease if the temperature remains high. This indicates that either the surface or interface reflection has been tracked into the upper zone near the Reference Plane where measurements are not accurate. This indicates that either the surface or interface reflection has been tracked into the lower zone near the End of Probe where measurements are not accurate. Indicates the final sensor characterization is incomplete. Indicates the final sensor calibration is incomplete. The Field Background was taken with a different set of mounting configuration than the current configuration. The Field Background is enabled before capture. The Field Background could not be loaded from non-volatile memory. Verify the environment temperature is within specification. Take steps to insulate the sensor housing from the temperature source. This is a condition that can occur during normal operation and does not generally require corrective action. If this condition is triggered when it is not expected, verify that the Blocking Distance High parameter is set correctly for the current conditions. If distance to product is in Higher zone then status associated with device variables derived from distance to product will be shown as uncertain in local display and on host the status would be poor accuracy. This is a condition that can occur during normal operation and does not generally require corrective action. If this condition is triggered when it is not expected, verify that the Blocking Distance Low parameter is set correctly for the current conditions. If distance to product is in Lower zone then status associated with device variables derived from distance to product will be shown as uncertain in local display and on host the status would be poor accuracy. The device is still available for use. There may be an impact on the accuracy of measurement. The device is still available for use. There may be an impact on the accuracy of measurement. Capture a new Field Background and perform a soft or hard reset. Capture a new Field Background and perform a soft or hard reset. Capture a new Field Background and perform a soft or hard reset. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 59

76 Non-Critical Status 2 Non-Critical Status 2 Possible Cause Recommended Action Interface in BDH Interface in BDL Surface rate of change exceeded This indicates that interface reflection has been tracked into the upper zone near the Reference Plane where measurements are not accurate. This indicates that interface reflection has been tracked into the lower zone near the End of Probe where measurements are not accurate. This indicates that the rate of change the product level is excedding the limit This is a condition that can occur during normal operation and does not generally require corrective action. If this condition is triggered when it is not expected, verify that the Blocking Distance High parameter is set correctly for the current conditions. If distance to interface is in Higher zone then status associated with device variables derived from distance to interface will be shown as uncertain in local display and on host the status would be poor accuracy. This is a condition that can occur during normal operation and does not generally require corrective action. If this condition is triggered when it is not expected, verify that the Blocking Distance Low parameter is set correctly for the current conditions. If distance to interface is in Lower zone then status associated with device variables derived from distance to interface will be shown as uncertain in local display and on host the status would be poor accuracy. Check the rate of change limit parameter value is as per application limit. If the problem exsist check the actual rate of change of the Level value and if the rate is within limit then check with Service person/support team for details. Interface rate of change exceeded Sensor characterization or calibration data corrupt This indicates that the rate of change the Interface level is excedding the limit Characterization of Sensor or Calibration data of sensor is corrupted. There may be impact on the accuracy of measurement. Check the rate of change limit parameter value is as per application limit. If the problem exsist check the actual rate of change of the Level value and if the rate is within limit then check with Service person/support team for details. Restart of Device is required. If this does not fix the problem, recharacterization or re-calibration of device is required to improve the accuracy. Page 60 FOUNDATION Fieldbus Option User's Manual Rev.5

77 DEVICE MODEL DETAILS: The device communication board model number is shown under device model detail menu. And selection of model number option is available to match the model number from Comm board or from Sensor. This is used when replacing either the comm module or the sensor electronics. Device Diagnostics: Time in Service Minutes the device has been in operation. Service Life Percent of expected Service Life that device has been in service. Value is based on conditions such as electronics temperature. Service life accumulates faster at higher stress conditions. Stress monitor Percentage of service time the device has been used under stressful conditions. Stress monitor = Amount of time the device was under stressful conditions Time in service of the device Power Cycle Track The power cycle track gives diagnostics related to the power-up information of the device. The Power Cycles is the number of power-ups experienced by the device after leaving factory. The Last Power Up Cycle time is the date and time of the last power up. Operating Voltage Track The statistics data for the supply voltage are tracked in the Operating voltage track. Supply Voltage is the current value of the voltage at the device input terminals. The status of the supply voltage whether it is normal or below operating value is indicated in the Status of Current Voltage parameter. Minimum Voltage is the value of the least voltage experienced by the device at the input terminals in its life time. Last Minimum Voltage Time is the date and time of the last minimum voltage experienced by the device. The Minimum Voltage can be reset by using the Reset Minimum Voltage parameter. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 61

78 Parameter List Table 11: Diagnostic Transducer block parameters Parameter Description ST_REV TAG_DESC STRATEGY ALERT_KEY MODE_BLK BLOCK_ERR UPDATE_EVT BLOCK_ALM EL_TEMP_DIAGNOSTIC SENSOR_DIAGNOSTICS POWER_TRAC OP_VOLTAGE TIME_IN_SERVICE SERVICE_LIFE STRESS_MONITOR SENSOR_DETAILED_STATUS SURFACE_SIGNAL_STRENGTH INTERFACE_SIGNAL_STRENGTH SURFACE_SIGNAL_QUALITY INTERFACE_SIGNAL_QUALITY HON_RES_1 HON_RES_2 HOS_RES_3 The revision level of the static data associated with the function block. The user description of the application of the block. Used to identify grouping of blocks. The identification number of the plant unit. The actual, target, permitted, and normal modes of the block. Reflects the error status associated with the hardware or software components associated with a block. It is a bit string, so that multiple errors may be shown. This alert is generated by any change to the static data. The BLOCK_ALM is used for all configuration, hardware, and connection failure or system problems in the block. The cause of the alert is entered in the subcode field. The first alert to become active sets the Active status in the Status attribute. As soon as the Unreported status is cleared by the alert reporting task, another block alert may be reported without clearing the Active status, if the subcode has changed. Electronic Temperature Diagnostic parameters. Sensor Diagnostics parameters. Power Up Track Data. Operating Voltage. Summation of time in minutes that power has been applied to the device since leaving the factory. Elapsed Service life of device in percentage. It monitors various diagnostic parameters which are then input into an algorithm to calculate an estimated percent of time that the transmitter has spent in stressful conditions. Three Bytes whose constituent bits represent the various status conditions set by the Sensor. Displays Surface signal strength value and Status Displays Interface Signal Strength Value and Status Displays Interface Signal Strength Value and Status Displays Interface Signal Strength Value and Status Reserved for Honeywell use only. Reserved for Honeywell use only. Reserved for Honeywell use only Page 62 FOUNDATION Fieldbus Option User's Manual Rev.5

79 Parameter COMM_MODEL_KEY Description Displays communication board model key COMM_MODEL_PART1 Displays communication board model part 1 COMM_MODEL_PART2 Displays communication board model part 2 None Sensor model number Comm model number SENSOR_MODEL_NO SENSOR_NVRAM_RESET It is used to reconcile the model number from sensor to comm and vice-versa. DISABLE ENABLE Enabled: Resets the sensor NVRAM Attributes Supported Modes The block supports the following modes: AUTO (Automatic) OOS (Out of Service). Alarm Types The block supports standard block alarms (see section 3.2). Rev.5 FOUNDATION Fieldbus Option User's Manual Page 63

80 3.8 LCD Transducer block The LCD Transducer block supports the Advanced Display. The block is used to configure the Advanced Display connected to the SLG 700 transmitter. The block stores the LCD configurations, and sends these values to the Display while the transmitter is powered up or restarted. The SLG 700 device supports up to eight LCD screen configurations. Figure 11: LCD Transducer Block ATTENTION The initial configuration of LCD transmitter is configured to show eight screens with Product Level, Distance to Interface, Interface Level, Distance to Interface, Electronic Temperature, Vapor, Vapor Volume, Upper Product Volume The Display shows the available set of process variables, and all function block inputs/outputs. In addition, the block reports the current device status and errors. If a function block parameter which is not currently a part of the control strategy is selected, an error appears in the Display. Execution Advanced Display The Advanced Display provides three formats, and describes the field in each of the three Advanced Display formats namely, PV, Bar Graph, and PV Trend. Essentially, all three formats provide the same information, but with the following differences: PV User configurable display shows the configured PV. Bar Graph User configurable 126 segment Bar Graph with range settings. The Bar Graph displays the current value of the configured PV. PV Trend User-configurable display period from one hour to 24 hours. The chart displays minimum, maximum, and average of the configured PV over the selected trend period. The LCD Transducer block supports configuration of up to eight LCD screens on the Advanced Display. The Display has a screen configured with default settings. Transmitter Messaging The transmitter messaging is a feature that allows message typed through host up to 64 alphanumeric characters) which is sent to the Advanced Display. The message is shown on the Display interspersed with the configured screens. Page 64 FOUNDATION Fieldbus Option User's Manual Rev.5

81 Clear Message To stop displaying the message, select the Clear Message method. After selecting this option, the device clears the entered Message from the Display. Table 12 lists the permitted parameters that can be configured using the LCD block. The selected parameter value will be displayed on the local display screen. Table 12 LCD parameters Block FF Parameter RADAR LEVELTB Product Level Distance To Product Product Level Rate Interface Level Distance To Interface Interface Level Rate Vapor Thickness Product Volume Electronic Temperature Vapor Volume Upper Product Volume Lower Product Volume Upper Product Thickness ANALOG INPUT BLOCK PV OUT FIELD_VAL ARITH IN IN_LO IN_1 IN_2 IN_3 ISEL OUT IN_1 IN_2 IN_3 IN_4 Rev.5 FOUNDATION Fieldbus Option User's Manual Page 65

82 Block FF Parameter PID BLOCK (PID) SP PV OUT IN CAS_IN BKCAL_IN BKCAL_OUT RCAS_IN ROUT_IN RCAS_OUT ROUT_OUT FF_VAL TRK_VAL SIGNAL CHARACTERIZER BLOCK OUT_1 OUT_2 IN_1 IN_2 OUTPUT SPLITTER BLOCK CAS_IN BKCAL_IN_1 BKCAL_IN_2 BKCAL_OUT OUT_1 OUT_2 INTEGRATOR OUT IN_1 IN_2 Page 66 FOUNDATION Fieldbus Option User's Manual Rev.5

83 Parameters List Table 13: LCD Transducer block parameters Parameter Description ST_REV TAG_DESC STRATEGY ALERT_KEY MODE_BLK BLOCK_ERR UPDATE_EVT BLOCK_ALM DISP_SEQ_TIME LANGUAGE LANGUAGE_PACK DISPLAY_TYPE LCD_CONTRAST DISP_FW_VER BLOCK_TYPE The revision level of the static data associated with the function block. The user description of the application of the block. Used to identify grouping of blocks. The identification number of the plant unit. The actual, target, permitted, and normal modes of the block. This parameter reflects the error status associated with the hardware or software components associated with a block. It is a bit string, so that multiple errors may be shown. This alert is generated by any change to the static data. The BLOCK_ALM is used for all configuration, hardware, and connection failure or system problems in the block. The cause of the alert is entered in the subcode field. The first alert to become active sets the Active status in the Status attribute. As soon as the Unreported status is cleared by the alert reporting task, another block alert may be reported without clearing the Active status, if the subcode has changed. Periodic rotation time of the display screens in seconds. Range 3-30 sec. Language selection for the Display. Supported Languages: English, French, German, Spanish, Turkish, Italian,Russian, Chinese and Japanese. Available selections are determined by the Language Pack supported. Type of language pack supported Western: English, French, German, Spanish, Italian, Turkish and Russian East Asian: English, Chinese and Japanese. Type of Display Connected. Possible Values: No Display Connected, Advanced Display. Contrast of the LCD screen can be controlled by this parameter. Its range is 1-9. Version Number of Display Firmware. Block type selection for screen process variable. The BLOCK_TYPE is present in all the eight screens: BLOCK_TYPE_1, BLOCK_TYPE_2, BLOCK_TYPE_3, BLOCK_TYPE_4, BLOCK_TYPE_5, BLOCK_TYPE_6, BLOCK_TYPE_7 and, BLOCK_TYPE_8. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 67

84 Parameter PARAM_INDEX UNIT_TYPES CUSTOM_UNIT CUSTOM_TAG DISPLAY_TEMPLATE Description Parameter selection for screen process variable. Parameters need to be chosen based on Block type. The PARAM_INDEX is present in all the eight screens: PARAM_INDEX_1, PARAM_INDEX_2, PARAM_INDEX_3, PARAM_INDEX_4, PARAM_INDEX_5, PARAM_INDEX_6, PARAM_INDEX_7 and, PARAM_INDEX_8. Unit selection for screen process variable. Appropriate units need to be selected based on the configured parameter. If desired units are not present, 'custom' may be selected. The UNIT_TYPES is present in all the eight screens: UNIT_TYPES_1, UNIT_TYPES_2, UNIT_TYPES_3, UNIT_TYPES_4, UNIT_TYPES_5, UNIT_TYPES_6, UNIT_TYPES_7 and, UNIT_TYPES_8. Character string to represent custom units. This value is used when Unit type of 'custom' is selected. Size: 8 Characters. The CUSTOM_UNIT is present in all the eight screens: CUSTOM_UNIT_1, CUSTOM_UNIT_2, CUSTOM_UNIT_3, CUSTOM_UNIT_4, CUSTOM_UNIT_5, CUSTOM_UNIT_6, CUSTOM_UNIT_7 and CUSTOM_UNIT_7. Tag to be displayed for the screen. Length: 14 Characters. The CUSTOM_TAG is present in all the eight screens: CUSTOM_TAG_1, CUSTOM_TAG_2, CUSTOM_TAG_3, CUSTOM_TAG_4, CUSTOM_TAG_5, CUSTOM_TAG_6, CUSTOM_TAG_7 and CUSTOM_TAG_8. Represents the display screen template. Possible Values: a. PV : PV value is displayed b. PV and Trend : PV value followed by a Trend is shown on the display c. PV and Bar Graph : PV value followed by a Bargraph is shown on the display d. None: Screen will not be seen. The DISPLAY_TEMPLATE is present in all the eight screens: DISPLAY_TEMPLATE_1, DISPLAY_TEMPLATE_2, DISPLAY_TEMPLATE_3, DISPLAY_TEMPLATE_4, DISPLAY_TEMPLATE_5, DISPLAY_TEMPLATE_6, DISPLAY_TEMPLATE_7 and DISPLAY_TEMPLATE_8. DECIMALS Number of digits to display after the decimal point. Range: 0-3. DECIMALS are present in all the eight screens: DECIMALS_1, DECIMALS_2, DECIMALS_3, DECIMALS_4, DECIMALS_5, DECIMALS_6, DECIMALS_7 and DECIMALS_8. PV_LOLIM PV_HILIM Display Low Limit (Trend, Bar, Custom PV scaling, usually equal to LRV). The PV_LOLIM is present in all the eight screens: PV_LOLIM_1, PV_LOLIM_2, PV_LOLIM_3, PV_LOLIM_4, PV_LOLIM_5, PV_LOLIM_6, PV_LOLIM_7 and PV_LOLIM_8. Display High Limit (Trend, Bar, Custom PV scaling, usually equal to URV). The PV_HILIM is present in all the eight screens: PV_HILIM_1, PV_HILIM_2, PV_HILIM_3, PV_HILIM_4, PV_HILIM_5, PV_HILIM_6, PV_HILIM_7 and PV_HILIM_8. Page 68 FOUNDATION Fieldbus Option User's Manual Rev.5

85 Parameter TREND_DURATION DISPLAY_MESSAGE ROTATE_ENABLE Description Duration of a trend screen in hours. Its valid range is The TREND_DURATION is present in all the eight screens: TREND_DURATION_1, TREND_DURATION_2, TREND_DURATION_3, TREND_DURATION_4, TREND_DURATION_5, TREND_DURATION_6, TREND_DURATION_7 and TREND_DURATION_8. A message with a maximum of 64 characters that appears on the Advanced Display of the transmitter. Parameter to Enable or Disable screen rotation. Attributes Supported Modes The block supports the following modes: AUTO (Automatic) OOS (Out of Service). Alarm Types The block supports standard block alarms (see section 3.2). Rev.5 FOUNDATION Fieldbus Option User's Manual Page 69

86 3.9 Analog Input block The Analog Input (AI) block takes the transducer s input data, selected by channel number, and makes it available to other function blocks at its output. The variables to be used by the block are defined through the available channels: Product Level Product Volume Distance To Product Electronic Temperature Product Level Rate Vapor Volume Interface Level Upper Product Volume Distance To Interface Lower Product Volume Interface Level Rate Upper Product Thickness Vapor Thickness Figure 12: Analog Input Block Execution Transmitter Output Signal and Status Viewing certain parameters, their values and status in the transmitter and understanding their relationship to each other are helpful in understanding transmitter output signal and status. The following paragraphs and tables describe transducer and AI block parameters which directly determine the way the transmitter output is presented. Level Sensor Signal In Transducer block, the Surface Signal or Interface Signal is represented as calculated Distance to Level and Distance to Interface Values. These values are used to calculate the Product Level, Interface Level, Vapor Thickness and Upper Product Thickness. These values use Level use the elements in Product Level Range to determine the engineering units, the decimal places for the display and also the high and low scale of the value. This Product Level and Interface Level values are further used to calculate the Product Level Rate and Interface Rate which use the elements in Level Rate Range to determine the engineering units and Product Volume, Vapor Volume, Upper Product Volume and Lower Product Volume which use the Product Volume Range to determine the engineering units, decimal places for the display and also the high and low scale of the value. These values become the PV value in the AI block, and uses the elements of OUT_SCALE in determining the units, decimal places and also the high and low scale values of PV. These signal leave the AI block as OUT value, which also uses the elements of OUT_SCALE. The Transducer scaling (XD_SCALE) is applied to the value from the channel to produce the FIELD_VAL in percent. The XD_SCALE unit s code must match the channel unit s code or be supported by the device if this is not the case the block remains in OOS mode, after being configured. Page 70 FOUNDATION Fieldbus Option User's Manual Rev.5

87 Figure 13: Analog Input Block Schematic Diagram The OUT_SCALE is normally the same as the transducer, but if L_TYPE is set to Indirect or Ind Sqr Root, OUT_SCALE determines the conversion from FIELD_VAL to the output. PV and OUT always have identical scaling. OUT_SCALE provides scaling for PV. The block places the value in OUT if the mode is AUTO. If MAN mode is allowed, write a value to the output. The status prevents any attempt at closed loop control using the MAN value, by setting the Limit value to Constant. The LOW_CUT parameter has a corresponding Low cut-off option in the IO_OPTS bit string. If the option bit is set as True, any calculated output below the low cut-off value changes to zero. This is only useful for zero based measurement devices, such as flow. The PV filter, whose time constant is PV_FTIME, is applied to the PV, and not the FIELD_VAL. Equations FIELD_VAL = 100*(channel value - EU@0%) / (EU@100% - EU@0%) [XD_SCALE] Direct: PV = channel value Indirect: PV = (FIELD_VAL/100) * (EU@100% - EU@0%) + EU@0% [OUT_SCALE] Ind Sqr Root: PV = sqrt (FIELD_VAL/100) * (EU@100% - EU@0%) + EU@0% [OUT_SCALE] XD_SCALE Range In the AI block, XD_SCALE values are used when L_TYPE is set to Indirect which converts the signal to other units. The high and low scale values of XD_SCALE (EU_100 and EU_0) define the range over which the AI OUT shows the status as Good. When L_TYPE is set to either Indirect or Direct, XD_SCALE units must match the transducer units. When L_TYPE is set to Direct, it is recommended that XD_SCALE and OUT_SCALE must contain the same values. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 71

88 PV Value The AI block PV value is determined based on the selected transducer channel s PRIMARY_VALUE. AI OUT AI in Manual Mode When the AI block is in manual mode, OUT can be written as a fixed value between -10% and +110% of the OUT_SCALE range. OUT values between 0 and 100% shows a status of Good. OUT values outside the range shows a status of Uncertain. The limit field is marked as Constant for all values. PV shows the live temperature signal in manual mode. AI in AUTO Mode L_TYPE determines whether the signal is taken directly from the transducer block and passed to the AI block output (L_TYPE = Direct) or converted into different units before it is passed to the AI block output (L_TYPE = Indirect or Ind Sqr Root). OUT_SCALE determines the units conversion of the signal presented to the output. When L_TYPE equals Direct, OUT is the same as the value passed from the transducer block. When L_TYPE is Indirect, the PRIMARY_VALUE is converted to XD_SCALE and that value is set equal to OUT (FIELD_VAL = %). The OUT in % is re-ranged to a value using the OUT_SCALE. OUT status The following table provides the resulting status of AI block OUT for a given status of PRIMARY_VALUE in the transducer block. If... Then... PRIMARY_VALUE status = Good::[alarm status]:not Limited PRIMARY_VALUE status = Uncertain 2 nd field in the PRIMARY_VALUE status = Non Specific OUT value is tested against OUT_SCALE range values: If OUT value is within the OUT_SCALE range, then OUT status = Good Non Cascade::[alarm status]:not Limited If OUT exceeds OUT_SCALE range, then OUT status = Uncertain:: Engineering Units Range Violation:& High or Low Limited OUT status = Uncertain OUT status = Non Specific PRIMARY_VALUE status = High or Low OUT status = High or Low Page 72 FOUNDATION Fieldbus Option User's Manual Rev.5

89 Parameters List Table 14: Analog Input block parameters Parameter ST_REV TAG_DESC STRATEGY ALERT_KEY MODE_BLK BLOCK_ERR PV OUT SIMULATE XD_SCALE OUT_SCALE GRANT_DENY IO_OPTS STATUS_OPTS CHANNEL Description The revision level of the static data associated with the function block. The revision value is incremented each time a static parameter value in the block is changed. The user description of the application of the block. It is used to identify grouping of blocks. This data is not checked or processed by the block. The identification number of the plant unit. This information may be used in the host for sorting alarms, and so on. The actual, target, permitted, and normal modes of the block. Target: The mode to go to Actual: The mode the block is currently in Permitted: Allowed modes that target may take on Normal: Most common mode for target This parameter reflects the error status associated with the hardware or software components associated with a block. It is a bit string, so that multiple errors may be shown. The process variable used in block execution. The block output value and status. A group of data that contains the current transducer value and status, the simulated transducer value and status, and the enable/disable bit. Elements used to display the value obtained from the transducer block. The elements are: High and low scale values (EU_100 and EU_0). Engineering units to display the value (UNITS_INDEX). Decimal places to display the value (DECIMAL). The high and low scale values, engineering units code, and number of digits to the right of the decimal point associated with OUT. Normally, the operator has permission to write to parameter values, but Program or Local remove that permission and give it to the host controller or a local control panel. Allows the selection of input/output options used to alter the PV. Low cutoff enabled is the only selectable option. Helps select options for status handling and processing. The supported status options for the AI block are Propagate Fault Forward Uncertain, if Limited Bad, if Limited and Uncertain if MAN mode. The CHANNEL value is used to select the measurement value. Configure the CHANNEL parameter before configuring the XD_SCALE parameter. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 73

90 Parameter L_TYPE Description The state (Direct or Indirect) values that are passed from the transducer block to the AI block. When L_TYPE = Direct, the values are passed directly from the transducer block to the AI block. (No units conversion.) When L_TYPE = Indirect, the values from the transducer block are in different units, and must be converted either linearly (Indirect) or in square root (Ind Sqr Root) using the range defined by the transducer and the OUT_SCALE range. LOW_CUT If the percentage value of transducer input fails below this, PV = 0. PV_FTIME FIELD_VAL UPDATE_EVT BLOCK_ALM ALARM_SUM ACK_OPTION ALARM_HYS HI_HI_PRI HI_HI_LIM HI_PRI HI_LIM LO_PRI LO_LIM LO_LO_PRI LO_LO_LIM HI_HI_ALM HI_ALM LO_ALM LO_LO_ALM The time constant of the first-order PV filter. It is the time required for a 63% change in the IN value. The value and status from the transducer block or from the simulated input when simulation is enabled. This alert is generated by any change to the static data. The block alarm is used for all configuration, hardware, and connection failure or system problems in the block. The cause of the alert is entered in the subcode field. The first alert to become active sets the Active status in the Status parameter. As soon as the Unreported status is cleared by the alert reporting task, another block alert may be reported without clearing the Active status, if the subcode has changed. The summary alarm is used for all process alarms in the block. The cause of the alert is entered in the subcode field. The first alert to become active sets the Active status in the Status parameter. As soon as the Unreported status is cleared by the alert reporting task, another block alert may be reported without clearing the Active status, if the subcode has changed. Used to set AUTO acknowledgment of alarms. The amount the alarm value must return within the alarm limit before the associated active alarm condition clears. The priority of the HI HI alarm. The setting for the alarm limit used to detect the HI HI alarm condition. The priority of the HI alarm. The setting for the alarm limit used to detect the HI alarm condition. The priority of the LO alarm. The setting for the alarm limit used to detect the LO alarm condition. The priority of the LO LO alarm. The setting for the alarm limit used to detect the LO LO alarm condition. The HI HI alarm data, which includes a value of the alarm, a timestamp of occurrence and the state of the alarm. The HI alarm data, which includes a value of the alarm, a timestamp of occurrence and the state of the alarm. The LO alarm data, which includes a value of the alarm, a timestamp of occurrence and the state of the alarm. The LO LO alarm data, which includes a value of the alarm, a timestamp of occurrence and the state of the alarm. Page 74 FOUNDATION Fieldbus Option User's Manual Rev.5

91 Attributes Supported Modes The block supports the following modes: AUTO (Automatic) MAN (Manual) OOS (Out of Service). Alarm Types The block supports standard block alarms (see section 3.2). Additionally it supports, standard HI_HI, HI, LO, and LO_LO alarms applied to OUT. Status Handling Uncertain - EU Range Violation status is always set if the OUT value exceeds the OUT_SCALE range and no worse condition exists. The following options from STATUS_OPTS apply, where Limited refers to the sensor limits: Propagate Fault Forward If the status from the sensor is Bad, Device failure or Bad, Sensor failure, propagate it to OUT without generating an alarm. The use of these sub-status in OUT is determined by this option. Through this option, the user may determine whether alarming (sending of an alert) is done by the block or propagated downstream for alarming. Uncertain, if Limited Set the output status of the Analog Input block to uncertain if the measured or calculated value is limited. Bad if Limited Set the output status to Bad if the sensor is violating a high or low limit. Uncertain if MAN Mode Set the output status of the Analog Input block to uncertain if the actual mode of the block is MAN. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 75

92 3.10 Proportional Integral Derivative (PID) block with auto tune The PID block is the key to many control schemes, and it is commonly used. The PID function integrates the errors. If there is difference in process time constants of a primary process and secondary process measurement, then the block can be cascaded if required. Auto tuning is a feature that tunes the PID constants as per the process automatically. Figure 14: PID Block Figure 15: PID Block Schematic Diagram Page 76 FOUNDATION Fieldbus Option User's Manual Rev.5

93 Execution The Process Variable to be controlled is connected to the IN input. The value is passed through a filter, and its time constant is PV_FTIME. The value is then shown as the PV, which is used in conjunction with the SP in the PID algorithm. A PID does not integrate if the limit status of IN input is constant, or if further control action based on the PID error proceeds IN input further towards its active status limit. A full PV and DV alarm sub-function is provided. The PV has a status, although it is a contained parameter. This status is a copy of IN s status, unless IN is Good and there is a PV or block alarm. The full cascade SP sub-function is used with rate and absolute limits. The block has additional control options which cause the SP value to track the PV value. The SP value tracks the PV value while the block is in Actual mode of IMan, LO, or ROut, or when the target mode of the block is MAN. The block provides a switch for BYPASS, which is available to the operator if the Bypass Enable control option is set as True. BYPASS can be used in secondary cascade controllers that have a Bad PV. The BYPASS Enable option is required, so if BYPASS is set as True, not all cascade control schemes are stable. BYPASS can only be changed when the block mode is in MAN or OOS mode. When BYPASS is set, the value of SP, in percent of range, is passed directly to the target output, and the value of OUT is used for BKCAL_OUT. When the mode is changed to Cas, the upstream block is requested to initialize to the value of OUT. When a block is in Cas mode, on the transition out of BYPASS, the upstream block is requested to initialize to the PV value, irrespective of the Use PV for BKCAL_OUT option. GAIN, RESET, and RATE are the tuning constants for the P, I, and D terms, respectively. The block provides existing controllers that are tuned by the inverse value of some or all of them, such as proportional band and repeats per minute. The human interface to these parameters must be able to display the user's preference. BAL_TIME parameter can be used to set the rate at which the I term moves towards balancing the difference between the previous integral term and the limited output. The Direct Acting control option, if set as True, causes the output to increase when the PV exceeds the SP. If set as False, the output decreases when the PV exceeds the SP. The Direct Acting control option must be set carefully, as it can cause a difference between positive and negative feedback. ATTENTION The Direct Acting control option can never be changed while in AUTO mode. The setting of the option must also be used in calculating the limit state for BKCAL_OUT. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 77

94 The output supports the feed forward algorithm. The FF_VAL input brings in an external value which is proportional to some disturbance in the control loop. The value is converted to percent of output span using the values of parameter FF_SCALE. This value is multiplied by the FF_GAIN and added to the target output of the PID algorithm. If the status of FF_VAL is Bad, the last usable value is used as this prevents bumping the output. When the status returns to Good, the block adjusts its integral term to maintain the previous output. The output supports the track algorithm. The block provides an option to use either the SP value after limiting or the PV value for the BKCAL_OUT value PID Control block PID Control block is an algorithm that produces an output signal in response to the measured variable and the setpoint. The PID block allows you to choose either a standard PID control equation (Ideal) or a robust PID equation defined by Honeywell. This selection is defined in the PID_FORM parameter. The output has three terms, namely Proportional, Integral, and Derivative. The output is adjusted by tuning constants. There are three tuning constants in the ideal PID equation. The robust PID uses four tuning constants: 1. GAIN is the tuning constant of the Proportional term. 2. RESET is the tuning constant of the Integral. 3. RATE is the tuning constant of the Derivative. RATE is usually modified by a lag, which is set at some fixed ratio higher than the rate time, to create a rate gain. There is no lag with the rate in this implementation. 4. OUT_LAG is the fourth tuning constant used in the robust PID; it adds roll off to the output response. The action is similar to PID with rate gain PID Ideal and PID Robust The ideal equation is a parallel or non-interacting implementation of PID control using three tuning constants. It automatically fixes OUT_LAG to 16 times the RATE time constant. This produces response characteristics equivalent to the algorithms used in TPS products. The robust equation is the same parallel implementation of ideal PID control but allows the engineer to set the OUT_LAG and effectively change the rate gain. ALGO_TYPE is a configuration parameter that contains one of three selected algorithm types, A, B, or C. Where: A - RATE, GAIN and RESET all act on the error between setpoint and measured variable. B - RATE acts on the measured variable only, GAIN and RESET use the error. C - RATE and GAIN act on the measured variable only, and RESET uses the error. Page 78 FOUNDATION Fieldbus Option User's Manual Rev.5

95 PID Tuning Parameters Table 15 lists the valid ranges for the tuning parameters for the PID block. Note that OUT_LAG parameter is not configurable when Ideal PID is selected (PID_FORM = 1) and can be configured when Robust PID is selected (PID_FORM = 2). The values given for these tuning parameters are valid under the following conditions: The values assume that the minimum configurable PID function block execution period (T s) is seconds. Algorithm typesetting (A, B, or C) has no effect on the validation of these tuning parameters. The PID function block rejects all values outside the following ranges: Table 15: PID Tuning parameters Parameter Initial Value Minimum Value Maximum Value Comment PV_FTIME Units: seconds. GAIN GAIN_NLIN RATE (sec.) RESET (sec.) 0 32 Ts 7500 The value of ZERO is permitted to turn off rate action. +INF 2 Ts 7500 The value of +INF is permitted to turn off reset action. (Some versions of NI configurator program cannot set +/- INF). OUT_LAG Ideal PID N/A N/A N/A Fixed for Ideal PID form - not configurable. Robust PID 0 2 Ts 7500 Zero permitted which implies no output lag. BAL_TIME 0 N/A N/A Not used in Honeywell Implementation. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 79

96 Cycle tuning Auto tuning The PID block supports the Cycle tuning algorithm. In Cycle tuning, the tuning parameter values are derived from the process response to the resultant action of causing the PV to oscillate about a SP value. The tuning method uses the measured ultimate gain and period to produce tuning parameter values, by using the relationship developed by Ziegler Nichols equations. Cycle tuning does not distinguish between process lags and always results in gain based on PV amplitude, and calculates the values of Reset and Rate based on time of the SP crossings using a fixed ratio of 4 to 1. Initially, this method does not require a stable process. Cycle tuning is applicable to Three Position Step control, and is used for integrating process. Auto tuning procedure There are nine parameters applicable for auto tuning: AT_TYPE, TUNING_CRITERIA, TUNE_REQ, ATI, AT_MODE, AT_ERR, AT_GAIN, AT_RESET, and AT_RATE. AT_Type There are two types of selections, namely Disable and Cycle Tune. When Disable is selected, AT_MODE becomes inactive. When Cycle Tune is selected, AT_MODE becomes AT Ready. TUNING_CRITERIA There are two types of tuning criteria available for selection: Normal and Fast. NORMAL - Conservative tuning designed to reduce overshoot as compared to FAST. FAST - Aggressive tuning designed to provide quarter-dampened response. TUNE_REQ TUNE_REQ can be turned ON only in the following modes, namely AUTO, CAS, RCAS, and ROUT. The ATI value becomes 1, and AT_ERROR shows the status as Run, this shows that auto tuning is in progress. If AT_ERROR shows OK, auto tuning is successful. AT_GAIN, AT_RESET, AT_RATE gets updated automatically and same values are copied to GAIN, RESET and RATE respectively. Page 80 FOUNDATION Fieldbus Option User's Manual Rev.5

97 Parameter list Table 16: PID block parameters Parameter ST_REV TAG_DESC STRATEGY ALERT_KEY MODE_BLK BLOCK_ERR PV SP OUT PV_SCALE OUT_SCALE GRANT_DENY CONTROL_OPTS STATUS_OPTS IN PV_FTIME Description The revision level of the static data associated with the function block. The revision value is incremented each time a static parameter value in the block is changed. The user description of the application of the block. Used to identify grouping of blocks. This data is not checked or processed by the block. The identification number of the plant unit. This information may be used in the host for sorting alarms, etc. The actual, target, permitted, and normal modes of the block. Target: The mode to go to Actual: The mode the block is currently in Permitted: Allowed modes that target may take on Normal: Most common mode for target This parameter reflects the error status associated with the hardware or software components associated with a block. It is a bit string so that multiple errors may be shown. The process variable used in block execution. It is the target block setpoint value. It is the result of setpoint limiting and setpoint rate of change limiting. The block input value and status. The high and low scale values, engineering units code and number of digits to the right of the decimal point associated with PV. The high and low scale values, engineering units code and number of digits to the right of the decimal point associated with OUT. Options for controlling access of host computers and local control panels to operating, tuning, and alarm parameters of the block. Not used by the device. Specify control strategy options. The supported control options for the PID block are Track Enable, Track in Manual, SP-PV Track in MAN, SP-PV Track in LO or IMAN, Use PV for BKCAL_OUT, Direct Acting, SP Track Retain, SP-PV Track Out, Restrict SP to limits in CAS and RCAS, No output limits in MAN. It helps to select options for status handling and processing. The supported status option for the PID block is Target to Manual if Bad IN. IFS if Bad IN, IFS if Bad CAS_IN, Use Uncertain as Good, Target to next permitted mode if Bad CAS_IN, Target to MAN if Bad TRK_IN_D and IFS if Bad TRK_IN_D. The connection for the PV input from another block. The time constant of the first-order PV filter. It is the time required for a 63 percent change in the IN value. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 81

98 Parameter BYPASS CAS_IN SP_RATE_DN SP-RATE_UP SP_HI_LIM SP_LO_LIM Description Used to override the calculation of the block. When enabled, the SP is sent directly to the output. The remote setpoint value from another block. Ramp rate for downward SP changes. When the ramp rate is set to zero, the SP is used immediately. Ramp rate for upward SP changes. When the ramp rate is set to zero, the SP is used immediately. The highest SP value allowed. The lowest SP value allowed. GAIN The proportional gain value. This value cannot = 0. RESET BAL_TIME RATE BKCAL_IN OUT_HI_LIM OUT-LO_LIM BKCAL_HYS BKCAL_OUT RCAS_IN ROUT_IN SHED_OPT RCAS_OUT ROUT_OUT TRK_SCALE TRK_IN_D The integral action time constant. The specified time for the internal working value of bias to return to the operator set bias. Also used to specify the time constant at which the integral term moves to obtain balance when the output is limited and the mode is AUTO, CAS, or RCAS. The derivative action time constant. The analog input value and status from another block s BKCAL_OUT output that is used for backward output tracking for bump less transfer and to pass limit status. The maximum output value allowed. The minimum output value allowed The amount the output value must change away from its output limit before limit status is turned off. The value and status required by the BKCAL_IN input of another block to prevent reset windup and to provide bump less transfer of closed loop control. Target setpoint and status that is provided by a supervisory host. Used when mode is RCAS. Target output and status that is provided by a supervisory host. Used when mode is ROUT. Defines action to be taken on remote control device timeout. Block setpoint and status after ramping, filtering, and limiting that are provided to a supervisory host for back calculation to allow action to be taken under limiting conditions or mode change. Used when mode is RCAS. Block output that is provided to a supervisory host for a back calculation to allow action to be taken under limiting conditions or mode change. Used when mode is RCAS. The high and low scale values, engineering units code, and number of digits to the right of the decimal point associated with the external tracking value (TRK_VAL). Discrete input that initiates external tracking. Page 82 FOUNDATION Fieldbus Option User's Manual Rev.5

99 Parameter TRK_VAL FF_VAL FF_SCALE FF_GAIN UPDATE_EVT BLOCK_ALM ALARM_SUM ACK_OPTION ALARM_HYS HI_HI_PRI HI_HI_LIM HI_PRI HI_LIM LO_PRI LO_LIM LO_LO_PRI LO_LO_LIM DV_HI_PRI DV_HI_LIM DV_LO_PRI DV_LO_LIM Description The value (after scaling from TRK_SCALE to OUT_SCALE) APPLIED to OUT in LO mode. The feedforward control input value and status. The high and low scale values, engineering units code, and number of digits to the right of the decimal point associated with the feedforward value (FF_VAL). The feedforward gain value. FF_VAL is multiplied by FF_GAIN before it is added to the calculated control output. This alert is generated by any changes to the static data. The block alarm is used for all configuration, hardware, connection failure, or system problems in the block. The cause of the alert is entered in the subcode field. The first alert to become active sets the active status in the status parameter. As soon as the Unreported status is cleared by the alert reporting task and other block alert may be reported without clearing the Active status, if the subcode has changed. The summary alarm is used for all process alarms in the block. The cause of the alert is entered in the subcode field. The first alert to become active sets the Active status in the Status parameter. As soon as the Unreported status is cleared by the alert reporting task, another block alert may be reported without clearing the Active status, if the subcode has changed. Used to set auto acknowledgment of alarms. The amount the alarm value must return to within the alarm limit before the associated active alarm condition clears. The priority of the HI HI Alarm. The setting for the alarm limit used to detect the HI HI alarm condition. The priority of the HI alarm. The setting for the alarm limit used to detect the HI alarm condition. The priority of the LO alarm. The setting for the alarm limit used to detect the LO alarm condition. The priority of the LO LO alarm. The setting for the alarm limit used to detect the LO LO alarm condition. The priority of the deviation high alarm. The setting for the alarm limit used to detect the deviation high alarm condition. The priority of the deviation low alarm. The setting for the alarm limit use to detect the deviation low alarm condition. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 83

100 Parameter HI_HI_ALM HI_ALM LO_ALM LO_LO_ALM DV_HI_ALM DV_LO_ALM PID_FORM Description The HI HI alarm data, which includes a value of the alarm, a timestamp of occurrence, and the state of the alarm. The HI alarm data, which includes a value of the alarm, a timestamp of occurrence, and the state of the alarm. The LO alarm data, which includes a value of the alarm, a timestamp of occurrence, and the state of the alarm. The LO LO alarm data, which includes a value of the alarm, a timestamp of occurrence, and the state of the alarm. The DV HI alarm data, which includes a value of the alarm, a timestamp of occurrence, and the state of the alarm. The DV LO alarm data, which includes a value of the alarm, a timestamp of occurrence, and the state of the alarm. Configuration parameter specifies the IDEAL or ROBUST PID equation to be used: IDEAL PID (default): Non-interactive form of a three mode control equation that provides Proportional, Integral and Derivative control action. Linear and non-linear gain parameters are available. ROBUST PID: The same as Ideal PID. Additionally, the equation supports a user-configurable lag filter applied to calculated output value. (See OUT_LAG parameter.) Linear and non-linear gain parameters are available. ALGO_TYPE Configuration parameter specifies algorithm type which can be A, B, or C: Type A equation where Proportional, Integral and Derivative act on ERROR. Type B equation where Proportional and Integral act on ERROR and Derivative acts on PV. Type C equation where Integral acts on ERROR and Proportional and Derivative act on PV. OUT_LAG GAIN_NLIN GAIN_COMP ERROR_ABS WSP BLOCK_TEST Time constant of single exponential LAG filter applied to the OUT parameter (primary output). Units (in seconds). For Ideal PID equation the lag filter is fixed at 1/16 and is not configurable. Dimensionless gain factor. When the gain factor is multiplied by absolute value of the error and added to the linear GAIN, the result is a gain response which is proportional to the deviation. The default value is zero resulting in no response due to non-linear gain action. The composite gain quantity including both linear and non-linear gain parameters. It is a read only parameter. Absolute value of the difference between PV and working setpoint. Read only parameter. Working setpoint. This is the setpoint value after absolute and rate limits have been applied. Deviation alarms are computed on this value. It is a read only parameter. Test parameter to determine if the block is functioning correctly. Page 84 FOUNDATION Fieldbus Option User's Manual Rev.5

101 Parameter AT_TYPE TUNING_CRITERIA TUNE_REQ ATI AT_MODE AT_ERROR AT_GAIN AT_RESET AT_RATE Description Auto Tune Selection supports two types: Disable, Cycle Tune. Tuning Criteria supports two types: Normal, Fast. Tuning Request performs auto tuning process. Auto Tune Indicator indicates Auto tune ON/OFF. Auto Tune Mode supports two options: AT Ready, Inactive AT Ready indicates block is ready for auto tune Inactive indicates auto tuning is disabled. Auto Tune Error supports the following errors: Abort, Not ready, OK, and Run. Auto tuned Gain. Auto tuned Reset. Auto tuned Rate. Attributes Supported Modes Alarm Types Status Handling The block supports the following modes: AUTO (Automatic) MAN (Manual) OOS (Out of Service) IMan Cas RCas ROut LO The block supports standard block alarms (see section 3.2), in addition to it standard HI_HI, HI, DV_HI, DV_LO, LO, and LO_LO alarms applied to PV. Standard, in addition to the following things for the control selector. If Not selected is received at BKCAL_IN, the PID algorithm must make necessary adjustments to prevent windup. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 85

102 3.11 Input Selector block The Input Selector block performs maximum, minimum, middle, average and first good input selection. The Input Selector block provides selection of up to four inputs and generates an output based on the selected type of input. The block normally receives its inputs from AI blocks, and provides a combination of parameter configuration options. The block functions as a rotary position switch, or a validated priority selection based on the use of the first good parameter and the disable_n parameter. As a switch, the block receives switching information from either the connected inputs or from an operator input. The block supports signal status propagation. The block is used to provide control input selection in the forward path only, and hence no back calculation support is provided. SELECTED indicates which input has been selected or the number of inputs selected by the algorithm. The block does not support process alarms. Execution Input processing Figure 16: Input Selector Block If DISABLE_n is True, the corresponding input IN_n is discarded. If there are no inputs left, or if there are inputs fewer than MIN_GOOD inputs, then the value of SELECTED becomes zero. Selection Processing If OP_SELECT is non-zero, the OP_SELECT value determines the selected input, irrespective of the SELECT_TYPE selection. The value of SELECTED is the number of the input used. If SELECT_TYPE is First Good, it transfers the value of the first remaining input to the output of the block. The value of SELECTED is the number of the input used. Page 86 FOUNDATION Fieldbus Option User's Manual Rev.5

103 Figure 17: Input Selector Schematic Diagram If SELECT_TYPE is Minimum, it transfers the lowest value to the output of the block. The value of SELECTED is the number of the input with the lowest value. If SELECT_TYPE is Maximum, it transfers the highest value to the output of the block. The value of SELECTED is the number of the input with the highest value. If SELECT_TYPE is Middle, if there are 3 or 4 values, the highest and lowest value is discarded. The average of the remaining two values is computed, and the value is transferred to the output of the block. The value of SELECTED becomes zero if an average is used, else the value of SELECTED is the number of the input with the middle value. If SELECT_TYPE is Average, it computes the average of the remaining inputs and transfers the value to the output of the block. The value of SELECTED is the number of inputs used in the average. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 87

104 Parameters List Parameter Table 17: Input Selector block parameters Description ST_REV TAG_DESC STRATEGY ALERT_KEY MODE_BLK BLOCK_ERR OUT GRANT_DENY STATUS_OPTI ONS IN_1 IN_2 IN_3 IN_4 DISABLE_1 DISABLE_2 DISABLE_3 DISABLE_4 SELECT_TYPE MIN_GOOD SELECTED OP_SELECT The revision level of the static data associated with the function block. The revision value increments each time a static parameter value in the block is changed. The user description of the application of the block. Used to identify grouping of blocks. This data is not checked or processed by the block. The identification number of the plant unit. This information may be used in the host for sorting alarms, etc. The Actual, Target, Permitted, and Normal modes of the block. Target: The mode to go to. Actual: The mode the block is currently in. Permitted: Allowed modes that target may take on. Normal: Most common mode for target. This parameter reflects the error status associated with the hardware or software components associated with a block. It is a bit string, so that multiple errors may be shown. The block output value and status. Options for controlling access of host computers and local control panels to operating, tuning, and alarm parameters of the block. Not used by device. It helps to select options for status handling and processing. The supported status option for the integrator block is: Use Uncertain as Good, Uncertain if MAN mode. The block input value and status. The block input value and status. The block input value and status. The block input value and status. Parameter to switch off the input from being used. 0 - On, 1 - Off. Parameter to switch off the input from being used. 0 - On, 1 - Off. Parameter to switch off the input from being used. 0 - On, 1 - Off. Parameter to switch off the input from being used. 0 - On, 1 - Off. Determines the selector action: First Good, Minimum, Maximum, Middle, and Average. The minimum number of inputs which are Good is less than the value of MIN_GOOD then set the OUT status to Bad. The integer indicating the selected input number. An operator settable parameter to force a given input to be used. Page 88 FOUNDATION Fieldbus Option User's Manual Rev.5

105 Parameter UPDATE_EVT BLOCK_ALM Description This alert is generated by any change to the static data. The block alarm is used for all configuration, hardware, connection failure, or system problems in the block. The cause of the alert is entered in the subcode field. The first alert to become active sets the Active status in the Status parameter. As soon as the Unreported status is cleared by the alert reporting task, another block alert may be reported without clearing the Active status, if the subcode has changed. Attributes Supported Modes The block supports the following modes: AUTO (Automatic) MAN (Manual) OOS (Out of Service). Alarm Types The block supports standard block alarms, (see section 3.2). Status Handling During normal operations, the value and status of the selected input is shown by OUT. If the number of inputs with Good status is fewer than MIN_GOOD, then the output status is Bad. The SELECTED output status is Good (NC), until the block is out of service. The block supports two status option: Uncertain as Good: If the selected input status is Uncertain, set the OUT status as Good. Uncertain, if in Manual mode: If the block is set to Manual mode, the status of the Output is set to Uncertain. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 89

106 3.12 Integrator block The Integrator block integrates a variable as a function of time, and also accumulates the counts from a Pulse Input block. The block is used as a totalizer that counts up until reset or as a batch totalizer that has a setpoint, and the integrated or accumulated value is compared to pre-trip and trip settings. When the pre-trip and trip settings are reached, the block generates discrete signals. The integrated value can go up, starting from zero, or go down, starting from the trip value depending on the settings. The block has two flow inputs to calculate and integrate net flow, which can be used to calculate volume or mass variation in vessels or as an optimizing tool for flow ratio control. The block does not support process alarms. ATTENTION Alternatively IN_1 and IN_2 can be used as pulse inputs coming from other blocks. The same general rules for integration applies for the accumulation of pulses. Execution Figure 18: Integrator Block The basic function of the Integrator block is to integrate an analog value over time. It can also accumulate the pulses coming from the Pulse Input block or from other Integrator blocks. The block is normally used to totalize flow, giving total mass or volume over a certain time, or totalize power, giving the total energy. Inputs The block has two inputs: IN_1 and IN_2. If IN_2 is not connected (does not have a corresponding link object), calculations for IN_2 can be avoided. Each input can be configured to receive a measurement per unit of time (rate). Page 90 FOUNDATION Fieldbus Option User's Manual Rev.5

107 The usage is as follows: Rate It is used when the variable connected to the input is a rate, that is Kg/s, w, Gal/hour, and so on. This input can come from the rate output OUT of an Analog Input block. Accum It is used when the input comes from the OUT_ACCUM output of a Pulse Input block, which represents a continuous accumulation of pulse counts from a transducer, or from the output of another Integrator block. The bits corresponding to IN_1 and IN_2 can be set to False for Rate, or can be set to True for Accum. If the input option is Rate Each input needs a parameter to define the rate time unit: IN_1, IN_2. The time unit can be selected in seconds/minutes/hours/days. The second analog input must be converted into the same unit as that of the first input. IN_2 must be converted into the same units of IN_1. This can be done by using the parameter UNIT_CONV. For example, if IN_1 is in seconds and if IN_2 is in minutes, IN_2 must be converted to seconds before starting the integration. In this case, the value of UNIT_CONV is.0166 (1/60). To find the mass, volume, or energy increment per block execution, each rate must be multiplied by the block execution time. This increment must be added or subtracted in a register. The following diagram is an example of the use of two Rate inputs: Figure 19: Two Rate Inputs Rev.5 FOUNDATION Fieldbus Option User's Manual Page 91

108 If the input option is Accum The Integrator block determines the number of additional counts from the counter input readings from the last execution. The difference in count is determined as follows: Net Flow If the difference between the reading in one cycle and the reading in the preceding cycle is less than 500,000 or greater than (- 500,000), the difference must be taken as the variation. If the difference between the reading in one cycle and the reading in the preceding cycle is greater than or equal to (+500,000), add (-1,000,000), use the result as the variation. If the difference between the reading in one cycle and the reading in the preceding cycle is more negative than or equal to (-500,000), add (+1,000,000), use the result as the variation. The variation of each input must be multiplied by the value, in engineering units, of each pulse given by PULSE_VAL1 or PULSE_VAL2, as appropriate. The result is the increment in engineering units of, for example, mass, volume or energy per block execution. The Net Flow is calculated by considering the direction of flow. The direction of the flow is calculated by selecting the parameters REV_FLOW and REV_FLOW2. When the status is set to True for any of these two parameters, the direction of the flow for that input is considered (Increment is negative) to be negative and the net flow is calculated by adding the increments for that cycle of execution. In order to integrate the difference between the inflow and outflow of a tank, for example, the second one can be assigned to be negative. The Net Flow direction to be considered in the totalization is defined in INTEG_OPTS. The following options are available: FORWARD = Only positive flows (after application of REV_FLOWi) are totalized. The negative values must be treated as zero. FORWARD is selected when the bit corresponding to Forward is set to True. REVERSE = Only negative flows are totalized. The positive values must be treated as zero. The option bit Reverse must be set to True. Page 92 FOUNDATION Fieldbus Option User's Manual Rev.5

109 Integration of Inputs There are three internal registers used for the totalization: Total = The net increment is added every cycle, irrespective of the status. Atotal = The absolute value of the net increment is added every cycle, irrespective of status. Rtotal = The absolute value of the net increments with status as Bad (rejects) are added to this register. The most significant part of Total can be read in the output OUT, and of Rtotal in RTOTAL. OUT_RANGE is used only for display of the totals by a host. The high and low range values of OUT_RANGE have no effect on the block. Types of Integration The value of OUT can start from zero and go up or it can start from a Setpoint value (TOTAL_SP) and go down. The Reset option can be automatic, periodic, or on demand. This is defined by the enumerated parameter INTEG_TYPE: UP_AUTO It counts up with automatic reset when TOTAL_SP is reached UP_DEM It counts up with demand reset, and the block resets only when the operator resets the block. DN_AUTO The block is reset when the output becomes zero. The integration starts as SP and increments are subtracted from the SP. DN_DEM The output is calculated even beyond zero till the block is reset. The integration starts from SP. PERIODIC The integration is done for the assigned period (specified in seconds in CLOCK_PER). After that period, the block is reset automatically. DEMAND The integration is done (positive or negative depending on the direction of the flow) until the block is reset. PER&DEM It is a combination of periodic and demand types. The integration is carried till the end of the specified period and after that period is automatically reset. The block can be reset at any time, before the end of periodic data set. The first four types indicate use as a batch totalizer with a setpoint TOTAL_SP. The count does not stop at TOTAL_SP going up or zero going down, as it is important to get the True total of flow. Two outputs, OUT_TRIP and OUT_PTRIP, are associated with the four types. The next three types indicate that TOTAL_SP and the trip outputs are not used. The Periodic type (5) disables reset action based on RESET_IN, but has no impact on OP_CMD_INT. The internal registers always add the net increments. Counting down is done by setting OUT to the value of TOTAL_SP minus the most significant part of Total. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 93

110 Resetting the totals The block uses a discrete input RESET_IN to reset the internal integration registers. The operator can send a command to reset the same registers by making OP_CMD_INT = RESET. This is a momentary switch that turns-off when the block is evaluated. The option Confirm Reset in INTEG_OPTS, if set, prevents another reset from occurring until the value 1 has been written to RESET_CONFIRM. This is an input that behaves like a momentary dynamic parameter if it is not connected. The number of resets is counted in the register N_RESET. This counter cannot be written or reset. It provides verification that the total has not been reset since N_RESET was last checked. The counter must roll over from to 0. The reset always clears the internal registers Total, Atotal, and Rtotal, except that when the option UP_AUTO or DN_AUTO is selected, a residual value beyond the trip value may be carried to the next integration if the option Carry is set in INTEG_OPTS. In this case, TOTAL_SP is subtracted from Total, leaving the residual value. Batch totalizer outputs When the integration is counting up (type 1 or 2) and the value of OUT equals or exceeds a value given by TOTAL_SP minus PRE_TRIP, the discrete output OUT_PTRIP is set. When it equals or exceeds a value given by the parameter TOTAL_SP, the discrete output OUT_TRIP is set. OUT_PTRIP remains set. When the integration is counting down (type 3 or 4), it starts from a value given by TOTAL_SP. When the value of OUT is equal to or less than PRE_TRIP, the discrete output OUT_PTRIP is set. When the count reaches zero, the discrete output OUT_TRIP is set. OUT_PTRIP remains set. When a reset occurs, the comparisons that set OUT_PTRIP and OUT_TRIP are no longer True; so they are cleared. OUT_TRIP shall remain set for five seconds after an automatic reset (type 1 or 3), if RESET_CONFIRM is not connected or the option to Confirm Reset in INTEG_OPTS is not set. To determine the amount of Uncertain or Bad readings, the block integrates the variables with Bad, or Bad and Uncertain status separately. The values used in this second integration are the values with Good status, just before the status changed from Good to Bad or Good to Uncertain. The ratio of Good to total counts determines the output status. Absolute values are used to avoid problems with changing signs. Integration options Any or all of the following integration options can be selected: INTEG_OPTS: 0 (Input1 Accumulate) When this option is selected, the accumulation of pulses is done instead of the rate input, integration. INTEG_OPTS: 0 (Input2 Accumulate) When this option is selected, the accumulation of pulses is done instead of the rate input, integration. Note: One input for rate and input for Accumulation can be selected. INTEG_OPTS: 0 (Flow forward) When this option is selected, only positive flows is considered for integration. If there is no forward flow inputs (whose value is positive value), and if one inputs is negative (whose value is positive value) the integration continues. Note: If both the inputs are negative, then the integration stops. Page 94 FOUNDATION Fieldbus Option User's Manual Rev.5

111 INTEG_OPTS: 0 (Flow reverse) When this option is selected, only reverse flows is considered for integration. If there is no reverse flow inputs (whose value is negative), and if one inputs is forward (whose value is positive) the integration continues. Note: If both the inputs are forward, then the integration stops. INTEG_OPTS: 0 (Use uncertain) When this option is selected, the input (IN_1/IN_2) whose status is Uncertain is considered for integration. INTEG_OPTS: 0 (Use Bad) When this option is selected, the input (IN_1/IN_2) whose status is Bad is considered for integration. INTEG_OPTS: 0 (Carry) This option is used only for UP_AUTO and DN_AUTO kind of integrations only. When this option is selected, the residual value after the integration is added / subtracted from the integral value in the next cycle of integration. INTEG_OPTS: 0 (Add Zero if Bad) When this option is selected, if IN_1/IN_2 is bad, the input value is zero for that input and integration does not happen. Integration stops at the last value. INTEG_OPTS: 0 (Confirm reset) This option is to be selected in conjunction with RESET_CONFIRM.VALUE. When the value of RESET_CONFIRM.VALUE is 1, and Confirm Reset is selected, the block gets reset. This is not applicable to UP_AUTO and DN_AUTO types. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 95

112 Parameters List Table 18: Integrator block parameters Parameter ST_REV TAG_DESC STRATEGY ALERT_KEY MODE_BLK BLOCK_ERR TOTAL_SP OUT OUT_RANGE GRAND_DENY STATUS_OPTS IN_1 IN_2 OUT_TRIP OUT_PTRIP TIME_UNIT1 TIME_UNIT2 UNIT_CONV PULSE_VAL1 PULSE_VAL2 REV_FLOW1 REV_FLOW2 Description The revision level of the static data associated with the function block. The user description of the application of the block. Used to identify grouping of blocks. This data is not checked of processed by the block. The identification number of the plant unit. This information may be used in the host for sorting alarms. The actual, target, permitted, ad normal modes of the block. Target: The mode to go to Actual: The mode the block is currently in Permitted: Allowed modes that target may take Normal: Most common mode for target. The summary of active error conditions associated with the block. The block error for the Integrator function block is Out of service. The set point for a batch totalization. The block output value and status. The high and low scale values, engineering units code, and number of digits to the right of the decimal point associated with OUT. Options for controlling access of host computers and local control panels to operating, tuning, and alarm parameters of the block (not used by the device). It helps to select option for status handling and processing. The supported status options for the Integrator block are: Uncertain if Manual mode. The block input value and status. The block input value and status. The first discrete output. The second discrete output. Converts the rate time, units in seconds. Converts the rate time, units in seconds. Factor to convert the engineering units of IN_2 into the engineering units of IN_1. Determines the mass, volume or energy per pulse. Determines the mass, volume or energy per pulse. Indicates reverse flow when True ; 0-Forward, 1-Reverse Indicates reverse flow when True ; 0-Forward, 1-Reverse Page 96 FOUNDATION Fieldbus Option User's Manual Rev.5

113 Parameter Description RESET_IN STOTAL RTOTAL SRTOTAL SSP INTEG_TYPE INTEG_OPTIONS CLOCK_PER PRE_TRIP N_RESET PCT_INC GOOD_LIMIT UNCERTAIN_LIMIT OP_CMD_INT OUTAGE_LIMIT RESET_CONFIRM UPDATE_EVT BLOCK_ALM Resets the totalizers Indicates the snapshot of OUT just before a reset Indicates the totalization of Bad or Bad and Uncertain inputs, according to INTEG_OPTIONS. The snapshot of RTOTAL just before a reset The snapshot of TOTAL_SP. Defines the type of counting (up or down) and the type of resetting (demand or periodic) A bit string to configure the type of input (rate or accumulative) used in each input, the flow direction to be considered in the totalization, the status to be considered in TOTAL and if the totalization residue must be used in the next batch (only when INTEG_TYPE=UP_AUTO or DN_AUTO). Establishes the period for periodic reset, in hours. Adjusts the amount of mass, volume or energy that should set OUT_PTRIP when the integration reaches (TOTAL_SP-PRE_TRIP) when counting up of PRE_TRIP when counting down. Counts the number of resets. It cannot be written or reset. Indicates the percentage of inputs with Good status compared to the ones with Bad or Uncertain and Bad status. Sets the limit for PCT_INC. Below this limit OUT receives the status Good Sets the limit for PCT_INC. Below this limit OUT receives the status Uncertain Operator command RESET Resets the totalizer The maximum tolerated duration for power failure Momentary discrete value with can be written by a host to enable further resets, if the option Confirm reset in INTEG_OPTIONS is chosen. This alert is generated by any changes to the static data. Used for all configuration, hardware, connection failure, or system problems in the block. The cause of the alert is entered in the subcode field. The first alert to become active sets the active status in the status parameter. As soon as the unreported status is cleared by the alert reporting task other block alerts may be reported without clearing the Active status, if the subcode has changed. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 97

114 Attributes Supported Modes The block supports the following modes: AUTO (Automatic) MAN (Manual) OOS (Out of Service). Alarm Types The block supports standard block alarms, (see section 3.2). Status Handling If an input has status as Uncertain or Bad, then the limit status of the inputs is ignored, as is the sub status. Either Good(C) or Good (NC) is accepted as Good. The increment calculated from an input has an internal status that is either Good or Bad. If the input status is Good(C) or Good (NC), the increment status is Good. If the input status is Uncertain, the increment status is Bad, and the last Good value is used unless the option Use Uncertain is set in INTEG_OPTS, and then the increment status is Good and the new value is used. If the input status is Bad, the increment status is Bad, and the last Good value is used unless the option Use Bad is set in INTEG_OPTS, and then the increment status is Good and the last Good value is used. The two increments are added together, and the resulting status is the worst of the two. The option Add zero if Bad in INTEG_OPTS causes the net increment to be zero if its status is Bad. The percentage of Bad or Uncertain and Bad counts can be determined by calculating the value of PCT_INCL from Rtotal and Atotal. As Atotal is the sum of increments with Good and Bad status, and Rtotal is the sum of increments with Bad status, Atotal minus Rtotal is exactly equal to the total of increments with Good status. If most significant part (msp) and Atotal is not zero then the percent of Good values may be calculated as: PCT_INCL = 100 * ( 1 - (msp of Rtotal) / (msp of Atotal) ) If Atotal is zero, then PCT_INCL shall be 100 if Rtotal is also zero or 0 if Rtotal is not zero. If the block mode is AUTO, if PCT_INCL GOOD_LIM, the status of OUT is Good, or else if PCT_INCL UNCERT_LIM, the status of OUT is Uncertain, or else the status of OUT is Bad. If the block mode is Manual, then the status of OUT, OUT_PTRIP, and OUT_TRIP is Good (NC) constant when then status option Uncertain, if MAN is not selected. If this status option is selected and the block mode is manual, then the status of these three outputs is for Uncertain constant, and no limits are applied to the output. Page 98 FOUNDATION Fieldbus Option User's Manual Rev.5

115 3.13 Arithmetic block The Arithmetic block is designed for using popular measurement math functions easily. The math algorithm is selected by name and the type of function to be performed. The block is used for calculating measurements from a combination of signals from the sensors. The block must not be used in a control path. The block does not support process alarms. The Arithmetic block supports the following functions: Flow compensation, linear Flow compensation, square root Flow compensation, approximate BTU flow Traditional Multiply Divide Average Traditional Summer Fourth order polynomial Simple HTG compensated level Fourth order Polynomial Based on PV Figure 20: Arithmetic Block Execution The block has five inputs, namely IN, IN_LO, IN_1, IN_2, and IN_3. The first two inputs (IN, IN_LO) are designed for a range extension function that results in a Process Variable (PV), with the status indicating the input in use. The remaining three inputs (IN_1, IN_2, and IN_3) are combined with the PV in a selection of four term math functions. To ensure that the PV enters the equation with the right units, the inputs used to form the PV must come from devices with the desired engineering units. Each additional input has a bias constant and gain constant. To correct Absolute Pressure, use the bias constant, and to normalize terms within a square root function, use the gain constant. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 99

116 Figure 21: Arithmetic Schematic Diagram Calculation of PV The range extension function has a graduated transfer controlled by two constants referenced to IN. An internal value, g, is zero for IN less than RANGE_LO. It is one when IN is greater than RANGE_HI. It is interpolated from zero to one over the range of RANGE_LO to RANGE_HI. The equation for PV follows: PV = g IN + (1 g) IN_LO If the status of IN_LO is not usable and IN is usable and greater than RANGE_LO, then g is set to one. If the status of IN is unusable, and IN_LO is usable and less than RANGE_HI, then g is set to zero. For three auxiliary inputs, six constants are used, and each input has a BIAS_IN_i and a GAIN_IN_i. The output has a BIAS and a GAIN static constant. For the inputs, the bias is added, and the gain is applied to the sum. The result is an internal value called t_i in the function equations. The equation for each auxiliary input is the following: t_i = (IN_i + BIAS_IN_i) GAIN_IN_i If an auxiliary input is unstable, to assure smooth degradation, the flow compensation functions have limits on the amount of compensation applied to the PV. The internal limited value is f. Page 100 FOUNDATION Fieldbus Option User's Manual Rev.5

117 The following function types are supported: 1. Flow compensation, linear. Used for density compensation of volume flow. func = f PV f = (t_1) (t_2) [limited] 2. Flow compensation, square root. Usually, IN_1 is pressure, IN_2 temperature and IN_3 is the compressibility factor Z. func = f PV f = (t_1) (t_2) (t_3) [limited] 3. Flow compensation, approximate. Both IN_2 and IN_3 would be connected to the same temperature. f = (t_1) (t_2) (t_3) (t_3) [limited] func = f PV 4. BTU flow, where IN_1 is inlet temperature, and IN_2 the outlet temperature. func = f PV f = (t_1 t_2) [limited] 5. Traditional Multiply Divide func = f PV f = (t_1) + (t_3) [limited] (t_2) 6. Average func = (PV + (t_1) + (t_2) + (t_3)) f f = number of inputs used in computation (unusable inputs are not used). 7. Traditional Summer func = PV + (t_1) + (t_2) + (t_3) 8. Fourth order polynomial. All inputs except IN_LO (not used) are linked together. func = PV + (t_1) 2 + (t_2) 3 + (t_3) 4 Rev.5 FOUNDATION Fieldbus Option User's Manual Page 101

118 9. Simple HTG compensated level, where PV is the tank base pressure, IN_1 is the top pressure, IN_2 is the density correction pressure, and GAIN is the height of the density tap. func = (PV (t_1)) (PV (t_2)) 10. Fourth order polynomial based on PV func = PV + GAIN_IN_1 (PV) 2 + GAIN_IN_2 (PV) 3 + GAIN_IN_3 (PV) 4 After the value of func is calculated, it is multiplied by GAIN, and then BIAS is added to the result. Then, the high and low output limits are applied as per configured range scaling, and PRE_OUT is updated with the calculated value. If the mode is AUTO, PRE_OUT is copied to OUT. Parameter List Table 19: Arithmetic block parameters Parameter ST_REV TAG_DESC STRATEGY ALERT_KEY MODE_BLK BLOCK_ERR PV OUT PRE_OUT PV_SCALE OUT_RANGE GRANT_DENY Description The revision level of the static data associated with the function block. The revision value increments each time a static parameter value in the block is changed. The user description of the application of the block. Used to identify grouping of blocks. This data is not checked of processed by the block. The identification number of the plant unit. This information may be used in the host for sorting alarms, etc. The actual, target, permitted, ad normal modes of the block. Target: The mode to go to Actual: The mode the block is currently in Permitted: Allowed modes that target may take Normal: Most common mode for target. This parameter reflects the error status associated with the hardware or software components associated with a block. It is a bit string so that multiple errors may be shown. It calculates the proportions of IN and IN_LO to for PV. The analog output value and status. Displays what would be the OUT value if the mode is AUTO or lower. The high and low scale values, the engineering units code, and the number of digits to the right of the decimal point associated with the PV. The high and low scale values, engineering units code, and number of digits to the tight of the decimal point associated with OUT. Options for controlling access of host computers and local control panels to operating, tuning, and alarm parameters of the block. (Not used by the device) Page 102 FOUNDATION Fieldbus Option User's Manual Rev.5

119 Parameter INPUT_OPTIONS IN IN_LO IN_1 IN_2 IN_3 RANGE_HI RANGE_LO BIAS_IN_1 GAIN_IN_1 BIAS_IN_2 GAIN_IN_2 BIAS_IN_3 GAIN_IN_3 COMP_HI_LIM COMP_LO_LIM ARITH_TYPE BAL_TIME BIAS GAIN OUT_HI_LIM OUT_LO_LIM UPDATE_EVT BLOCK_ALM Description Option bit string for handling the status of the auxiliary inputs. The block input value and status. Input of the low range transmitter, in a range extension application. The first block input value and status. The second block input value and status. The third block input value and status. Constant value above which the range extension has switch to the high range transmitter. Constant value below which the range extension has switch to the high range transmitter. The bias value for IN_1. The proportional gain (multiplier) value for IN_1. The bias value for IN_2. The proportional gain (multiplier) value for IN_2. The bias value for IN_3. The proportional gain (multiplier) value for IN_3. Determines the high limit of the compensation input. Determines the low limit of the compensation input. The set of 9 arithmetic functions applied as compensation to or augmentation of the range extended input. Specifies the time for a block value to match an input, output, or calculated value or the time for dissipation of the internal balancing bias. The bias value is used to calculate the output. The gain value is used to calculate the output. The maximum output value allowed. The minimum output value allowed. This alert is generated by any changes to the static data. Used for all configuration, hardware, connection failure, or system problem in the block. The cause of the alert is entered in the subcode field. The first active alarm sets the active status in the status parameter. When the Unreported status is cleared by the alert reporting test, other block alert may be reported without clearing the Active status, if the subcode has changed. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 103

120 Attributes Supported Modes The block supports the following modes: AUTO (Automatic) MAN (Manual) OOS (Out of Service). Alarm Types The block supports standard block alarms, (see section 3.2). Status Handling The INPUT_OPTS bit string controls the use of auxiliary inputs with less than Good status. The status of unused inputs is ignored. The status of the output is the worst of the inputs used in the calculation after applying INPUT_OPTS. Page 104 FOUNDATION Fieldbus Option User's Manual Rev.5

121 3.14 Signal Characterizer block The Signal Characterizer block describes the input/output relationship for any type of function. The block has two paths, each with an output that is a non-linear function of the corresponding input. The non-linear function is configured based on a single look-up table with 21 arbitrary x-y pairs. To use the block in a control or process signal path, the status of an input is provided to the corresponding output. To use the backward control path, the block provides an option to swap the axes of the function. Figure 22: Signal Characterizer Block The block calculates OUT_1 from IN_1 and OUT_2 from IN_2 using a curve given by the coordinates: [x1; y1], [x2; y2]... [x21; y21] Where, x is the Input and y is the Output. The x-coordinates are given in engineering units of X_RANGE. The y-coordinates are given in engineering units of Y_RANGE. Execution Figure 22 describes the components of the block. The output value is calculated by linear interpolation between two points enclosing the input value. OUT_1 is associated to IN_1 and OUT_2 to IN_2 by the same curve, but there is no association between IN_1 and IN_2 or between OUT_1 and OUT_2. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 105

122 To derive the output value that corresponds to the input, use the following formula, y = mx + c Where, m is the slope of the line. c is the y-intercept of the line Figure 23: Signal Characterizer Curve The values of x must increase sequentially for interpolation to be applicable. If not, a configuration error is set in BLOCK_ERR, and the Actual mode of the block goes to Out of Service mode. If the curve has m points, m<21, the non-configured points, [xm+1; ym+1], [xm+2; ym+2], [x21; y21] is set to +INFINITY to mark them as unused. Since x1 is the smallest specified value for the input and x m is the largest, the output is at y1 when the input is smaller than x1, and the output is at y m when the input is larger than x m. Since the ends of the y curve act as limits, the OUT status is shown when either limit is active. Backward Control path A reverse function swaps the interpretation of IN_2 and OUT_2 that provides a way to do reverse calculation using the same curve. If the parameter SWAP_2 is set to True, the block provides: IN_1 = x and OUT_1 = y while IN_2 = y and OUT_2 = x If the function is not sequential in y and SWAP_2 is True, BLOCK_ERR indicates a configuration error, and the Actual mode goes to Out of Service mode for x. A function is said to be sequential when y values always increase or decrease when x values increase. If SWAP_2 = False, IN_1 and IN_2 have the same engineering units defined in X_RANGE and OUT_1 and OUT_2 use the units defined in Y_RANGE. If SWAP_2 = True, OUT _1 and IN_2 have Y_RANGE and OUT_2 and IN_1 have X_RANGE. Page 106 FOUNDATION Fieldbus Option User's Manual Rev.5

123 Parameter list Table 20: Signal Characterizer block parameters Parameter ST_REV TAG_DESC STRATEGY ALERT_KEY MODE_BLK BLOCK_ERR OUT_1 OUT_2 X_RANGE Y_RANGE GRANT_DENY IN_1 IN_2 SWAP_2 CURVE_X CURVE_Y UPDATE_EVT BLOCK _ALM Description The revision level of the static data associated with the function block. The revision value is incremented each time a static parameter value in the block is changed. The use description of the intended application of the block. The strategy field can be used to identify grouping of blocks. This data is not checked or processed by the block. The identification number of the plant unit. This information may be used in the host for sorting alarms, etc. The actual, target, permitted, ad normal modes of the block. Target: The mode to go to Actual: The mode the block is currently in Permitted: Allowed modes that target may take on Normal: Most common mode for target This parameter reflects the error status associated with the hardware or software components associated with a block. It is a bit string so that multiple errors may be shown. The block output value and status. The block output value and status. The display scaling of the variable corresponding to the x-axis for display. It has no effect on the block. The display scaling of the variable corresponding to the y-axis for display. It has no effect on the block. Options for controlling access of host computers and local control panels to operating, tuning, and alarm parameters of the block. (Not used by the device) The block input value and status. The block input value and status. Changes the algorithm in such a way that IN_2 corresponds to y and OUT_2 to x. Curve input points. The x points of the curve are defined by an array of 21 points. Curve input points. The y points of the curve are defined by an array of 21 points. This alert is generated by any changes to the static data. The block alarm is used for all configuration, hardware, connection failure, or system problems in the block. The cause of the alert is entered in the subcode field. The first alert to become active sets the active status in the status parameter. As soon as the Unreported status is cleared by the alert reporting task other block alerts may be reported without clearing the active status, if the subcode has changed. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 107

124 Attributes Supported Modes The block supports the following modes: AUTO (Automatic) MAN (Manual) OOS (Out of Service). Alarm Types The block supports standard block alarms, (see section 3.2). Status Handling OUT_1 shows the status of IN_1 and OUT_2 shows the status of IN_2. The sub-status is also passed to the outputs. If one of the curve limits is reached or the input is limited, the appropriate limit must be indicated in the output sub-status. Limits shall be reversed if the curve slope is negative. If SWAP_2 is set, cascade initialization is controlled by the lower block. When this block is in OOS mode, the cascade to both the lower and upper blocks is broken by Bad status at the outputs. When the block goes to AUTO mode, the lower block can begin cascade initialization with status values that pass through this block to the upper block. The output status signals from the upper block pass through this block to the lower block. The block does not use STATUS_OPTS. Page 108 FOUNDATION Fieldbus Option User's Manual Rev.5

125 3.15 Output Splitter block The output splitter block drives two control output signals from a single input signal. Each output is a linear function of a fraction of the input signal. The same linear function when used in reverse provides the back calculation support. For different combinations of input and output conditions, a decision table supports cascade initialization. This block finds application in split ranging or sequencing of multiple valve. In a typical split range application, when the splitter input is 50% both the output valves remain closed. One of the valves opens proportionately to full as the input drops to 0% and the other valve opens proportionately as the input rises above 50%. In a typical sequencing application, both the valves are closed at 0% input. One of the valves opens proportionately to full as the input rises to 50%, while the other stays shut. The second valve opens as the input rises above 50%, and the first valve may remain open or shut off quickly. As this block is in the control path, it has the ability to pass limit and cascade initialization information back to the upstream block. Figure 24: Output Splitter Block Execution Figure 25: Output Splitter Schematic The relationship of each output to the input may be defined by a line. Each line may be defined by its endpoints. Examples of graphical representations of OUT_1 and OUT_2 vs. SP are shown below for a split range and a sequencing application. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 109

126 Figure 26: Split Range and Sequence Operation The examples shown do not show the full range of possibilities. The lines could overlap like an X, or both start from the origin but have different slopes. The endpoints do not have to lie within 0-100%. Limits in the external blocks may affect the useful range of a line. Units of percent are used in the examples because the common application of this block is to valves, but any units may be used to suit the application. The following parameters may be used to specify the output splitter operation: X11, Y11, X12, Y12 X21, Y21, X22, Y22 Where XnJ is the value of SP associated with OUT_n and Xn1 and Xn2 refer to the 1st and 2nd coordinates of the nth curve respectively. YnJ is the value of OUT_n and Yn1 and Yn2 refer to the 1st and 2nd coordinates of the nth curve respectively. IN_ARRAY OUT_ARRAY Index Coordinate Index Coordinate 1 X11 Start value of SP for the OUT_1 line.(x11<x12) 2 X12 End value of SP for the OUT_1 line.(x11 <X12) 3 X21 Start value of SP for the OUT_1 line.( X21 <X22) 4 X22 Start value of SP for the OUT_1 line.( X21 <X22) 1 Y11 Value of OUT_1 at X11 2 Y12 Value of OUT_1 at X12 3 Y21 Value of OUT_2 at X21 4 Y22 Value of OUT_2 at X22 By specifying the coordinates as shown above, the endpoints of the lines are defined. The contents of the respective X s are held in the IN_ARRAY parameter and the contents of the respective Y s are held in the OUT_ARRAY parameter. If a set of points are specified such are held in the IN_ARRAY parameter and the contents of the respective Y s are held in the OUT_ARRAY parameter. If a set of points are specified such that a region of the input range is not specified, then the corresponding OUT_n may be set to the closest endpoint of the input value, either high or low, when the specified region is exceeded. Page 110 FOUNDATION Fieldbus Option User's Manual Rev.5

127 A configuration error shall be set in BLOCK_ERR and the actual mode of the block shall go to Out of Service if the X values have any of the following conditions: X21 < X11, X12 <= X11, X22 <= X21. The parameter LOCKVAL provides an option to specify whether OUT_1 remains at its ending level when control is switched to OUT_2, or goes to Y11. If LOCKVAL is LOCK, OUT_1 remains at its ending value when X is greater than X12. If LOCKVAL is NO LOCK, then OUT_1 goes to Y11 when X is greater than X12. Some hysteresis in the switching point may be required because the output may change by a full stroke of the valve. HYSTVAL contains the amount of hysteresis. If X <= X12-HYSTVAL, OUT_1 may be determined by the calculated y value. If X12-HYSTVAL < X < X12 and X has not reached X12 since it was less than X12-HYSTVAL, OUT_1 may be determined by the calculated y value. If X transitioned from a value > X12 to a value where X12-HYSTVAL < X < X12, then the value of OUT_1 is determined by the LOCKVAL setting. If X12 < X, OUT_1 may be determined by the LOCKVAL setting. In the following example LOCKVAL = LOCK : Figure 27: OUT with LOCKVAL LOCK In this example LOCKVAL= NOLOCK Figure 28: OUT with LOCKVAL NO LOCK Rev.5 FOUNDATION Fieldbus Option User's Manual Page 111

128 Parameter list Table 21: Output Splitter block parameters Parameter Description ST_REV TAG_DESC STRATEGY ALERT_KEY MODE_BLK BLOCK_ERR SP OUT_1 OUT_2 OUT_1_RANGE OUT_2_RANGE GRANT_DENY STATUS_OPTS CAS_IN BKCAL_OUT IN_ARRAY OUT_ARRAY LOCKVAL BKCAL_IN_1 The revision level of the static data associated with the function block. The user description of the application of the block. Used to identify grouping of blocks. The identification number of the plant unit. The actual, target, permitted, and normal modes of the block. Reflects the error status of the hardware or software components associated with a block. It is a bit string, so that multiple errors may be shown. It is the target block setpoint value. It is the result of setpoint limiting and setpoint rate of change limiting. The value and status of out_1 of the block. The value and status of out_2 of the block. The maximum value range of out_1 of the block. The maximum value range of out_1 of the block. Options for controlling access of host computers and local control panels to operating, tuning, and alarm parameters of the block. Not used by the device. Helps select options for status handling and processing. The supported status options for the OS block are IFS if Bad CAS_IN and Target to next permitted mode if BAD CAS_IN. The remote setpoint value from another block. The value and status required by the BKCAL_IN input of another block to prevent reset windup and to provide bump less transfer of closed loop control. An array which contains the values of the input or X variables. An array which contains the values of the output or Y variables. Flag for holding the first output at current value when the other output is non-zero. The analog input value and status from another block s BKCAL_OUT output that is used for backward output tracking for bump less transfer and to pass limit status. Page 112 FOUNDATION Fieldbus Option User's Manual Rev.5

129 Parameter BKCAL_IN_2 BAL_TIME HYSTVAL UPDATE_EVT BLOCK_ALM Description The analog input value and status from another block s BKCAL_OUT output that is used for backward output tracking for bump less transfer and to pass limit status. The specified time for the internal working value of bias to return to the operator set bias. Also used to specify the time constant at which the integral term moves to obtain balance when the output is limited and the mode is AUTO, CAS, or RCAS. Specifies the Hysteresis value. This alert is generated by any change to the static data. The BLOCK_ALM is used for configuration, hardware, and connection failure or system problems in the block. The cause of the alert is entered in the subcode field. The first alert to become active sets the Active status in the Status attribute. When the Unreported status is cleared by the alert reporting task, another block alert is reported without clearing the Active status, if the subcode has changed. Attributes Supported Modes Alarm Types Status Handling The block supports the following modes: AUTO (Automatic) IMAN (Manual) OOS (Out of Service) Cas Standard block alarm Sub-status values received at CAS_IN shall be passed to both outputs, except for those used in the cascade handshake. An IFS shall go to both outputs. The status option IFS if Bad CAS_IN is available. The splitter block shall propagate the BKCAL_IN status of Bad, Device failure or Good Cascade, Fault State Active or Local Override only if the statuses of both BKCAL_IN s contain a propagated fault status Configuring the transmitter using Field Device Manager system The transmitter can be configured through Field Device Manager (FDM), by using DTM for releases R410 and R430 and using DD as well as DTM for release R440 and R450. For more information, refer the FDM manuals #EP-FDM-11410, #EP-FDM and #EP-FDM for the corresponding releases. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 113

130 4. SLG 700 FF Level Transmitter operation 4.1 Operational considerations There are a number of considerations that must be noted when configuring a transmitter to operate in a fieldbus network. LAS Capability The transmitter is capable of operating as the Link Active Scheduler (LAS). The LAS is a fieldbus feature which controls traffic on the network, such as controlling token-rotation and coordinating data publishing. This fieldbus function is active in only one device at any given time on a network. Devices which can be designated as the LAS may be an operator station or a field device. The transmitter can be designated as LAS, in the event of a failure of the primary LAS, control in the field could continue. ATTENTION Note that the transmitter can be used only as backup LAS. Special Non-volatile parameters and NVM Wear-out All function block parameters designated as Non-Volatile (N) in the FF specifications are updated to non-volatile memory (NVM) on a periodic basis. NV_CYCLE_T parameter in the resource block specifies this update interval. To provide predictable restart behavior in the transmitter, the following Non-Volatile parameters are updated to NVM each time they are written over the fieldbus. MODE.TARGET for all blocks SP.VALUE for the PID block Since these are user-written parameters, these additional updates to NVM contribute negligibly to NVM wear out. However, users are cautioned to not construct control configurations where the above parameters are written continuously (via a computer application for example) or at rates greater than the NV_CYCLE_T interval. This consideration helps to minimize the possibility of NVM wear-out. In the case of MODE this must not be a problem. When users wish to provide set-points to the PID block via a computer application, users should use RCAS mode with its corresponding setpoint value RCAS_IN. RCAS_IN is updated only at the NV_CYCLE_T update rate and this mode supports full shedding functionality and PID initialization necessary for a robust application. Mode Restricted Writes to Parameters Some block parameters have restrictions on having write access to them. These are specified in the FF specifications. Writing to certain function block parameters are restricted based on the block s Target and/ or Actual mode. Page 114 FOUNDATION Fieldbus Option User's Manual Rev.5

131 4.2 Configuration of the transmitter using Handheld (HH) Figure 29 graphically represents the connection of the transmitter to the handheld. Each transmitter includes a configuration database that stores its operating characteristics in a non-volatile memory. The handheld is used to establish and/or change selected operating parameters in a Transmitter database. The process of viewing and/or changing database parameters is called configuration. Configuration can be accomplished both online and offline with the Transmitter powered up and connected to the handheld. The online configuration immediately changes the Transmitter operating parameters. For offline configuration, Transmitter operating characteristics are entered into the handheld memory for subsequent downloading to a Transmitter. Figure 29: Connecting the transmitter to the handheld Rev.5 FOUNDATION Fieldbus Option User's Manual Page 115

132 4.3 Performing block instantiation About block instantiation A block instance is a copy of an available block in the device, say for example AI block. There are a total of 11 permanent blocks and only five blocks support instantiation in a device. The five blocks that support instantiation are: Analog Input Block Arithmetic Block Signal Characterizer Block Input Selector Block PID Block Five instances of the Analog Input block, and one instance of Arithmetic block, one instance of Signal Characterizer Block, one instance of Input Selector Block and one instance of the PID block can be instantiated. A block can be instantiated or deleted. Before block instantiation, the device checks whether the particular block is supported, and if there is sufficient memory to store the parameters. After Instantiation, the instantiated block must be loaded into the device, and then the strategies can be created. Block instantiation using Experion PKS The following are the steps for performing block instantiation using Experion PKS. Step Action From the DD at the Library-Containment window, select an instantiation block from the supported blocks, that is Analog Input block, or Input Selector block, or Signal Characterizer block. Drag and drop the required instantiation block into the device on the Project- Assignment window. After adding the instantiation block into the device in the Project- Assignment window, select the device. Right-click the device, and click Load. The instantiated block is loaded into the device. Page 116 FOUNDATION Fieldbus Option User's Manual Rev.5

133 5. SLG 700 FF Level Transmitter maintenance 5.1 Replacing the Local Display and Electronic Assembly For more information about Local Display and Electronic Assembly. Refer to the SLG 700 SmartLine Level Transmitter Guided Wave Radar User s Guide, Document #34- SL or spares replacement instruction sheet 34-ST Downloading the firmware The device allows the upgrade of the firmware irrespective of hardware/software write protect mode. Note: Device is protected in Experion user level. Refer to spares replacement instruction sheet 34-ST ATTENTION In the SLG 700 FF level transmitter, only communication board firmware can be upgraded using the class 3 download. Display and sensor boards firmware upgrade is not possible through FF link. About firmware download feature The download class indicates how the device operation is affected by the download process. There are three types of download classes (1, 2 & 3). The transmitter supports only one type of download class as per FOUNDATION Fieldbus specifications. SLG 700 device FF variant supports download type Class 3 only. A class-3 firmware download is performed, irrespective of whether the device is ON /OFF process. Class 3 When class 3 download is performed the device prepares for the download and goes out of the link as the memory of the device is re-written with the new firmware. After the restart of the device, the device comes back to the link automatically. However, the device retains the following credentials: Retains its original device identification Retains only its System Management VFD in its VFD_LIST Retains its Node Address and PD Tag (only when the same firmware version is reloaded) Retains its management VCR to provide access to the SMIB. SAT Tool Using SAT Tool Communication board, Display board and sensor board firmwares can be upgraded. Download SAT Tool, communication board, Display board and sensor board firmware files from: Go to Software tab Rev.5 FOUNDATION Fieldbus Option User's Manual Page 117

134 Recommendations For Communication board download. If a firmware upgrade is required for a large number of SLG 700 devices, follow these guidelines: 1. Diagnostics must be backed-up before initiating the firmware update. The communication board diagnostics are initialized to zero if backup is not performed before initiating the firmware update. The backup diagnostics method is available in the Diagnostics transducer block. 2. Only one device firmware download is allowed in a given H1 Link: Firmware download to multiple devices must happen one after another in the same link. However, parallel downloads can be performed to devices on different H1 links. 3. Download firmware to one device type at a time in a H1 link: This reduces the chance for unknown interactions between devices to cause link issues or download failures. 4. Reduce usage of DTM through tools like FDM in the H1 link: This reduces the traffic on the link and therefore reduces the time required for the download to complete. 5. Parallel Firmware downloads from single Control Builder Firmware downloads to a single FIM should be done from single Control Builder instance. This reduces the chance of initiating multiple downloads to the same H1 link from different users. 6. FF segment design (the choice of devices to connect to a FF segment) must consider the maximum current draw of those devices, as well as the potential for inrush current during power-up. For reference, the SLG 700 provides the following: Max current draw (observed during firmware download): 28mA Normal quiescent current: 18 ma Inrush when powered on: 28 ma Page 118 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

135 Downloading the File The firmware file to be downloaded is called as Gendomain file and have the file extension.ffd. File Name The file name is constructed as follows: Manufacturer ID + _ + Device Type + _ + Domain Name + _ + Software Name + _ + Software Revision +. + ffd, where: Manufacturer ID is represented as six hexadecimal digits (leading and trailing zeroes are included). Device Family is represented as four hexadecimal digits (leading and trailing zeroes are included). For Multidomain devices, Device Family is replaced by Multidomain Family. Device Type is represented as four hexadecimal digits (leading and trailing zeroes are included). Leading 0 s are not suppressed for Manufacturer ID and Device Type. Trailing blanks are stripped from Device Family, Domain Name, Software Name, and Software Revision. If Software Name or Software Revision is composed of all blanks, then the underscore that would have proceeded is omitted to prevent names with two adjacent underscores, or from having the underscore character appear directly before the.ffd. For example, if the file contains the following header values: Manufacturer ID = 48574C Device Type = 0007 Domain Name = FD-DOM Software Name = FD_SW Software Revision = 2-41 Then the file name would be: 48574C0007_0007_FD-DOM_FD-SW_2-41.ffd. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 119

136 6.1 Introduction 6. Using the DTM SLG 700 Fieldbus models support DTMs running on PACTware or FDM / Experion. To set up the DTM network on the FDM/Experion, refer to the FDM/Experion User Guide. In this manual, the procedure is given to run the SLG 700 FF DTM on PACTware (Version 4.1 or above). 6.2 Components In order to be able to use the FF DTM the user needs the following: PACTware or some other Container application. Microsoft.NET Framework. Latest FF Communication DTM: Free version of FF Communication DTM available for download from CodeWrights website. The SLG700 FF DTM can be downloaded from Honeywell website: NI FBUS communication modem. NI FBUS communication modem driver (Available at Downloads Download 1: PACTware 4.x and.net 2.0 Download from Download 2: FF Communication DTM Download from Download 3: Honeywell FF DTM Library Download from HPS web site: Download 4: NI FBUS modem driver Download from web site: Page 120 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

137 6.4 to Install and launch the DTM 1. Install the softwares described in section Connect the Transmitter to the FF power conditioner. 3. Connect the NI modem at FF link terminal on power conditioner board. 4. Connect other end of NI modem USB connector to the PC COM port. 5. Run PACTware and select the Device Catalog option under the View menu. The Device Catalog window should open to the right-hand side of the display. 6. Click on the Update Device Catalog button at the bottom of the Device Catalog window and click on Yes in the confirmation pop-up window. 7. Select the Project option on the Window menu to close the Device Catalog window and select the top level of the project view, which may be labeled HOST PC. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 121

138 8. Right click on the selected project and select Add Device from the context menu. 9. In the device pop-up window select the FF H1 Communication DTM device and click on the OK button at the bottom of the window. Page 122 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

139 10. The popup will be appear as below then click on Yes. 11. Right click on the FF H1 Communication DTM device in the project view and select Add Device from the context menu. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 123

140 12. In the device pop-up window select the SLG700 device that matches the transmitter model, SLG 700 Rev.1 R100, Rev.2 R101 and Rev.3 R Click on the OK button at the bottom of the window. 14. Right click on the SLG700 FF device in the project menu. 15. Select Connect from the context menu. After a few seconds the device label should turn to bold. Page 124 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

141 16. Right click on the FF H1 Communication DTM device in the project view and select Additional functions. 17. Then select Set DTM Address from the context menu. The new window will open then provide device address(device to be commissioned before this with experion or NI host) Double click on the SLG700 Rev.1 R100 or Rev.2 R101 or Rev.3 R102 in the project window depending on which firmware version is running on the SLG700 transmitter. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 125

142 The SLG700 Welcome screen will be displayed while the DTM is reading some basic configuration parameters from the transmitter. When the initial reading of data is completed then the user can observe each transducer block menu to advance to the main menu items. 1. Go through the respective block and perform action, for example double click on LEVELTB block and click on menu DEVICE and then tick the block mode target as OOS to configure the parameters. 2. The above statement can be applicable for all the blocks to configure the parameters. Page 126 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

143 6.5 DTM Help Take the mouse over the symbol next to a parameter to read its description. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 127

144 6.6 Level Transducer block configuring The Level Transducer block has all the basic configuration parameters and functions required to measure and calculate the level. Completion of the Level Transducer Block (Level TB) is a quick way to start operating the SLG 700 transmitter in most applications. This configuration consists of few parameters. Level TB contains three main menus Device, Process & Diagnostics Device menu: This menu contains three tabs namely Block modes, Ranges & Sensor. Block Mode: This menu provides facility to the user to select the mode of the target/device, to configure any parameter user has to keep the target mode as OOS, if it is in AUTO mode then user can t configure the parameters. User can also configure the Permitted mode & normal mode. Page 128 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

145 Ranges Using this tab Level range, Product volume range & Level rate range and its units can be configured. Level: mm, cm, m, in, ft Level Rate: m/s, m/h, in/s, in/min, ft/s, ft/min Volume: l, m³, in³, ft³, yd³, US gal, US bbl (liq), US bbl (oil), imp gal Rev.5 FOUNDATION Fieldbus Option User's Manual Page 129

146 Sensor This menu contains parameters which are related to sensor such as sensor serial Number, Hardware revision, firmware version of sensor, etc. Device Reset will be part of Field Diagnostics, which is available under Resource block. Page 130 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

147 Process menu: This menu contains sub menus like Process configuration, Process variables and Trends as shown below. The Process configuration menu groups the most commonly modified parameters into five categories; Process, Measurement, Probe, Mounting & Attenuation. The parameters in these groups address the major site-specific configuration that might be needed during the commissioning of a transmitter. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 131

148 Process The four parameters in this group allow the products involved in the process of operating the tank to be identified, as shown. The first consideration to be made is the number of products involved, and secondly the dielectric constant of each product. The dielectric constant of a medium affects radar measurements in two ways: 1. Pulses travelling through a medium are slowed by an amount related to the dielectric constant. 2. The relative amount of the original pulse that is reflected from the boundary between two mediums is related to the dielectric constants of the media on each side of the interface. For the reflected pulse, the reduction in the amplitude with respect to the original pulse amplitude can be calculated from the dielectric constants of the media on each side of the interface. Common dielectric constants can be found from the pull-down lists. If a material is not present on the list or if the dielectric constant is not correct, the correct value can be input in the box. Page 132 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

149 Measured Products: This configuration parameter allows the number of products in the tank to be identified. The available options are: Single Liquid: In this application the SLG 700 measures the level of one liquid product in the tank with a vapor, which is usually air, above the product. This application is shown in Figure 30. Figure 30: Single Liquid Two Liquids Flooded: In this application there are two liquid products in the tank; one supported on top of the other, as shown below in Figure 31. As the name indicates, the tank is always full with the Upper Product occupying the entire upper portion of the tank so that there is no vapor above the Upper Product. The SLG 700 measures the level of the interface (boundary) between the two liquid products in the tank. Figure 31: Two Liquids Flooded Rev.5 FOUNDATION Fieldbus Option User's Manual Page 133

150 Two Liquids Non-Flooded: In this application there are also two liquid products in the tank, however, the tank is not normally full so that there is a vapor above the Upper Product, as shown below in Figure 32. The SLG 700 measures the total level of the products in the tank as well as the level of the interface (boundary) between the two liquid products in the tank. Figure 32: Two Liquids Non-Flooded Vapor Dielectric Constants: Depending on the selection above, the user interface allows users to enter values for the dielectric constant (DC) for each of the products present, as shown in Table 22. Table 22 - Dielectric Constants Required by Application Single Liquid Two Liquid Non-Flooded Two Liquid Flooded Vapor DC Vapor DC Product DC Upper Product DC Upper Product DC Lower Product DC Lower Product DC The dielectric constant of most gasses is very close to 1.0 and the Vapor Dielectric Constant parameter will most often not need to be edited. Enter the correct value if it is significantly different than 1.0. Upper Product/Lower Product: For liquid products the dielectric constants vary much more. For the two liquid applications, the value entered for the Upper Product Dielectric Constant will have a significant impact on the accuracy of the reported Interface Level. Two Liquids Flooded, Two Liquids Non-Flooded. Entering of the correct value for the DC of the Upper Products ensures accurate measurement of the Interface, because the speed of the measuring signal varies with the DC of the Upper Product. Page 134 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

151 Measurement Most customers are more interested in the height of the liquid surface or interface relative to some lower datum point, such as the bottom of the tank, rather than the transmitter s reference plane. Measurements made relative to this lower, user-defined datum point are referred to as levels to distinguish them from the distances measured from the transmitter s datum point. In order to convert distance measurements to level measurements, the following parameters are used to describe the geometry of the installation: Sensor Height (A): Height of the transmitter's Reference Plane above some userdefined fixed bottom reference plane. This fixed bottom reference plane should be a location from which accurate measurements to the reference Plane can be obtained. It may be the bottom of the vessel but it may also be the ground or other convenient location and does not necessarily have to be the plane that represents a level of 0.0. Level Offset (C): The distance between the fixed bottom reference plane and the plane that represents a level of 0.0. This offset may be positive (upward), negative (downward) or zero if it coincides with the bottom reference plane. This offset defines the zero point for the transmitter's level measurements. Maximum Product Level (B): The maximum level reading, in length units, above the Level Offset point that is expected when the tank is considered full. This parameter is used primarily to allow the level to be reported in units of % as well as in the specified length units. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 135

152 Probe Length: The distance from the transmitter s Reference Plane to the end of the probe. This parameter is normally entered by the factory based on the model number ordered and does not need to be changed. See SLG 700 Transmitter User s manual #34-SL for trimming probes. For coax probes and rod probes without a centering disk the distance to enter is the distance to the physical end of the probe. For rod probes with a centering disk attached the distance to the top surface of the disk should be entered. For wire probes with an end-weight attached it should be the distance to the top of the end weight. Reference plane R The GWR transmitter inherently measures the time of flight of radar pulses that reflect off the boundary between two different mediums. This time is first transformed into a measure of the distance between a fixed point on the transmitter body, referred to as the Reference Plane, and the boundary between the two medium. The Reference Plane has been chosen to be a flat machined surface near the probe connection point. Figure 33 shows the location of the Reference Plane, denoted as R, for the two basic methods of connecting the transmitter to the tank, either threaded or flanged. Refer to the Radar Level Measurement section in the SLG 700 Transmitter User s manual #34-SL Figure 33- Reference plane R for flanged and threaded connections Page 136 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

153 Probe Probe Type: Only adjust this if you are changing the type of probe. Adjustments to the calibration offsets and many other tuning parameters may be necessary if the probe is changed. The available options are: Custom, Rod, Wire, Multi-Twist Wire and Coax. (Single-twist wire requires a selection of wire and Multi-twist wire requires a selection of multi-twist wire). Probe Material: Probe Material provides user an option to select the material with which probe is made of. Probe Diameter: Probe Diameter can be selected from the options available via drop down. Probe End Type: This parameter specifies how the probe is terminated. For Rod and Coaxial probes the only available option is None. For Wire probes the available options are Clamp, Weight and Loop. Probe Length: This is a factory setting based on the purchase order. Adjustments to this parameter is only required if the probe has been replaced or cut shorter. This parameter should always be measured from the reference plane to the effective end of the probe. For a Coaxial probe and a Rod probe without a centering disk, the effective end of the probe is the physical end of the probe. For a Rod probe with a centering disk attached, the effective end of the probe is the top surface of the centering disk. For a Wire probe with an end weight, the effective end of the probe is the top of the end weight. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 137

154 Centering Disk Type: This parameter identifies if a centering disk is present and if so the material that it is made off. If the centering disk was ordered with the transmitter this will be correctly set when the transmitter leaves the factory. Centering Disk Diameter: If the Centering Disk Type is not set to None, an additional parameter is required to specify the diameter of the disk. If the centering disk was ordered with the transmitter this will be correctly set when the transmitter leaves the factory. Probe Propagation Factor: Propagation factor will be factory set for the probe type ordered. If the probe is changed or a customer supplied probe is used, this value may need to be adjusted to scale the apparent distance to product appropriately. Consult Honeywell for details. Blocking Distance Low: Blocking distances are areas of the sensor reading range where it is not desirable to search for reflections, possibly due to poor signal to noise ratios. The Blocking Distance Low is the distance value measured starting from the Probe End. For a wire probe with an end weight, the end of the probe is considered to be the top of the end weight. The transmitter will not attempt to make a reading in this area. A minimum value is predefined by the factory to be the same as the Low Transition Distance. The minimum value for Blocking Distance Low, as well as transition distances, is shown in Table 23. Blocking Distance High: Blocking distances are areas of the sensor reading range where it is not desirable to search for reflections, possibly due to poor signal to noise ratios. The Blocking Distance High is the distance value measured starting from the Sensor Reference Plane. The transmitter will not attempt to make a reading in this area. The factory-set blocking distance is set to the transition distance high. It is recommended that the blocking distance is set to the largest value the measurement can tolerate and that the loop current is adjusted to reach maximum before level reaches the blocking distance. The minimum value for Blocking Distance High, as well as the transition distances is shown in the table below. Transition zones Transition zones are areas close to the process connector and close to the end of probe where measurements have reduced accuracy, see table below. For more information on transitions zones for the various sensor configuration (i.e. coax, rope, rod, HTHP, etc.), refer to SLG 700 SmartLine Level Transmitter User s manual, #34-SL Table 23 - Minimum blocking distances and transition zones for the various probe types Probe Type Media in Tank Minimum Blocking Distance High [cm] Upper Transition Zone, Tup [cm] Minimum Blocking Distance Low [cm] Rod/Wire Water (DC=80) Rod/Wire Oil (DC=2) Coax Water (DC=80) Coax Oil (DC=2) Lower Transition Zone, Tlow [cm] Page 138 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

155 Maximum Filling Rate: This parameter indicates the maximum rate at which the tank is expected to be filled or emptied. This allows the transmitter to collect data over the correct area of the probe so that the surface and/or interface positions can be tracked effectively and aids in the rejection of false reflections that might look similar to the correct reflections. The valid range is between m/s ( ft/s). The sensor uses this value to discard erroneous echoes. It is recommended that a value somewhat larger than that Mounting The main configuration parameters in this group deal with describing how the transmitter is physically mounted to the tank. The lower portion of the display provides access to a number of advanced options and actions that may be necessary to fine tune the transmitter performance in cases where the characteristics of the mounting cause disturbances that cannot be modeled in the factory. Transmitter Model: Read-only parameter reflecting the model of transmitter ordered, either SLG720 or SLG726. Process Connector Type: Read-only parameter indicating whether the transmitter was order with a flange for mounting to the tank or with a simple threaded connection. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 139

156 Sensor Connection Type: Read-only parameter indicating how the Sensor Housing and Process Connector are connected together. In most cases these two components are connected end-to-end in the Direct mount mode. For harsh environments where the temperature at the Process Connector is too high for the electronics inside the Sensor Housing, a 3m Remote Mount cable is available to physically separate the electronics from the process connector. When the Remote mount mode is used, the transmitter will acquire a longer echo curve to cover the additional length of the Remote Mount cable, and will use the process connector reflection as the datum point to find the transmitter s Reference Plane location. Mounting Location: This parameter allows users to select the option that best describes how the GWR transmitter is located on the tank. The available selections are: Tank (Mounted to a flat surface in the tank ceiling or wall) Bracket (Mounted to a bracket over an open roof tank) Nozzle (See transmitter specifications for limits on nozzle dimensions) Bypass (See transmitter specifications for limits on bypass dimensions) Stillwell (Stillwell must extend beyond the length of the probe) Unknown (To be used only if none of the above are applicable) Selecting the Bypass or Stillwell options require an additional parameter entry to specify the inside diameter of the bypass or stillwell. Selecting the Nozzle option requires two additional parameter entries to specify both the inside diameter and length of the nozzle. Mounting Angle: The physical angle at which the probe is mounted relative to vertical (0 degrees means the probe is perfectly vertical). Mounting Height: It is the length of the nozzle/bypass pipe from the transmitter reference plane to the bottom of the Nozzle. Mounting Diameter: It is the inner diameter of the Nozzle/Bypass. Page 140 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

157 Field Background: The physical components used to mount the transmitter to the tank will always cause some reflection of the radar pulse as the pulse leaves the confines of the process connector and starts to travel through the medium in the region near the reference plane. Depending on the configuration, these reflections may appear very similar to the reflections from the products in the tank and therefore should be ignored. In addition obstacles present close to the wave guide can cause reflections that mimic levels. The SLG 700 transmitter utilizes a means of subtracting out these static background reflections before processing the data for reflections from the product(s). All transmitters have pre-configured backgrounds for standard probe configurations which can be selected with the Factory option. In all but the simplest applications, these should be replaced if possible in-situ with one of the other two options using the capture mechanism described below. The Field option is meant to reduce the effect of the process connector reflection created when the radar pulse traverses between two regions of different impedances. The preset length varies from 1.32m (standard temperature and pressure gauge) to 2.38m (high pressure high temperature model) from the measurement Reference Plane. Ensure that the level in the tank is below these values when acquiring the background. The field background is stored in permanent memory. The Obstacle option is similar to the field background but is intended to both suppress process connector reflections as well as any false echoes generated by obstacles in the tank (ladders, pipes, valves) in the vicinity of the probe. There is no limit on the length that can be specified by the user. As with the field background, the level in the tank needs to be about 30cm below the end of the requested echo. One difference between the obstacle suppression echo and the field background echo is that the sensor algorithms analyze this echo and store only those sections of the profile that are found to contain false echoes. For example, if a ladder exists 2m down a tank and a pipe inlet 19m down the tank, the user should obtain an obstacle echo up to approximately 20m. The sensor will automatically detect the two objects and permanently store the relevant data, omitting quiet regions in between. The active Background Type selection is independent of the capture Background Type described below. New backgrounds are applied immediately once captured. However, it is not possible to stay in obstacle mode after collecting a field type background because it is likely that the obstacle background is significantly longer than the field background just collected. Normal operation is to choose a background mode, apply, then collect a background in that mode. Backgrounds can be verified on the Echo Curve display on the Monitor menu. Use Field Background: This Parameter provides an option to do different operations like starting a Field background capture and invoking verification of status of Field background capture. Field Background Capture Status: Field background status provides status of Success or Failure. Field Background Capture Progress: This will provide in progress status in terms of percentage completion. Field Background additional Status: This will provide detailed status of failure due to which field background capture failed Rev.5 FOUNDATION Fieldbus Option User's Manual Page 141

158 Full Tank Detection: Full tank detection enables the detection of a level within the upper blocking distance at startup and it ensures reliable measurement when the block distance high (BDH) is reduced below the transition upper distance. This feature enables the transmitter to perform additional analysis on the data in the region near the reference plane where the product reflections become mixed with reflections from the physical mounting components such as a flange or nozzle. This additional analysis allows the transmitter to detect the presence of product in this region even if the shape of the product reflections deviate significantly from the expected shape. This option should only be enabled if a recently captured Field or Obstacle background is in use (see below) and the Dielectric Constant of the Upper Product is above 12. It should not be enabled for products with low Dielectric Constants or when the Factory background type is being used. In a demanding application where measurements close to the process connector are required but large temperature fluctuations are expected it is also recommended to enable Dynamic Background updates as discussed below. Dynamic Background update: The feature provides enhanced immunity against measurement conditions by dynamically adjusting the active Field or Obstacle background profile. (This feature is not available for the Factory Background Type.) With Dynamic Background enabled, the sensor periodically schedules automatic updates to the background echo profile. Echoes are only updated if the level is outside of the transition zones (see section Transition zones) and the signal is of good quality. Data is collected up to approximately 30 cm from the level at the time, if this distance is within the requested background echo length. The most recently updated background is also stored in permanent memory and is applied after a sensor reset if dynamic background is enabled. At all times the sensor maintains a copy of the original user acquired (static) background echo and will revert to this if the dynamic background feature is once again disabled. Re-enabling dynamic background at that point starts the process anew. It is recommended that this feature is turned on in all installations where probe build-up or large ambient temperature swings over 30 C are expected. Background Capture: This group of controls provide the mechanism for obtaining new background echoes for the Field and Obstacle background types described above. These controls are only visible when no other parameters are being edited as the background echoes are inherently dependent on the current mounting configuration. All edits must be applied or discarded before a background capture may be started. Background Length Type: This control allows the user to select the type of background profile that should be collected as either Field or Obstacle. (The Factory background profile is completely static and cannot be captured or dynamically updated.) This type parameter does not have to be the same as the active Background Type parameter described above which is located outside this group of controls. In fact, a Field or Obstacle background profile must be collected first before it can be activated. Background Length: This control allows the user to enter the desired length of background profile to collect as measured from the Reference Plane. For the Field background type the control will be automatically populated with a preset length based on the current mounting configuration. The length cannot be increased beyond this preset value and should only be lowered in extreme cases when it is not possible to bring the surface of the product below this length. For the Obstacle background type the control will also be automatically populated with this preset length but the value may be increased as required to cover all obstacles, up to the measureable length of the probe. Page 142 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

159 Echo Lost timeout: This parameter allows for time adjustment when the transmitter waits in response to echo loss. Field Background Capture This method collects a new background echo for the selected type and length. This process should only be performed when there is no product in the region over which the background will be captured. The length of this region varies with the transmitter model, mounting location and probe type. A pop-up message similar to the one shown below will be displayed indicating the required length. If the OK option is selected, another message will pop-up asking for user input whether can be moved to OSS, since Field background capture can be performed only in OOS mode as shown below, once block is moved to OOS, user input will be required to proceed with Field background capture. Ok clicking Ok, method will ask for following details like Capture background type, Background Length Type and Background Length Rev.5 FOUNDATION Fieldbus Option User's Manual Page 143

160 On entering all the requested details the transmitter will start the capture sequence and in progress message will be displayed to show the progress. The function of the button will also change, as shown below, allowing the user to Abort the currently active method if required. Upon completion of the process, a pop-up message such as the one shown below will be displayed indicating whether the capture was successful or not. In the case of a successful capture there may also be some additional information or warnings provided. The new background is immediately applied by the transmitter, but sees the comments above for the active Background Type parameter. Method will ask whether to put mode back to previous mode, ok clicking ok block will be put back to previous mode and method will be completed with the below message. Page 144 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

161 Attenuation This menu deal with Attenuation configuration of Vapor, Upper product, Lower product. Lower Prod. Attenuation Upper Prod. Attenuation Vapor Attenuation This sets the linear attenuation coefficient (Radar Pulse energy dissipation) of Lower Product. (For Two Liquids only). This sets the linear attenuation coefficient (Radar Pulse energy dissipation) of Upper Product (For Two Liquids, otherwise this is just Product/Surface attenuation). This sets the linear attenuation coefficient (Radar Pulse energy dissipation) of Vapor. Linear Attenuation Model The gain (amplitude) of the radar reflection is exponentially decayed based on the linear attenuation coefficient. This accounts for radar pulse energy dissipation to the vapor and media surrounding the probe and is a function of the distance travelled. This is modeled as:g surface (0) = g surface (0) e αx. Where: x = the distance from the reference plane α = the linear attenuation coefficient The linear attenuation of the gain is plotted in red in the upper graph in Figure. There is one linear attenuation coefficient for each possible medium in the tank: Rev.5 FOUNDATION Fieldbus Option User's Manual Page 145

162 Vapor Upper product Lower product Figure 34 Attenuation model These are available on the Attenuation Model panel shown in Figure 34. For each possible medium in the tank there is also a reference point from which the linear attenuation should be applied. For the Surface and End of Probe reflections this reference point is the transmitter s Reference Plane. For the Interface reflection this reference point is the location of the Surface reflection in non-flooded applications and the location of the transmitter s Reference Plane for flooded applications. The Reflection Model panel has entry fields where the locations of these reference points can be entered. In many cases, these locations will have been determined by the transmitter and these entry fields will be pre-populated with the correct values from the echo curve data. Page 146 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

163 Process Variables menu Process Variables menu contains the dial gauges of all Device variables of transmitters. In Section 6.6.2, Process variable Button is shown, clicking that button we get to this Menu. This page will show values of different process parameters in dial form. Trends menu Trends menu contains the Trends of all Device variables of transmitters. In Section 6.6.2, Trends Button is shown, clicking that button we get to this Menu. This page will show values of different process parameters in Trend form. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 147

164 Diagnostics Diagnostics menu consists of block errors alarms and Static Revision, the detail description of block error information is available in Table 3. Page 148 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

165 6.7 Diagnostics Transducer block configuration This menu provides the facility to select the mode of the target/device, to configure any parameter keep the target mode as OOS, if it is in AUTO mode then the parameters can t be configured. Block Modes General: This menu consists of block errors, the detail description of diagnostics information is available in Table 3. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 149

166 Sensor Diagnostics: This menu consists of sensor diagnostics and sensor signal strength and sensor signal quality parameters, the description of diagnostics information is available in Table 36: Diagnostics. Electronic Temperature Diagnostics: This menu consists of Max. Electronic Temperature, Min. Electronic Temperature, Electronics Temperature Unit, ET Over Range CTR, ET Over Range Date, ET Under Range CTR and ET Under Range Date parameters, the description of diagnostics information is available in Table 36: Diagnostics. Page 150 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

167 Sensor Detailed Status: This menu consists of sensor reported critical status 1, critical status 2, non-critical status 1, non-critical status, the description of diagnostics information is available in Table 36: Diagnostics. Device Model Details: This menu consists of comm. model details such as model key, model part 1, model part 2 and model number reconcile selection, the description of the device model detailed information is available in Table 36: Diagnostics. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 151

168 Comm General Diagnostics: This menu consists of Time in service, Service life, Stress monitor parameters, the description of diagnostics information is available in Table 36: Diagnostics. Power Track: This menu consists of Power cycle, last pawer up cycle time parameters, the description of diagnostics information is available in section Table 36: Diagnostics. Page 152 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

169 Operating Voltage Track: This menu consists of supply voltage, minimum voltage, reset minimum voltage, status of current voltage, last minimum volage time parameters, the description of diagnostics information is available in Table 36: Diagnostics. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 153

170 6.8 LCD Transducer block configuration Device: This menu provides the facility to select the mode of the target/device, to configure any parameter keep the target mode as OOS, if it is in AUTO mode then the parameters can t be configured Display Settings: This menu consists Rotation time, Language, Language pack, Display connected, Contast level, Display software version, Message, Rotate enable parameters, the description of parameters under display settings menu is available in section Page 154 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

171 Screen 1 (screen parameters) This menu consists of Block type-1, Parameter index-1, Unit type-1, Custom unit-1, Custom tag-1, Screen format-1, Decimals-1, Low limit-1, High limit-1, Trend duration-1 parameters, the description of parameters is available in section Similarly screen 2 to 8 has the same parameters as like screen 1. General: This menu consists of block errors, the detail description of diagnostics information is available in Table 3. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 155

172 6.9 Auxiliary Transducer block configuration The Auxiliary Transducer block(rlauxtb) menu items deal with fine tuning of the algorithms used inside the transmitter and generally do not need to be adjusted. However, in demanding applications or if the process or mounting configuration changed from what was ordered, some of the default options may need to be adjusted. Aux TB contains three main menus Device, Configuration & diagnostics Device menu: This menu contains three tabs namely Block modes parameters, it provides the facility to select the mode of the target/device, to configure any parameter keep the target mode as OOS, if it is in AUTO mode then the parameters can t be configured. Configuration is also available in Permitted mode & normal mode. Page 156 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

173 Configuration: This menu contains sub menus like Linearization, Correlation Algorithm, Volume & Echo curve as shown in figure. Linearization This option allows users to adjust the level measurement to agree with a customer measurement. It is available only through the use of a PC-based DTM / DD. Configure the linearization table to make the transmitter output agree with an independent level measurement. Note: The Level Linearization feature does not affect the values reported for the Distance to Product and Distance to Interface device variables. If Level Linearization checkbox is enabled, associated level is no longer described solely by the basic geometry and it is possible that the Product Level will not be equal to (Sensor Height Level Offset Distance to Product). Likewise for the Interface if is being calculated. Table should be entered either in ascending or descending order only. Enable Linearization: If enabled, linearization will convert the level as measured by the sensor to a corrected level value as defined by the user in the linearization table on this page (max 32 points). This may be used to correct for any non-linearity s that may occur. For example, a tank for which the roof height changes during filling. Wet Linearization: When the measured level for the tank reaches a level where the corresponding corrected level is known, select a row in the linearization table, enter the corrected level in the textbox below, and proceed further. This will immediately set the values into the selected row in the strapping table (i.e. immediately set in the transmitter). Rev.5 FOUNDATION Fieldbus Option User's Manual Page 157

174 Correlation Algorithm The method by which the distance to product surface and distance to interface is found is based on correlation between the measured echo curve and reflection models. The algorithm slides the models across the echo curve and at each step calculate the difference between the model and the echo curve, referred to as the Objective Function. Typically the smallest value of the Objective Function corresponds to the level selected by the sensor algorithms but the values must be below a user defined threshold. In case of multiple local minima, there is additional logic to select the best candidate. The final best candidate is used to calculate the distance to the product surface and/or the distance to interface. Page 158 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

175 Reflection Models: The radar impulse reflection model is an asymmetric damped cosine function that takes four parameters as listed in the leftmost Reflection Models in above screen shot. The model and its gain, width and attenuation parameters are illustrated in Figure 35. Go to section for details on how to tune the parameters using HART DTM Figure 35 - Radar Impulse Reflection Model Gain: This parameter determines the magnitude of the central peak of the damped cosine function. Width: This parameter determines the width of the central lobe of the damped cosine function. It approximately equals the width between the zero crossings of the function. Attenuation: This parameter determines how fast the cosine wave is reduced to zero magnitude, and therefore determines the height and width of the side lobes to either side of the central lobe. Increased attenuation results in smaller side lobes. Note that the asymmetric property means that the side lobes will each have a slightly different shape. This attenuation parameter should not be confused with the medium attenuation that determines how the RADAR amplitude diminishes as it propagates down the probe. There are a total of 5 reflection models maintained by the transmitter to represent the types of reflections that might be visible. Reference Process Connector Surface Interface End Of Probe The Reference reflection is a reflection caused by an impedance change where the transmission line connects to the sensor board that generates the radar pulses. This reflection is always present and its characteristic shape is not altered by any environmental or process conditions. In cases where the sensor housing is directly connected to the process connector, the Reference reflection serves as an internal datum point for locating the position of the transmitter s Reference Plane in the echo curve. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 159

176 The Process Connector model is only used in cases where the sensor housing is separated from the process connector by the optional 3m Remote Mount Cable. Since the remote cable may be subject to a high temperature gradient, a reflection within the process connector is used as the datum point for locating the transmitter s Reference Plane, eliminating temperature dependences of the level measurement. This reflection is located at the start of the process connector. The Surface model is used to describe the characteristics of the reflection caused as the radar pulse encounters the boundary between a vapor and a liquid product. The Interface model is used to describe the reflection caused as the radar pulse encounters the boundary between two liquid products. Refer to Reflection Models on page 159 for a description of when each of these types of reflections may be present. The End of Probe model is used to describe the characteristics of the reflection caused as the radar pulse encounters the physical end of the probe or a centering disk attached to the probe. The shape of these reflections varies depending on the probe type and end treatment as well as the transmitter model and other mounting considerations. While the physical end of the probe is always present, depending on the transmission characteristics and amount of product(s) above the end of the probe, this reflection may not be noticeable in an echo curve. Offsets There are three offsets used by the algorithm in calculating the distance to surface measurement. The Process Connector Offset (m) is only used for cases where the optional Remote Mount Cable is installed, as it indicates the observed distance between the Reference and Process Connector reflections. It is a calculated offset and is therefore a read-only parameter. If the Remote Mount cable is not installed, this offset will default to zero. The Reference Plane Offset (m) is a read-only parameter that is determined in the factory for each transmitter. It corresponds to the distance between the physical reference plane and the internal datum point, which is the location of either the Reference reflection or the Process Connector reflection, depending on whether or not the optional remote mount cable has been ordered. The Calibration Offset (m) is a user-entered offset that may be used to adjust for minor inaccuracies in the distance measurements caused by differences between the factory and field conditions. It has a range of ±1.0m and is always treated as a vertical measurement, even if the probe is mounted on an angle. Amplitude Tracking: This feature enhances the sensor to track levels under dynamic conditions or when the radar pulse attenuations in the media are not well known. Once the sensor has locked onto a correct level, it will track the amplitude rather than use the initial (user specified) model amplitude. These values are periodically permanently stored and are hence recovered after a power down. Stored values are cleared and re-initialized to the user provided amplitudes by turning off Amplitude Tracking (and applying this change) and then turning it back on it. Amplitude tracking is not a replacement for setting correct correlation models and will not track pulses whose amplitudes differ more than about 40% from the user specified pulse model amplitudes. Under normal circumstances, the only parameter that may require adjustment in the field is the Gain parameter under the Model tab. Page 160 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

177 Volume Configure volume calculation method. For details information of Tank configuration refers Table 9. The Level Transmitter measures only distance and related quantities (level, percent of range, etc.). The calculation of volume by the transmitter is based on measured level and additional tank geometry measurements. Wet Volume Calibration When the measured level for the tank reaches a level where the corresponding volume is known, select a row in the method, enter the corresponding volume in the textbox below, and proceed further. This will immediately set the values into the selected row in the strapping table (I.e. immediately set in the transmitter). Rev.5 FOUNDATION Fieldbus Option User's Manual Page 161

178 Echo Curve The Echo Curve display allows users to capture echo curves for commissioning or troubleshooting purposes. Start Distance End Distance Units Resolution: to select the resolution to select the resolution of the data collected (Impacts upload time) Clear Echo curve. Save To File: Allows users to save to disk and later perform analyses on the data or send for offline analysis by experts. For detail information on how to take Echo curve using different types refer section and for trouble shooting the echo curve please refer section Page 162 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

179 6.10 Diagnostics Diagnostics menu consists of block errors alarms and Static Revision, the detail description of block error information is available in Table 3. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 163

180 6.11 Resource block configuration Device: This menu provides the facility to select the mode of the target/device, to configure any parameter keep the target mode as OOS, if it is in AUTO mode then the parameters can t be configured Field Diagnostics: This menu consists of field diagnostics parameters, the description of parameters under display settings menu is available in section Alarms tab Page 164 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

181 Mapped tab Mask tab Rev.5 FOUNDATION Fieldbus Option User's Manual Page 165

182 Priority tab Simulate tab Page 166 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

183 Active tab General tab Rev.5 FOUNDATION Fieldbus Option User's Manual Page 167

184 General tab Common Diagnostics This menu consists of block errors, the detail description of diagnostics information is available in Table 3. Page 168 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

185 6.12 Analog input block configuration The Analog Input (AI) block takes the transducer s input data, selected by channel number, and makes it available to other function blocks at its output. For details information of calculation & equation of Output from Level Transducer block refer section 3.5. Figure 36 - Analog Input Block Level TB contains three main menus Device, Process Variables & Diagnostics. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 169

186 Device menu: This menu contains three tabs namely Block modes, Configuration and Scaling Block Mode: This menu provides the facility to select the mode of the target/device, to configure any parameter to keep the target mode as OOS, if it is in AUTO mode then the parameters can t be configured. Configuration is also available in Permitted mode & normal mode. Configuration This menu contains required parameters for configuration of AI block to function. Page 170 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

187 The variables to be used by the block are defined through the available channels: Product Level Product Volume Distance To Product Electronic Temperature Product Level Rate Vapor Volume Interface Level Upper Product Volume Distance To Interface Lower Product Volume Interface Level Rate Upper Product Thickness Vapor Thickness For details information of using configuration tab refer Section Scaling Scaling menu contain three sub menu namely Channel (refer section ), Transducer scaling and Output scale units. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 171

188 Process variables This menu contains only one sub-menu Dynamic Variable which display the Output value with units and status of AI block, for details refer section 3.9 Diagnostics This menu contains two sub menus namely General and Alarms General General menu consists of block errors alarms and Static Revision, the detail description of block error information is available in Table 3. Page 172 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

189 Alarms The block supports standard block alarms (see section 3.3). Additionally it supports, standard HI_HI, HI, LO, and LO_LO alarms applied to OUT. For details on configuration of Process alarms refer section Rev.5 FOUNDATION Fieldbus Option User's Manual Page 173

190 7. SLG 700 FF Level Transmitter troubleshooting 7.1 Troubleshooting overview This section contains information to help you identify the faults in devices and the recommended actions to correct them. Troubleshooting is performed to determine the cause of the fault by analyzing the device indications (such as device not visible on network or not able to write values to parameters.) Device status and faults The transmitter constantly runs internal background diagnostics to monitor the functions and status of the device operations. When errors and/or faults are detected, they are reported in the status bits of certain block parameters, (for example, BLOCK_ERR). The other parameters can be seen by viewing the status descriptions and/or a value, which may help to identify a fault. Device status and operational faults are identified by viewing key parameter values or status and then interpreting their meaning using the following tables. ATTENTION Additional diagnostics are available through supervisory and control applications that monitor and control fieldbus networks. These diagnostics and messages are dependent upon the capabilities of the application and the control system that is used. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 174

191 7.2 Troubleshooting the transmitter Device not visible on the network If a device cannot be seen on the fieldbus network, the device may not be powered up or possibly the supervisory or control program is not able to find (or polling) the node address of that device. See the following table for possible causes and recommended actions. Symptoms Device not visible on the network Possible cause Things to check Recommended action No power to the device. Insufficient current to the device. More than two or less than two terminators are wired to fieldbus link. Insufficient signal to the device. Names of parameters are not visible. Measure the DC voltage at the device s SIGNAL terminals. Voltage must be within the limits. Measure the DC current / voltage ranges to the device. The DC current / voltage ranges must be within the limits. Check to see that only two terminators are present on a link. Measure the peak-to-peak signal amplitude. The output must be 0.75 to 1.0Vp-p. Measure the signal on the + and - SIGNAL terminals and at a frequency of 31.25k Hz. Missing or incorrect version of Device Description file on host computer. If no voltage or voltage is out of operating limits, determine the cause and correct it. If the current / voltage is insufficient, determine the cause and correct it. Correct, if necessary. If the signal amplitude is insufficient, determine the cause and correct it. Check the loaded Device Description. Load correct version of DD. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 175

192 Incorrect or non-compatible tools If non-compatible versions of fieldbus software tools are used, such as Standard Dictionary or Device Description (DD) files, or if you are using the incorrect revision level of device firmware, then device objects or some block objects may not be visible or identified by name. See the following table for the possible causes and recommended actions. Symptoms Device and/or block objects not identified (Unknown). Or Parameters are not visible or identified by name. Or Honeywell-defined parameters are not visible. Possible cause Things to check Recommended action Incorrect Standard Dictionary, Device Description (DD) or Symbols on host computer. Incorrect pathnames to descriptions on host computer. Incorrect version of device firmware Verify that the Standard Dictionary, the DD or symbols files are correct for the device. Check that the pathnames to locations of the Standard Dictionary, and DD files on the host computer are correct. Read the following Resource block parameters: DEV_REV (contains the revision level of the resource block). DD_REV (contains the revision level of the resource block). Install the compatible version of Standard Dictionary and DD for the device on the host computer. Make sure that the pathnames of the Standard Dictionary and DD are in the correct location for the fieldbus software application. Perform a code download of the correct device firmware. See section 5.2. Page 176 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

193 7.3 Troubleshooting blocks Non-functioning blocks Device block objects may not be running (executing their function block schedules) or the blocks may be in Out of Service (OOS) mode due to block configuration error. For example, if the AI function block is in OOS mode, the block does not provide updated output values, although the AI block may be running. While troubleshooting a non-functioning block objects, it is recommended to start with the resource block. For example, if the resource block is in OOS mode, all other blocks in the device are also in the OOS mode. Troubleshooting block configuration errors The block configuration errors prevent a device block from leaving the OOS mode. The BLOCK_ERR parameter (bit 1) shows whether a block configuration error is present. The following section explains the troubleshooting for all the function blocks. Troubleshooting the Resource block Table 24: Resource block Problem cause Things to check Recommended action Resource block mode is OOS mode and is not going to AUTO mode. Resource block is not running. Read MODE_BLOCK.PERMITTED Read MODE_BLOCK. ACTUAL of Resource block. Check BLOCK_ERR for errors. Add AUTO mode to MODE_BLOCK.PERMITTED. If necessary, Set MODE_BLOCK.TARGET to AUTO. NOTE: If the mode is set to OOS for maintenance, then do not change the mode to AUTO. See Table 3 for details on BLOCK_ERR. Incorrect revision level of the device firmware. Read SOFTWARE_REV See section 7.2 Block alarms are not reported. Field diagnostics alarms are not reporting. Read FEATURE_SEL Read LIM_NOTIFY Check Field Diagnostics MASK. Check Field Diagnostics Priority. Check Field Diagnostics MAP. Reports are not selected in FEATURE_SEL. If features do not include Reports then the host must poll for alarms. Set LIM_NOTIFY to a value higher than zero, but not higher than MAX_NOTIFY. If the alarms are MASKED, then the alarms do not report. Unmask the alarms. Table 4. If the priority is zero alarms do not report. For information on how set the priority, see If alarms are not mapped, then Map alarms to any of the Field Diagnostics alarm parameters. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 177

194 Problem cause Things to check Recommended action Sensor Board Fault Communication Board Fault Sensor Communication Fault Characterization data or Calibration data corrupt Sensor and Communication Board Database CRC Mismatch Sensor and Communication Board Database version Mismatch Sensor Board Over Temperature Communication Board Over Temperature PV out of Range Check Sensor Detailed Diagnostics to know the reason of Sensor Board Fault. If any of the critical diagnostics bit except probe missing is set it will set Field Diagnostic bit of Sensor Fault This fault is set if operating voltage is not with in limit (9 to 32 V) or RAM or FLASH failure. There is no response from sensor Characterization of Sensor or Calibration data of sensor is corrupted. There may be impact on the accuracy of measurement. This fault is set if configuration parameters used by sensor and stored in the communication board EEPROM differs. This fault is set if configuration parameters database version used by sensor differs from communication board EEPROM database. Sensor housing temperature is too high. Accuracy and life span may decrease if it remains high. Communication Board temperature is too high. Life span may decrease if it remains high. Sensor Overload/Sensor Fault Redundant Characterization Calculation Error Calculated level is above Upper Transducer Limit (UTL). Restart of Device is required. If error persists change the Sensor housing of the Device or Device. Restart of Device is required if error persists change the communication Module of the device or Device. Restart of Device is required. If this does not fix the problem, replace the sensor module. Restart of Device is required. If this does not fix the problem, re-characterization or re-calibration of device is required to improve the accuracy. Restart of Device required. If error persists try replacing the Electronics module. If this does not fix the problem, replace the sensor module. Upgrade firmware, either communication module or sensor module is required. Verify the environment temperature is within specification. Take steps to insulate Sensor housing from temperature source Verify the environment temperature is within specification. Take steps to insulate communication module from temperature source Check level is within range and outside blocking distance range, replace transmitter with one that has a wider range. Sensor housing may have been damaged. Check the transmitter is outside the entered range for accuracy and linearity. Replace Sensor housing and recalibrate if needed. Page 178 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

195 Problem cause Things to check Recommended action Surface in BDH Surface in BDL Interface in BDH Interface in BDL This indicates that either the surface or interface reflection has been tracked into the upper zone near the Reference Plane where measurements are not accurate. This indicates that either the surface or interface reflection has been tracked into the lower zone near the End of Probe where measurements are not accurate. This indicates that interface reflection has been tracked into the upper zone near the Reference Plane where measurements are not accurate. This indicates that interface reflection has been tracked into the lower zone near the End of Probe where measurements are not accurate. This is a condition that can occur during normal operation and does not generally require corrective action. If this condition is triggered when it is not expected, verify that the Blocking Distance High parameter is set correctly for the current conditions. If distance to product is in Higher zone then status associated with device variables derived from distance to product will be shown as uncertain in local display and on host the status would be poor accuracy. This is a condition that can occur during normal operation and does not generally require corrective action. If this condition is triggered when it is not expected, verify that the Blocking Distance Low parameter is set correctly for the current conditions. If distance to product is in Lower zone then status associated with device variables derived from distance to product will be shown as uncertain in local display and on host the status would be poor accuracy. This is a condition that can occur during normal operation and does not generally require corrective action. If this condition is triggered when it is not expected, verify that the Blocking Distance High parameter is set correctly for the current conditions. If distance to interface is in Higher zone then status associated with device variables derived from distance to interface will be shown as uncertain in local display and on host the status would be poor accuracy. This is a condition that can occur during normal operation and does not generally require corrective action. If this condition is triggered when it is not expected, verify that the Blocking Distance Low parameter is set correctly for the current conditions. If distance to interface is in Lower zone then status associated with device variables derived from distance to interface will be shown as uncertain in local display and on host the status would be poor accuracy. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 179

196 Troubleshooting the Level Transducer block Table 25: Level Transducer block Problem cause Things to check Recommended action Transducer block mode is in OOS and does not change to AUTO mode. Transducer block does not produce valid Distance to Level, Product Level Read MODE_BLOCK.PERMITTED Read MODE_BLOCK. ACTUAL of Resource block. Check the product Level Range. Check Field Diagnostics Status bit of Characterization data and Calibration data Corrupt and Sensor Characterization Status and Sensor Calibration Status bits of Sensor Details Status parameter of Diagnostic Block Verify parameter: Distance To Level and Product Level Value status are not GOOD Check Sensor Configuration Add AUTO mode to MODE_BLOCK.PERMITTED. If necessary, Set MODE_BLOCK.TARGET to AUTO. NOTE: If the mode is set to OOS for maintenance, then do not change the mode to AUTO. Ensure that Product Level Range has valid ranges and units assigned. Change the Sensor housing. Verify the Surface configuration of the Correlation Algorithm parameters and Sensor parameters configuration Ensure that Auxiliary Transducer block is in AUTO mode. Verify that correct Dielectric constant, Sensor height, Maximum Product Height, Probe Type, Probe Length, Level Offset, Blocking Distance High and Low values are assigned. Verify that correct Correlation Algorithm Surface values are assigned by reading Echo curve again. Page 180 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

197 Problem cause Things to check Recommended action Transducer block does not produce valid Distance to Interface and Interface Level value. Check the Product Level Range Check Field Diagnostics Status bit of Characterization data and Calibration data Corrupt and Sensor Characterization Status and Sensor Calibration Status bits of Sensor Details Status parameter of Diagnostic Block Verify parameter: Distance To Interface and Interface Level Value Status are not GOOD Check Sensor Configuration Ensure that Product Level Range has valid ranges and units assigned. Change the sensor housing Verify that correct Measured Product (Two Liquid(Flooded) or Two Liquid (Non Flooded)) and the Surface and Interface configuration of Correlation Algorithm parameters and Sensor parameters configuration Ensure that Auxiliary Transducer block is in AUTO mode. Verify that correct Measured Type, Dielctric constant, Sensor height, Maximum Product Height, Probe Type, Probe Length and Blocking Distance High and Low values are assigned. Verify that correct Correlation Algorithm Surface and Interface values are assigned by reading Echo curve again. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 181

198 Problem cause Things to check Recommended action Transducer block does not produce valid Product Volume Transducer Block does not produce valid Vapor Thickness and Vapor volume Transducer block does not produce valid Upper Product Thickness, Upper Product Volume and Lower Product Volume Transducer block shows incorrect Electronic Housing temperature value. Block alarms are not reported. Check the Product Volume Range Check Distance to Product, Product Level and Distance to Interface, Interface Level (if Two Liquid selected) values are valid Verify parameter: Product Volume Value Status is not GOOD Check Sensor Configuration Check Distance to Product, Product Level value. Check Distance to Product, Product Level value. Check Distance to Interface and Interface Level value and Measured Product is selected as Two Liquid (Non Flooded) Check the Electronic Housing temperature units. Read FEATURE_SEL. Read LIM_NOTIFY. Ensure that Product Volume Range has valid ranges and units assigned. Verify that sensor and correlation algorithm configuration. Verify that correct Volume Calculation type is selected and correct tank configuration is assigned in the Auxiliary Transducer Block. Ensure Auxiliary Transducer Block is in AUTO mode. Verify that correct Measured Type, Dielectric constant, Sensor height, Maximum Product Height, Probe Type, Probe Length and Blocking Distance High and Low values are assigned. Verify that correct Correlation Algorithm Surface and Interface values are assigned by reading Echo curve again. Verify sensor configuration and correlation algorithm configuration Verify sensor configuration and correlation algorithm configuration Ensure that proper unit is assigned to Electronic Housing temperature. Reports are not selected in FEATURE_SEL. If features do not include Reports then the host must poll for alarms. Set LIM_NOTIFY to a value higher than zero, but not higher than MAX_NOTIFY. Page 182 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

199 Troubleshooting the Diagnostics Transducer block Table 26: Auxiliary Transducer block Problem cause Things to check Recommended action Diagnostic Transducer block mode is in OOS and does not change to AUTO mode. Read MODE_BLOCK.PERMITTED Read MODE_BLOCK. ACTUAL of Resource block. Add AUTO mode to MODE_BLOCK.PERMITTED. If necessary, Set MODE_BLOCK.TARGET to AUTO. NOTE: If the mode is set to OOS for maintenance then do not change the mode to AUTO. Troubleshooting the Diagnostics Transducer block Table 27: Diagnostics Transducer block Problem cause Things to check Recommended action Diagnostic Transducer block mode is in OOS and does not change to AUTO mode. Sensor Diagnostics, Sensor voltage diagnostics, Electronic temperature diagnostics values are not updating. Block alarms are not reported. Read MODE_BLOCK.PERMITTED Read MODE_BLOCK. ACTUAL of Resource block. Read UPLOAD_TRACK_DATA Read FEATURE_SEL Read LIM_NOTIFY Add AUTO mode to MODE_BLOCK.PERMITTED. If necessary, Set MODE_BLOCK.TARGET to AUTO. NOTE: If the mode is set to OOS for maintenance then do not change the mode to AUTO. Select value other than NONE, and then wait for 10 seconds. If no values are updated (for example, if Max and Min still shows 999) in Sensor Diagnostics and Sensor voltage diagnostics, Contact Honeywell TAC. Reports are not selected in FEATURE_SEL. If features do not include reports then the host must poll for alarms. Set LIM_NOTIFY to a value higher than zero, but not higher than MAX_NOTIFY. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 183

200 Troubleshooting the LCD Transducer block Table 28: LCD Transducer block Problem Cause Things to check Recommended Action LCD Transducer block mode is in OOS and does not change to AUTO mode. Writing to display parameters fails. Writing to some of display parameter in SCREEN_1, SCREEN_2, SCREEN_3 SCREEN_4 SCREEN_5, SCREEN_6, SCREEN_7, or SCREEN_8 fails. Local display shows Attention as title with some text. Block alarms are not reported. Read MODE_BLOCK.PERMITTED Read MODE_BLOCK. ACTUAL of Resource block. Check for local display. Check DISPLAY_TYPE. Check the DISPLAY_MESSAGE parameters. Read FEATURE_SEL. Read LIM_NOTIFY Add AUTO mode to MODE_BLOCK.PERMITTED. If necessary, Set MODE_BLOCK.TARGET to AUTO. NOTE If the mode is set to OOS for maintenance, then do not change the mode to AUTO. An Advanced Display is required for LCD_TB to work. If display is available, remove and reconnect the local display, and check if display powers up. If display is not powering up contact Honeywell TAC. These parameters are supported only by the Advanced Display. Transmitter messaging is activated; to clear the message executed the Clear Message method. For more information see section 3.8 Reports are not selected in FEATURE_SEL. If features do not include Reports then the host must poll for alarms. Set LIM_NOTIFY to a value higher than zero, but not higher than MAX_NOTIFY. Page 184 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

201 Troubleshooting the Analog Input (AI) block Table 29: Analog Input block Problem cause Things to check Recommended action Analog Input block mode is in OOS and does not change to AUTO mode. Analog Input block mode is in OOS mode with Block Configuration Error. Value of output seems wrong. Process and block alarms do not work. Read MODE_BLOCK.PERMIT TED Read MODE_BLOCK. ACTUAL of Resource block. Read WRITE_LOCK parameter in resource block. Check if device is in Write Protect mode. If WRITE_LOCK = Locked (2) Schedule Read CHANNEL parameter and range. Read L_TYPE parameter. Check if L_TYPE= Direct Read Linearization Type. Read Scaling. Read FEATURE_SEL. Read LIM_NOTIFY Read Alarm Summary Disable. Add AUTO mode to MODE_BLOCK.PERMITTED. If necessary, Set MODE_BLOCK.TARGET to AUTO. NOTE: If the mode is set to OOS for maintenance, then do not change the mode to AUTO. Change Write Protect jumper to W position. (See section 7.7) Reset the device. (Cycle power to transmitter or write Processor to RESTART parameter in Resource block.) Block is not scheduled and therefore cannot execute to go to Target Mode. Schedule the block to execute. CHANNEL must be set to a valid value and cannot be left at the initial value of zero. XD_SCALE.UNITS_INDX must be compatible with the units in the transducer block for the channel. L_TYPE must be set to Direct, Indirect, or Indirect Square Root and cannot be left at the initial value of zero. When L_TYPE = Direct, XD_SCALE and OUT_SCALE must contain the same range values (EU_0 and EU_100). Check the L_TYPE setting. Check XD_SCALE and OUT_SCALE Reports are not selected in FEATURE_SEL. If features do not include Reports then the host must poll for alarms. Set LIM_NOTIFY to a value higher than zero, but not higher than MAX_NOTIFY. Check that process and block alarms are not disabled. Cannot set alarm limits. Read Scaling. Limit values are outside the OUT_SCALE.EU_0 and OUT_SCALE.EU_100 values. Set values within range. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 185

202 Troubleshooting the Proportional Integral Derivative (PID) block Table 30: PID block Problem Cause Things to check Recommended action PID block mode is in OOS mode, and does not change to AUTO, CAS, RCAS and ROUT mode. PID block mode is in OOS mode with Block configuration Error. Mode does not change from IM, target mode is MAN, AUTO, or Cas. Mode does not change from MAN; target mode is MAN, AUTO, or Cas. Mode does not go to Cas, target mode is Cas. Value of output does not make sense Block alarms are not reported Read MODE_BLOCK.PERMITTED. Read MODE_BLOCK. ACTUAL of Resource block. Schedule Read parameters: BYPASS SHED_OP Read SP_HI_LIM, SP_LO_LIM OUT_HI_LIM, OUT_LO_LIM No path to process. Check Input blocks. Check Upstream block. Check Cascade Initialization Read FEATURE_SEL Read LIM_NOTIFY Add AUTO, CAS, RCAS and ROUT modes to MODE_BLOCK.PERMITTED. If necessary, Set MODE_BLOCK.TARGET to AUTO. NOTE: If the mode is set to OOS for maintenance then do not change the mode to AUTO. Block is not scheduled and therefore cannot execute to go to Target Mode. Schedule the block to execute. The default values of these parameters are configuration errors and they must be set to a valid range. See Table 35. Check that SP_HI_LIM < SP_LO_LIM, OUT_HI_LIM < OUT_LO_LIM. Assure that the downstream blocks to at least one AO are all in Cas mode and that the path ends in an AO block. All BKCAL connections must be linked. The status of IN is Bad, not connected. The upstream block cannot not able to complete cascade initialization for some reason. Assure that BKCAL_OUT is connected to BKCAL_IN of the upstream block. Assure that the output can move an actuator. Reports are not selected in FEATURE_SEL. If features do not include Reports then the host must poll for alarms. Set LIM_NOTIFY to a value higher than zero, but not higher than MAX_NOTIFY. Page 186 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

203 Troubleshooting the Input Selector block Table 31: Input Selector block Problem Cause Things to check Recommended Action Input Selector block mode is in OOS and does not change to AUTO mode. Input Selector block mode is in OOS mode with Block configuration Error. Status of output is Bad. Block alarms are not reported. Read MODE_BLOCK.PERMITTED. Read MODE_BLOCK. ACTUAL of Resource block. Schedule Check SELECT_TYPE Check Inputs Check OP_SELECT Check MIN_GOOD Read FEATURE_SEL. Read LIM_NOTIFY. Add AUTO mode to MODE_BLOCK.PERMITTED. If necessary, Set MODE_BLOCK.TARGET to AUTO. NOTE: If the mode is set to OOS for maintenance then do not change the mode to AUTO. Block is not scheduled and therefore cannot execute to go to Target Mode. Schedule the block to execute. SELECT_TYPE must be set to a valid value and cannot be left at 0. Make sure at least one input has status as good. OP_SELECT is not set to 0 (or it is linked to an input that is not used), and it points to an input that is Bad. Make sure that value entered in MIN_GOOD is greater or equal to actual number of Good inputs. Reports are not selected in FEATURE_SEL. If features do not include Reports then the host must poll for alarms. Set LIM_NOTIFY to a value higher than zero, but not higher than MAX_NOTIFY. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 187

204 Troubleshooting the Arithmetic block Table 32: Arithmetic block Problem Cause Things to check Recommended Action Arithmetic block mode is in OOS and does not change to AUTO mode. Mode does not change from OOS. Value of output is incorrect Block alarms are not reported. Read MODE_BLOCK.PERMITTED Read MODE_BLOCK. ACTUAL of Resource block. Configuration error. Error in configuration. Read FEATURE_SEL. Read LIM_NOTIFY. Add AUTO mode to MODE_BLOCK.PERMITTED. If necessary, set MODE_BLOCK.TARGET to AUTO. NOTE: If the mode is set to OOS for maintenance, then do not change the mode to AUTO. BLOCK_ERR shows the Block Configuration Error condition, since ARITH_TYPE is not set. Ensure that engineering units are correct for the computation. If that fails, see section 3. Reports are not selected in FEATURE_SEL. If features do not include reports then the host must poll for alarms. Set LIM_NOTIFY to a value higher than zero, but not higher than MAX_NOTIFY. Page 188 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

205 Troubleshooting the Output Splitter block Table 33: Output Splitter block Problem Cause Things to check Recommended Action Arithmetic block mode is in OOS and does not change to AUTO mode. Mode does not change from OOS. Value of output is incorrect Block alarms are not reported. Read MODE_BLOCK.PERMITTED Read MODE_BLOCK. ACTUAL of Resource block. Configuration error. Error in configuration. Read FEATURE_SEL. Read LIM_NOTIFY. Add AUTO mode to MODE_BLOCK.PERMITTED. If necessary, set MODE_BLOCK.TARGET to AUTO. NOTE: If the mode is set to OOS for maintenance, then do not change the mode to AUTO. BLOCK_ERR shows the Block Configuration Error condition. This could be because The block IN_ARRAY is not configured correctly or LOCKVAL is not set to a valid value Ensure that engineering units are correct for the computation. Also check if IN_ARRAY and OUT_ARRAY are configured correctly. Reports are not selected in FEATURE_SEL. If features do not include reports then the host must poll for alarms. Set LIM_NOTIFY to a value higher than zero, but not higher than MAX_NOTIFY. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 189

206 Troubleshooting the Signal Characterizer block Table 34: Signal Characterizer block Problem cause Things to check Recommended action Signal characterizer block mode is in OOS and does not change to AUTO mode. Mode does not change from OOS Read MODE_BLOCK.PERMITTED. Read MODE_BLOCK. ACTUAL of Resource block. Configuration error. Add AUTO mode to MODE_BLOCK.PERMITTED. If necessary, Set MODE_BLOCK.TARGET to AUTO. NOTE: If the mode is set to OOS for maintenance, then do not change the mode to AUTO. BLOCK_ERR shows the Block Configuration Error condition, due to array configuration errors. Value of output is incorrect Error in X or Y array. See section 3. Block alarms are not reported. Read FEATURE_SEL Read LIM_NOTIFY Reports are not selected in FEATURE_SEL. If features do not include reports then the host must poll for alarms. Set LIM_NOTIFY to a value higher than zero, but not higher than MAX_NOTIFY. Page 190 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

207 Resolving the block configuration errors Table 35 lists the parameters of all the blocks that can cause the status bit of Block Configuration Error to be set in their respective BLOCK_ERR parameters. The following table provides the initial values and the valid range for the parameters. Table 35: Resolving block configuration errors Parameter Initial Value Valid Range Corrective Action ALERT_KEY 0 non-zero Initial Value is a configuration error. Set value to non-zero number. SIMULATE 1 (disabled) 1-2 (disabled - enabled) XD_SCALE 0 to 10m EU_100 > EU_0, UNITS_INDEX matches output of transducer block Set value in valid range. Set values to valid range(s). OUT_SCALE 0 to 10m EU_100 > EU_0 Set values to valid range. CHANNEL Initial Value is a configuration error. Set value to valid range. L_TYPE 0 (Uninitialize) 1,2,3 (direct, indirect, sq. root) Initial Value is a configuration error. Set value to valid range. PV_FTIME Set value to valid range. ALARM_HYS 0.5 (%) 0-50 (%) Set value to valid range. HI_HI_PRI, HI_PRI, LO_LO_PRI, LO_PRI Set value to valid range. HI_HI_LIM, HI_LIM +INF +INF or within OUT_SCALE range Set value to valid range. LO_LIM, LO_LO_LIM -INF -INF or within OUT_SCALE range Set value to valid range. BYPASS 0 1:OFF, 2:ON Initial value is a configuration error. Set value in valid range. SHED_OPT see Shed Options in the FF specs.) Initial value is a configuration error. Set value in valid range. HI_HI_LIM HI_LIM +INF +INF PV_SCALE, +INF Values must be set in rank order. For example, LO_LIM > LO_LO_LIM but < HI_LIM etc. LO_LIM -INF PV_SCALE, -INF Values must be set in rank order. LO_LO_LIM -INF OUT_HI_LIM OUT_LO_LIM OUT_SCALE +/- 10% Verify that OUT_HI_LIM > OUT_LO_LIM. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 191

208 Parameter Initial Value Valid Range Corrective Action SP_HI_LIM SP_LO_LIM PV_SCALE +/- 10% Verify that SP_HI_LIM > SP_LO_LIM. Page 192 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

209 7.4 Device Diagnostics SLG 700 FF level transmitter memory The transmitter contains a number of areas of memory. An EEPROM provides a non-volatile memory area for static and non-volatile parameter values. The transmitter also contains areas of RAM and ROM. Performing diagnostics in the background Block objects (Resource, Transducer and Function blocks), the communications stack and other device objects, each of them have an allotted area of memory for their corresponding database. Diagnostic routines are performed in the background during device operations that checks the integrity of these individual databases. When a failure is detected, a status bit is set in the BLOCK_ERR parameter in the appropriate block object. Diagnostic checks are performed continuously on the device functional databases of the transmitter application shown in Table 36. Table 36: Diagnostics Device Functional Area Block object database (DB) Communication stack database (DB) Boot ROM Program ROM Trend and link object databases (DB) Location RAM and EEPROM EEPROM ROM ROM ROM BLOCK_ERR parameter BLOCK_ERR parameter shows diagnostic faults of hardware and software components within the transmitter. Each block object in the transmitter device application contains a BLOCK_ERR parameter. BLOCK_ERR is actually a bit string, which provides a means to show multiple status or error conditions. A status message identifying the fault can be viewed by accessing the parameter. Table 3 shows the bit mapping of the BLOCK_ERR parameter. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 193

210 Transmitter Diagnostics Transmitter faults are grouped into one of these three diagnostic categories and could cause the following results: 1. Non-Critical Fault Transmitter continues to calculate PV output. 2. Critical Fault Transmitter drives PV output to failsafe state. 3. Block Configuration Errors Incorrect parameter values causes the transmitter to generate a fault, for example, BLOCK_ERR or MODE_BLK = OOS. A description of each condition in each category is provided in Table 37, Table 38, and Table 39. The condition is described, a probable cause is stated and a recommended corrective action is given for each fault. Page 194 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

211 7.5 Function Block Faults Checking the status and values of key block parameters helps in identifying the type of function block fault whether it is critical or non-critical. Table 37 helps in identifying the type of function block fault and provides corrective action to restore normal operation. Table 37: Identifying Critical and Non-critical Function block faults Block. Parameter Value Fault Type Action AI.OUT = Bad/sensor failure Critical See AI.BLOCK_ERR for message. See Table 3 for details on BLOCK_ERR. See BLOCK_ERR of all blocks in device for message. See Table 39. STATUS = Bad/device failure Critical See AI.BLOCK_ERR for message. See Table 3. See BLOCK_ERR of all blocks in device for message. See Table 39 Good/constant Uncertain Noncritical See Table 38 AI.ALARM_SUM. CURRENT = Block alarm Critical/ Noncritical See BLOCK_ERR of all blocks in the device in Table 3. Process alarm Noncritical See Table 38. All Blocks BLOCK_ERR= Block Configuration Error (1) Noncritical Check the value of all configurable parameters in the block and correct if necessary. See Resolving the block configuration errors. See Table 3 for description of BLOCK_ERR (messages) Simulation Active (3) Noncritical Set "simulate jumper" to "N" on the electronics board, and set the ENABLE_DISABLE field to 1 of the SIMULATE parameter. See section 7.6. Input Failure/Process Variable has Bad Status (7) Critical Write Processor or (4) to RESTART parameter of resource block. If failure continues, replace the sensor board. Memory Failure (9) Critical Set Resource block to OOS. Lost Static Data (10) Critical Write Processor or (4) to RESTART parameter. Lost NV Data (11) Critical Wait for 10 seconds. Rev.5 FOUNDATION Fieldbus Option User's Manual Page 195

212 Block. Parameter Value Fault Type Action Readback Check Failed (12) Out-of-Service (15) Critical Noncritical See Critical Fault NOTE. Write proper mode to MODE_BLK parameter. Unable to write values to valid device parameters. Configur ation Error See Resolving the block configuration errors. ATTENTION Depending on the fieldbus interface application, device operating status and parameter values may appear as text messages. The text in the table is typical of values or messages seen when using the NI-FBUS configurator. Critical Fault In the case of a critical fault due to Memory Failure, NV/Static data loss or the readback check failure, writes to the RESTART parameter twice, for the transmitter to fully recover from the fault condition. Therefore: 1. Write 4 or restart processor to RESTART parameter of resource block. 2. Wait until communication is established. 3. If the fault occurs again, repeat the write to the RESTART parameter. 4. If the fault occurs again, replace the transmitter communication module. Note that if a ROM error (Memory Failure) occurs in the resource block, it may take up to 10 seconds for the fault to reappear. Page 196 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

213 Table 38 summarizes the conditions that could cause a non-critical fault in the transmitter along with recommended actions to correct the fault. Table 38: Summary of Function blocks Non-critical Faults Problem/Fault Probable Cause Recommended Action AI block is executing, but status of OUT parameter is: Good::[alarm status]:constant AI block is executing, but status of OUT parameter is: Uncertain::[alarm status]: inaccurate AI block is in Manual mode. PV value of transducer block is outside range of XD_SCALE. When AI block CHANNEL = 1(OR) OUT value of AI block is outside of OUT_SCALE range. Write AUTO to MODE_BLK parameter of AI block. Sensor board may have been damaged. Check the transmitter for accuracy and linearity. Replace the sensor board and recalibrate, if needed. AI block is executing, but status of OUT parameter is: One of the following AI alarms is active in ALARM_SUM.CUR RENT HI_HI, HI, LO, LO_LO - OUT has crossed the corresponding limit HI_HI_LIM, HI_LIM, LO_LIM, LO_LO_LIM, and is either still past the limit or is in the hysteresis range. ALARM_HYS is the percentage of OUT_SCALE that is used for alarm hysteresis. Block alarm. Reduce the value or increase limits. Check BLOCK_ERR for status bit. See Table 3 Rev.5 FOUNDATION Fieldbus Option User's Manual Page 197

214 Table 39 summarizes the conditions that could cause a critical fault in the transmitter along with recommended actions to correct the fault. Table 39: Summary of Function blocks Critical Faults Problem/Fault Probable Cause Recommended Action AI block is executing, but status of output is: Bad:[alarm status]: sensor failure AI block is executing, but status of output is: Bad::[alarm status]: device failure One of the FAIL conditions in Field Diagnostics has got Set.. Sensor board has stopped communicating with the communication board. If the diagnostics is related to input being open, check the connections as per the connections diagram. If the failure still exists, write "4" or restart processor to RESTART parameter of resource block. If the failure persists and sensor related, replace the sensor board if the. If the failure persists and communication board related, replace the communication board. Write "4" or restart processor to RESTART parameter of resource block. If failure is still present, replace communication board. Page 198 FOUNDATION Fieldbus Option User's Guide Rev. 3.0

215 7.6 Understanding simulation mode About the simulation mode jumper If the process is not running, a simulation mode is available in the transmitter which aids in system debug. When simulation mode is enabled, the SIMULATE parameter in the AI and DI blocks provide a user-selected value as the input to the AI or DI block. Setting the simulation jumper A hardware jumper on the Communication board is set to enable or disable the SIMULATE parameter. See Figure 37 for jumper location. Table 40 shows how to set the simulation jumper on the Communication board. Figure 37: Simulation Jumper Location on Communication Board Rev.5 FOUNDATION Fieldbus Option User's Manual Page 199