SMAR HI302 User Manual

Download

  HART / Foundation Fieldbus  

  SCADA  www.esma-rt.ru

smar

Specifications and information are subject to change without notice.

Up-to-date address information is available on our website.

web: www.smar. c om/contactus.asp

www.smar.com

Introduction

INTRODUCTION

The HI302 is a device integrated to System302 which main function is to interface HA RT devices to F

OUNDATION

status monitoring, device status, among other information. See below some HI302 features:

• Integral part of System302.

• Tight integration with different system manufactures due to the use of standard protocols such

as FOUNDATIONTM fieldbus and HART.

• 8 HART master channels.

• Optional Analog Conversion (4-20 mA / FOUNDATIONTM fieldbus – HI302-I and FOUNDATIONTM

fieldbus / 4-20 mA – HI302-O).

• Totally integrated to AssetView.

• Uniform systems and tools, making it easy to operate and reducing maintenance costs.

• Non-multiplexed and independent HART channels.

• HART Configuration Commands located into the module, allowing HART messages to be sent

through bypass parameters.

• Suitable for Asset Management systems.

• Complete configuration of Smar devices enclosed in the HI302 module, thus no additional

configuration is required.

• Configuration for third party equipments can also be embedded in the Flash memory or added through F

• Registered in Fieldbus F

fieldbus systems, allowing the user to perform maintenance, calibration, sensor

OUNDATION

fieldbus blocks.

OUNDATION, it successfully has passed by rigorous interoperability tests.

III

HI302 - User’s Manual

Table of Contents

TABLE OF CONTENTS

CHAPTER 1 - OVERVIEW...........................................................................................................................1.1

GENERAL CHARACTERISTICS................................................................................................................................1.1

FUNCTION BLOCKS ..................................................................................................................................................1.2

HART COMMUNICATION BLOCKS...........................................................................................................................1.2

ANALOG BLOCKS......................................................................................................................................................1.3

TECHNICAL CHARACTERISTICS.............................................................................................................................1.4

CHAPTER 2 - INSTALLATION....................................................................................................................2.1

INSTALLATION OF THE HI302 MODULES...............................................................................................................2.1

MECHANICAL INSTALLATION..................................................................................................................................................2.1

ELECTRICAL CONNECTIONS..................................................................................................................................................2.1

HART DEVICE INSTALLATION..................................................................................................................................2.4

DEVICE TYPES ..........................................................................................................................................................2.4

LOW IMPEDANCE DEVICES ....................................................................................................................................................2.4

HIGH IMPEDANCE DEVICES....................................................................................................................................................2.4

HART INSTALLATION TOPOLOGY..................................................................................................... ......................2.4

SUPPLY VOLTAGE VS. TOTAL LOOP IMPEDANCE...............................................................................................................2.5

EXAMPLE WITH HI302-N (WITHOUT ANALOG CONVERSION) .............................................................................................2.5

HI302-I (4-20 MA TO FOUNDATION FIELDBUS CONVERSION).............................................................................................2.6

HI302-O (FOUNDATION FIELDBUS TO 4-20 MA CONVERSION)...........................................................................................2.7

MAXIMUM CABLE LENGTH.......................................................................................................................................2.7

OTHER DEVICES IN THE LOOP...............................................................................................................................2.7

PORTABLE CONFIGURATOR ..................................................................................................................................................2.7

INDICATORS AND CONVERTERS IN GENERAL.....................................................................................................................2.8

SWITCHING ON THE HI302.......................................................................................................................................2.8

UPDATING THE HI302 FIRMWARE ..........................................................................................................................2.8

CHAPTER 3 - BASIC CONFIGURATION ...................................................................................................3.1

INSTRUCTIONS ON HI302 CONFIGURATION.........................................................................................................3.1

CONFIGURING THE HCFG BLOCK..........................................................................................................................3.2

HART COMMUNICATION OPERATION PARAMETERS..........................................................................................................3.2

HART COMMUNICATION DIAGNOSTIC PARAMETERS.........................................................................................................3.3

CONFIGURING THE HIRT BLOCK............................................................................................................................3.3

CONFIGURING THE HVT BLOCK.............................................................................................................................3.7

HI302-I - CONFIGURING THE MAI OR AI BLOCKS..................................................................................................3.8

HI302-O – CONFIGURING THE MAO OR AO BLOCKS ...........................................................................................3.8

STARTING THE HI302 OPERATION.........................................................................................................................3.8

CALIBRATING THE HI302 ANALOG BOARDS .........................................................................................................3.8

HI302-I CALIBRATION (GLL1205).............................................................................................................................................3.9

HI302-O CALIBRATION (GLL1194)...........................................................................................................................................3.9

CHAPTER 4 - ADVANCED CONFIGURATION ..........................................................................................4.1

SPECIFIC HART COMMAND CONFIGURATION WITH HCD AND HWPC BLOCKS..............................................4.1

BASIC INSTRUCTIONS ON HART PROTOCOL.......................................................................................................4.1

TYPES OF HART COMMANDS..................................................................................................................................4.1

DESCRIBING THE HART COMMANDS.....................................................................................................................4.2

SETTING THE DEFINITION OF THE HART COMMANDS........................................................................................4.2

CONFIGURING THE HCD BLOCK.............................................................................................................................4.3

MAPPING THE HART VARIABLE AS FOUNDATION FIELDBUS PARAMETERS ...................................................................4.4

HVT ALLOCATION MAP AND COMMAND DESCRIPTION......................................................................................4.4

REQUEST PARAMETERS .........................................................................................................................................4.4

RESPONSE PARAMETERS.......................................................................................................................................4.4

WHAT ABOUT THE RESPONSE CODE?..................................................................................................................4.5

COMMAND 0..............................................................................................................................................................................4.7

COMMAND 3..............................................................................................................................................................................4.8

COMMAND 13............................................................................................................................................................................4.9

COMMAND 18..........................................................................................................................................................................4.10

HI302 - User’s Manual

WHAT ABOUT THE PARAMETER WRITING?........................................................................................................4.11

SETTING THE HWPC BLOCK CONFIGURATION..................................................................................................................4.11

CONFIGURATION OF THE HWPC FOR THE GIVEN EXAMPLE ...........................................................................................4.11

CHAPTER 5 - OPERATION.........................................................................................................................5.1

INITIALIZATION..........................................................................................................................................................5.1

LEDS STATUS............................................................................................................................................................5.1

LED ON......................................................................................................................................................................................5.1

LED FAIL....................................................................................................................................................................................5.1

LED SAVING..............................................................................................................................................................................5.2

H1 LED.......................................................................................................................................................................................5.2

CH#1 TO CH#8 LEDS................................................................................................................................................................5.2

AUXILIARY PUSH BUTTONS.....................................................................................................................................5.2

UNDERSTANDING THE HART COMMUNICATION..................................................................................................5.3

BLK_EXEC_STATE PARAMETER............................................................................................................................................5.3

BLK_ERROR AND DEVICE_STATUS PARAMETERS .............................................................................................................5.4

HIRT BLOCK OPERATION........................................................................................................................................................5.4

HART VARIABLE WRITING AND READING .............................................................................................................5.5

HART VARIABLES READING CYCLES ....................................................................................................................................5.5

WRITING ON PARAMETERS THAT MAP THE HART VARIABLES .........................................................................................5.5

OPERATING THE HVT BLOCK..................................................................................................................................5.7

SEQUENCE FOR HVT READING CYCLE.................................................................................................................................5.7

WRITING SEQUENCE IN HVT BLOCK PARAMETER..............................................................................................................5.8

HI302 VERSUS PORTABLE PROGRAMMERS (FIELD ALTERATIONS).................................................................5.9

STATIC REVISION (ST_REV) PARAMETER.............................................................................................................5.9

CONCLUSIONS ON THE STATIC REVISION:........................................................................................................................5.10

HART RESPONSE CODE CONVERSION TO STATUS FOUNDATION FIELDBUS..............................................5.10

BYPASS MODE ........................................................................................................................................................5.10

SEQUENCE FOR SENDING A HART MESSAGE THROUGH A BYPASS.............................................................................5.11

EXAMPLE..................................................................................................................................................................5.11

CHAPTER 6 - BASIC FUNCTIONING THEORY.........................................................................................6.1

THE HI302 BLOCK DIAGRAM....................................................................................................................................6.1

HARDWARE................................................................................................................................................................6.1

POWER SUPPLY, OPERATION VOLTAGE AND PROTECTION.............................................................................6.2

HOT SWAP ................................................................................................................................................................................6.2

REGULATORS...........................................................................................................................................................................6.2

PROTECTION............................................................................................................................................................................6.2

ELECTROSTATIC DISCHARGE (ESD).....................................................................................................................................6.3

SURGES, HIGH VOLTAGE AND GROUNDING........................................................................................................................6.3

PROCESSING CORE.................................................................................................................................................6.3

FIRMWARE PROGRAMMING...................................................................................................................................................6.3

EPLD PROGRAMMING .............................................................................................................................................................6.4

MANUAL RESET KEY AND FACTORY INIT.............................................................................................................................6.4

HI302 MODULE RESETTING.....................................................................................................................................6.5

H1 FIELDBUS COMMUNICATION.............................................................................................................................6.5

HART COMMUNICATION...........................................................................................................................................6.5

4-20MA TO FOUNDATION FIELDBUS ANALOG CONVERSION (HI302-I)..............................................................6.5

FOUNDATION FIELDBUS TO 4-20MA ANALOG CONVERSION (HI302-O)............................................................6.6

CHAPTER 7 - AN EXAMPLE OF HI302 USAGE........................................................................................7.1

INSTALLATION...........................................................................................................................................................7.1

STEP BY STEP CONFIGURATION............................................................................................................................7.1

STEP BY STEP OPERATION.....................................................................................................................................7.3

CHAPTER 8 - TROUBLESHOOTING .........................................................................................................8.1

INSTALLATION...........................................................................................................................................................8.1

CONFIGURATION ......................................................................................................................................................8.1

OPERATION ...............................................................................................................................................................8.2

QUESTIONS AND ANSWERS....................................................................................................................................8.3

Table of Contents

APPENDIX A - HCFG - HART CONFIGURATION & DIAGNOSTIC.......................................................... A.1

HIRT - HART INFORMATION & DYNAMIC DATA AND HUT – HART UNIVERSAL TRANSDUCER......................A.3

HVT – HART VARIABLE TEMPLATE.......................................................................................................................A.12

HCD – HART COMMAND DEFINITION ...................................................................................................................A.14

HWPC – HART WRITE PARAMETER CONFIGURATION......................................................................................A.16

HBC - HART BYPASS COMMUNICATION..............................................................................................................A.17

APPENDIX - B - HART COMMAND CONFIGURATION IN FLASH MEMORY......................................... B.1

HIRT BLOCK...............................................................................................................................................................B.1

SENT HART READING COMMAND USED BY THE HIRT BLOCK...........................................................................B.1

IDENTIFICATION HART COMMANDS.......................................................................................................................B.1

HART WRITING AND EXECUTION COMMANDS USED BY THE HIRT BLOCK.....................................................B.1

HVT BLOCK ................................................................................................................................................................B.2

APPENDIX C - HVT'S ALLOCATION MAP ...............................................................................................C.1

HVT'S ALLOCATION MAP FOR FY301 ....................................................................................................................C.1

HVT'S ALLOCATION MAP FOR LD301 ....................................................................................................................C.6

HVT'S ALLOCATION MAP FOR TT301...................................................................................................................C.10

HVT'S ALLOCATION MAP FOR DT301.................................................................................................................. C.14

HVT'S ALLOCATION MAP FOR TP301 ..................................................................................................................C.17

HVT'S ALLOCATION MAP FOR LD291 ..................................................................................................................C.18

APPENDIX D - CODES FOR SMAR HART VARIABLES AND CONFIGURATION OF THE HIRT BLOCK

FOR THE ASSETVIEW............................................................................................................................... D.1

FY301 INTELLIGENT VALVE POSITIONER............................................................................................................. D.1

AVAILABLE VARIABLES ..........................................................................................................................................................D.1

CONFIGURATION OF THE HIRT BLOCK FOR ASSETVIEW..................................................................................................D.1

LD301 AND LD291 INTELLIGENT PRESSURE TRANSMITTER............................................................................. D.2

VARIABLES LIST OF THE HART COMMAND #33...................................................................................................................D.2

CONFIGURATION OF THE HIRT BLOCK FOR ASSETVIEW..................................................................................................D.2

TT301 INTELLIGENT TEMPERATURE TRANSMITTER.......................................................................................... D.2

VARIABLES LIST OF THE HART COMMAND #33...................................................................................................................D.2

CONFIGURATION OF THE HIRT BLOCK FOR ASSETVIEW..................................................................................................D.2

DT301 INTELLIGENT DENSITY TRANSMITTER..................................................................................................... D.3

VARIABLES LIST OF THE HART COMMAND #33...................................................................................................................D.3

CONFIGURATION OF THE HIRT BLOCK FOR ASSETVIEW..................................................................................................D.3

TP301 INTELLIGENT PRESSURE TRANSMITTER................................................................................................. D.3

VARIABLES LIST OF THE HART COMMAND #33...................................................................................................................D.3

CONFIGURATION OF THE HIRT BLOCK FOR ASSETVIEW..................................................................................................D.3

APPENDIX E – SRF – SERVICE REQUEST FORM.................................................................................. E.1

APPENDIX F - SMAR WARRANTY CERTIFICATE....................................................................................F.1

VII

HI302 - User’s Manual

VIII

Chapter 1

OVERVIEW

This user’s manual contains instructions about how to install and configure the HI302. If the user already knows how to install the F the HI302 immediately, please, go to the chapter 7.

This manual is compliant to firmware version 6.01 or later and DD 0601 and CF 060101 (or later). Check the parameter HCFG.FIRMWARE_VERSION.

General Characteristics

OUNDATION

fieldbus and HART devices and wants to work with

Figure 1.1 – HI302-I Module

Among the main characteristics, the following may be mentioned:

• The HI302 supports up to eight point-to-point HART devices or 32 HART devices in the multidrop mode (4 devices per channel). Consult Smar about multidrop option;

• 8 HART Master communications ports that can be configured as Primary or Secondary;

• 1 F

OUNDATION fieldbus H1 Channel;

• Fed via rack (5Vdc @400 mA);

• Device’s power supply should be from an external source;

• Input circuits 4-20 mA on HI302 – I (current conversion to F

• Output circuits 4-20 mA on HI302 – O (F

There are three models for the HI302, according to the analog conversion needs:

• HI302 – N: only HART communication;

• HI302 – I : HART communication and conversion of eight 4-20 mA analog inputs to F

fieldbus;

• HI302 – O: HART communication and F

outputs.

OUNDATION fieldbus conversion to current).

OUNDATION fieldbus conversion to eight 4-20 mA analog

OUNDATION fieldbus );

OUNDATION

1.1

HI302 - User’s Manual

Function Blocks

Several blocks were implemented to give the module the required functionality. The HI302 is registered Fieldbus F

HART Communication Blocks

HCFG (HART Configuration and Diagnostic) – Concentrates general configuration parameters for

module operation, in addition to parameters on HART Communication performance and diagnostic. It also concentrates parameters for analog circuit calibration.

HIRT (HART Information and Dynamic Data) – This block contains the main parameters, i.e., the

most commonly used, besides dynamic variables. All parameters related to universal commands and some main “Common Practice” commands are found here. There should be one HIRT block for each HART device installed. In normal operation, the HIRT block parameters show the HART device variables, since there are mechanisms to keep the HI302 database updated. See the Appendix A or the Function Blocks manual for further details. All of the HART dynamic variables should be accessed through this block. The HIRT block has 8 output parameters which may be used to make HART variables available in the control strategy, through the link with other blocks.

HUT (HART Universal Transducer), is equal to HIRT, but it does not has the 8 output parameters.

It allows supervising all HART variables. This block may be used in third part F systems that are not compatible with specific function blocks as the HIRT block.

Figure 1.2 – Hart/4-20 mA

OUNDATION equipment.

OUNDATION fieldbus

1.2

Analog Blocks

Overview

HVT (HART Variable Template) – This block is a large collection of variables for general use. It is

now possible to access any HART instrument parameter, specially associated to specific HART commands. To this effect, the module should get a configuration (HCD and HWPC blocks) to define the specific instrument to be accessed, and how these commands will relate to each parameter on the block. There is just one HVT block that should be shared among the devices when accessing them. This configuration is already in the HI302’s Flash memory, when it is also possible to include third party configurations according to the application’s needs.

HCD (HART Command Definition) – It contains the HART command description for each device

type or version. This description stores information needed by the module to communicate and the data read on the HIRT or HVT blocks. The HCD blocks that defining the universal and the common practice commands, as well as all commands specific to Smar instruments, are already stored in the equipment’s memory and do not require any configuration from the user. See the Appendix B for details. Configuration of specific commands for third party devices can be made through this block.

HWPC (HART Write Parameter Configuration) - This block stores information about all

parameters to be written in the instrument and mapped in the HVT block. See table with detailed definitions on the Appendix A.

HBC (HART Bypass Communication) - This block allows directly the sending and receiving of

HART messages. Ideal for use with Hosts that access directly the HART devices through its commands, using for example its DD. For more information see the BYPASS Communication Mode section.

In order to support the analog circuits on HI302-I and HI302-O modules, use the AI/MAI or AO/MAO blocks F fieldbus or F

OUNDATION fieldbus

OUNDATION fieldbus to 4-20 mA.

standard, respectively, to convert the analog 4-20 mA to FOUNDATION

AI – Analog Input

Analog input block FOUNDATION fieldbus standard. It allows associating its input to one of the analog channels through the CHANNEL (1 to 8) parameter. It allows instantiate 8 blocks.

MAI – Multiple Analog Input

The MAI block FOUNDATION fieldbus standard makes available to the fieldbus network 8 variables of the I/O subsystem through 8 output parameters, namely, OUT_1 to OUT_8. These parameters correspond to the current value, in percentages, on the 8 analog inputs. The current values read through this parameter may be linked to any other block, as part of the control strategy. It allows instantiate 1 block

AO – Analog Output

Analog output block F

OUNDATION fieldbus

standard. It allows associating its output to one of the

analog channels through the CHANNEL (1 to 8) parameter. It allows instantiate 8 blocks.

MAO – Multiple Analog Output

The MAO block F

OUNDATION fieldbus

standard makes available to the I/O subsystem 8 input parameters, IN_1 to IN_8. These parameters correspond to the current value on the 8 analog outputs. Through the MAO block, it is possible to control the current of each loop from another block’s output that is part of the control strategy. It allows instantiate 1 block

1.3

HI302 - User’s Manual

Technical Characteristics

Power Supply

Input voltage 5 Vdc±5% @ 400 mA, maximum ripple of 20 mVpp, via rack Maximum consumption 2 W Indication Green LED – the device is powered

Memory

Operational system, applications and resident configurations 512 Kb – Super Flash User’s configuration 32 Kb – EEPROM General purpose memory 128 Kb - SRAM

Processor

Processor HC11 @ 16 MHz

Indication

HI302-I - Analog Input 4-20 mA

Input Impedance 250 Ω

A/D Converter

Input filter Low pass filter, fc~10 Hz

Isolation

Power supply Supply of the HART devices through external power supply Input Protections Polarity inversion, over voltage, transients, etc.

HI302-O - Analog Output 4-20 mA

D/A converter

Isolation

Power supply Supply of the HART devices through external power supply Protection Protected by TVS and zener diode Current control Passive circuit, with current control: sink Voltage on output terminals Maximum voltage 36 V (zener protection)

HI302-N - Only HART Communication

Isolation Isolation between channels 500Vrms Coupler with the Loop Capacitive

- Red LED - indicating fail

- Yellow LED - indicating saving in the EEPROM

Range: 3.8 to 21 mA A/D converter: 16 bits Accuracy 0.05%

of range Repeatability: ±0.01% of range. Nonlinearity: ±0.01% of range Temperature effect: ±0.001%/ºC.

Field isolation through optical couplers and DC-DC converters, 1000 Vrms Inputs are not isolated from each other

Range: 3.8 to 21 mA D/A converter: 12 bits Accuracy: 0.05% of range Repeatability: ±0.02% of range. Nonlinearity: ±0.002%. Temperature effect: ±0.00025%/ºC. Field isolation through optical couplers and DC-DC converters, 1000 Vrms Outputs are not isolated from each other

It can reach until ±0.2% under severity EMI conditions (Electromagnetic Interference).

Foundation is a trademark of Fieldbus Foundation.

1.4

Overview

HART

Supported Versions

Supports HART devices versions 5. Consult Smar about its use with other HART protocol versions. Resident configuration for Smar devices. Consult Smar about its

Configurations

use with third part HART devices. Allows configuration of specific HART commands 8 Master ports

Communications ports

Galvanic isolation of 1000 Vrms Non multiplexed, that is, an independent UART per HART port

Indication Green LED – indicating the state of each port

Fieldbus

Controller Dedicated controller – Smar FB3050

Communications channel

1 channel H1, independent with DMA Baud rate of 31.25 Kbps

MAU Passive MAU (not supplied by the bus) with 500 Vrms isolation Physical layer ISA-S50.02.1992 Indication Green LED – indicating communications Fieldbus Foundation Registration ITK 4.61

The HI302-I, HI302-O and HI302-N models were tested and are manufactured in agreement with the IEC-61326:2002 “Electrical

CE Certification

Equipment for Measurement, Control and Laboratory Use – EMC Requirements” standard. The conformity declaration is available for download in the page of the product in

www.smar.com.

Environment Conditions

Operation 0 to 60 °C Storage -20 to 80 °C Humidity 20 to 90% non condensed relative humidity

Dimensions

142 x 40 x 126 mm

Dimensions and weight

5.6 x 1.6 x 5.0 inch Net weight: 450 g. With package: 500 g.

1.5

HI302 - User’s Manual

1.6

Chapter 2

INSTALLATION

This chapter deals with the main physical installation features, namely: mechanical and electrical elements.

All comments or considerations made in this manual refer to HART communication using FSK modulation (Frequency Shift Keying).

Installation of the HI302 modules

Mechanical Installation

The HI302 modules are enclosed in the Smar standard plastic housing, like the LC700 and the DFI302. Therefore, they are fully interchangeable on the standard racks. The picture below shows a typical HI302 installation set:

IMPORTANT

Figure 2. 1 – HI302 modules in racks

The HI302 requires 5V @ 400 mA from the rack. You may use Smar DF50 power supply modules. Besides providing a high quality feeding, they also provide a “Power Fail” signal to prevent power failure or AC problems. However, the user can use another power supply provided it meets the minimum requirement of quality and safety.

The other elements follow the same installation procedure as F devices. For further information on installation procedures, visit our site www.smar.com and download a free copy of the any Smar device’s manuals.

ATTENTION ABOUT GROUNDING

The HI302 is equipment for industrial use that meets the rigorous international standards CE, FF, HART, etc. For to offer the maximum of performance and safety to the users and the equipments connected is fundamental that there is an appropriate grounding, according to NBR-5410, NBR5419, NBR-7117, IEC-200, IEEE-141 or IEEE-142 standards, or other more appropriate local standard. All the power supply, racks, rail, and shield of cables should be grounded appropriately. The grounding should be tested regularly, according to the maintenance plan of each installation, to guarantee the maintenance of its electric properties. As suggestion the safety recommendations of the NR 10 standards or another local standard on electric safety should be respected.

OUNDATION

fieldbus and HART

Electrical Connections

The minimum electrical connections for the HI302 are the power supply, normally connected to the rack, to the connection with the H1 communications bus and to the connection with HART devices. See the following figure for details. Since the HI302 does not supply the devices, it is necessary to use a power supply for them. The DF50 can be used if the devices’ consumption does not exceed 300 mA (about 12 devices), otherwise the DF52 should be used as shown in the figure.

2.1

HI302 - User’s Manual

IMPORTANT

Since the HI302 H1 channel is a passive channel, it is not necessary to use the bus power supply (DF53). For instance, if the DF51 channel is connected to the HI302 channel, they will communicate normally. However, the BT302 terminator should always be used.

2.2

Figure 2. 2 – Example of necessary connections for the HI302

IMPORTANT

The figure above shows the connection of devices supplied by the same power supply module. Remember that the HI302-I and HI302-O analog inputs and outputs are isolated from the field, not from each other, that is, they have the negative terminal internally connected. The HI302-I or the HI302-O can only be connected to an I/O system with a common ground.

The following figure shows an example of an HI302-N connection focused on the HART communication. In order to simplify the connection below, connect the HART channel in parallel to the device, instead of connecting it in parallel to the resistor. Doing so, a common ground should be used to decrease the wiring length. The connection below makes the channel independent from the device’s power supply. Consult Smar for further details about this kind of link.

IMPORTANT

The HI302N channels are isolated from each other, thus they can be connected to different I/O subsystems independently of the grounding or power supply used for the field devices.

Installation

Figure 2. 3 – Example of an HI302 connection

Figure 2. 4 – Connections between the HI302-N and a HART equipment in an I/O system

2.3

HI302 - User’s Manual

HART Device Installation

Now we will describe the main communication features regarding the device installation. For more detailed information about the devices, please read the specific device’s manual. Concerning the HART communication, consider that the superimposition of a modulated signal on an analog current signal can deteriorate, if some precautions are not taken. It is important to mention that the HART communication does not affect modulated signal is zero. Thus, if the HART device is already installed, make sure that the minimum impedance (250 Ω) is used and connect the HI302 channel in parallel to the device.

Device Types

Low Impedance Devices

Low impedance devices are typically signaling elements intended to receive current analog signals or serve as master for a multidrop network. As an example of a low impedance device we can mention the FY301 or input analog cards, such as HI302-I.

High Impedance Devices

High impedance devices control current, either as a mean of analog signaling or at a fixed level in a multidrop topology. As an example of a high impedance device we can mention the LD301, TT301 or analog output cards such as HI302-O.

These concepts are fundamental when connecting different devices. For example, in the connection shown below, it is not necessary to install a 250 Ω resistor for the HART communication. The transmitter’s impedance should be enough. Although it may be necessary to install a resistor in series with the power supply, just to achieve minimum impedance requirement (250 Ω). Each case should be analyzed individually according to the equipment’s characteristics.

the 4-20 mA analog signal, since the average value of a FSK

Whatever the topology used, it is important to keep a 250 Ω impedance. In the previous figure, it is not necessary to connect an impedance in series with the power supply, if the impedance read by the HART channel is at least 250 Ω. In case the impedance is less than 250 Ω, increase its value to the minimum requirement. The connection above allows the communication between the two devices as long as the identification is done via TAG not via Polling Address.

HART Installation Topology

The HI302 complies with several applications, since the new ones to older installations, where it is necessary to increase the HART device’s life span and preserve the investment with the gradual introduction of the F However, the applications are not limited to these examples and should be considered separately.

2.4

Figure 2. 5 – Connection without the 250Ω resistor

IMPORTANT

OUNDATION fieldbus technology. Below are some examples of connections.

Installation

Supply Voltage vs. Total Loop Impedance

The total impedance of the devices connected to the pair of cables and the cable impedance should be kept between the operation limits complying with the loop supply voltage. See the graph below:

Figure 2. 6 – Supply Voltage vs. Total Loop Impedance

Notice that it is very important to keep the minimum impedance (250 Ω) to allow HART communication. Sometimes the voltage supply must be increased to ensure that the system is in the operation area specially when associating devices on the same loop.

Example with HI302-N (without Analog Conversion)

This HI302 model has only HART communication and no circuit for analog conversion. The HI302-N does not have an internal resistor, so it needs an external resistor or active impedance (PSI301) if many devices are used. It is not necessary to use impedance or external resistor, if the loop has already enough impedance to guarantee communication.

• Typical Multidrop There are two ways to perform this connection. The resistor can be installed in series with the power supply or in parallel to the HART channel. The first way is shown below:

• Multidrop with 4-20 mA enabled

Be careful with this topology because some types of I/O devices do not accept the connections presented below, for example, the DCSs that feed the devices via internal power supply. The I/O device must receive external power supply, like PLC cards or field devices. Despite the complexity, this connection allows an improvement in the use of the HI302 channels, and due to the fact that the current that flows in the loop is in the order of by the hundred mA, uses active impedance instead of

Figure 2. 7 – Resistor in series with the power supply

2.5

HI302 - User’s Manual

a simple resistor. See the next figure:

Figure 2. 8 – Parallel impedance with the HART channel

HI302-I (4-20 mA to FOUNDATION Fieldbus Conversion)

In this kind of topology, it is not necessary 250Ω external resistor connected in series with each device, since there is a 4-20 mA sampling resistor in the HI302 analog board serial to the loop.

Figure 2. 9 – 4-20 mA FOUNDATION fieldbus conversion

2.6

Installation

HI302-O (FOUNDATION Fieldbus to 4-20 mA Conversion)

In this topology, it is not necessary to use a resistor in series with the power supply, because the device’s internal impedance and the actuator impedance ensures the minimum requirement for HART communication. However, the user should watch the minimum supply voltage required for total impedance (including the wiring impedance).

Maximum Cable Length

The user may choose from a shielded pair of twisted cables, multipair cables with a single shield or a combination of these.

The shield can be overlooked if noise in the environment or any other interference does not affect the communication.

Use a 24 AWG (0.5 mm least a 20 AWG (0.8 mm

If a cable is longer than 500 m is required, make a detailed analysis of the system to avoid operation failures. According to HCF (HART Communication Foundation), the maximum cable length depends on:

• The cable’s resistance, capacitance and inductance.

• The device’s resistance and capacitance on the HART channel, as well as the additional

equipment.

Due to the complexity of the subject, users should read the HART Foundation Communication documentation, specially the FSK Physical Layer Specification. Consult Smar for further information.

Other devices in the loop

The control loop may have additional devices, besides the HI302 and the HART devices. See some common types as follows.

Portable Configurator

As mentioned before, the HI302 operates as a master in most applications. So, there is no problem in using a portable configurator, such as the HPC401. Whatever the installation topology, make sure to install a 250 Ω impedance serial to the power supply. If no active impedance or resistors are installed, the secondary master device will not communicate.

Figure 2. 10 – FOUNDATION fieldbus to 4-20 mA conversion

IMPORTANT

) cable for lengths up to 1500 meters. For lengths over 1500 meters, use at

) cable.

2.7

HI302 - User’s Manual

Indicators and Converters in general

Indicators and converters are very common in industrial installations. They usually have high impedance in the HART communication frequency (1200 to 2200 Hz). Sometimes the introduction of such elements in the loop can prevent communication. However, there is a simple and well known solution for this problem, by connecting a capacitor ranging from 0.1 to 1μF@200v parallel to the device. This capacitor supplies an impedance of hundreds Ohm parallel to the device’s impedance, allowing the HART communication.

Switching On the HI302

When the module is turned on, the system will check some important hardware and firmware components. If any errors are found, the module will not operate and the FAILURE LED (red LED) will light. The HART LEDs (green LEDs) will blink slowly around 1/4 Hz. This check takes approximately 1 minute, so you should wait before checking the HI302 in the Live List or watch for any value.

Updating the HI302 Firmware

To update the HI302 firmware you must use the FBTools program built in the System302 as an integral part of it. To do so, connect the RS232 (Code: 102A0927) serial cable to the firmware download connector located behind the module. Just remove the protection cover and connect the cable.

Connector with cover

Connector without cover

Connector cover

Figure 2. 11 – Firmware programming connector

2.8

Installation

Figure 2. 12 – Cable connector for firmware download

Before you begin the update, the HI302 module must be set in the bootloader mode. To do so, turn on the HI302 and press for 5 seconds the Reset button located at the upper left side in the front part of the module. After the 5 seconds, the YELLOW SAVING LED and the GREEN LED will light. To updating the firmware follow the steps bellow:

1 - In the System302 version 6.x, to start the FBTools Wizard, click Start → Programs →

System302 → Interfaces → FBTools Wizard. Another way is from the Start menu, selecting Programs→System302→System302 Application, and double-click the FBTools Wizard item.

In the System302 version 7.x, the user has to execute the software from the Studio302 interface. Click Start → Programs → System302 → Studio302, and select Studio302 icon. To launch the

FBTools just click the icon

at the toolbar under the main menu, or in the left panel in the

Studio302 window. The following window will open.

2 - Select HI302 (I, O or N) and click Next. The next figure will appear.

Figure 2. 13 – The FBTools wizard

2.9

HI302 - User’s Manual

Figure 2. 14 – Serial Download dialog box

3 - Click the Browse button

to select the firmware file to be downloaded (HI302*.abs file).

Figure 2. 15 – Choosing the firmware file

4 - After selecting the firmware file, the Download button will be enabled. Click it to start the firmware download.

2.10

Installation

Figure 2. 16 – Downloading the firmware

5 - A message box will appear requesting a confirmation. Click Ok to continue.

6 - After the completion of the update process, press the Reset button again, in order to put the module back in normal operation.

NOTE

As a standard procedure, the user should always do a Factory Init after updating the firmware. Just press the Fct Init button after the equipment returns to normal operation.

Figure 2. 17 – Reset and Fct Init buttons

2.11

HI302 - User’s Manual

2.12

Chapter 3

BASIC CONFIGURATION

Instructions for HI302 Configuration

The minimum configuration to be applied in the Syscon consists of:

• 1 RESOURCE block

• 1 HCFG block

• 1 HIRT block for each HART device

• 1 AI block for current reading

Figure 3.1 – Minimum configuration for the Syscon

The maximum number of blocks and its quantities in the factory configuration are shown belo w:

BLOCK MAXIMUM FCT INIT2 FCT INIT3

RS2 1 1 1

DIAG 1 1 1

MAO/MAI1 1 1 0

AO/AI1 8 8 8

HCFG 1 1 1

HIRT 8 8 0

HUT 8 0 8 HVT 8 0 0 HCD 1 0 0

HWPC 1 0 0

HBC 1 0 0

1 – In HI302-N model consider 0. 2 – Normal version of factory. 3 – Special version for Hosts FF that not support blocks dynamic instantiation, by inquiry.

Limits for applications: Maximum number of blocks: 24 Maximum number of Subscriber links: 12 Maximum number of Publisher links: 19

IMPORTANT

Whenever a download is performed, wait for the yellow SAVING LED to turn off. Only then turn off or reset the equipment. If the equipment is turned off or reset during the data saving process, the configuration must be redone. See the chapter “HI302 Configuration Example” for more details.

3.1

HI302 - User’s Manual

Configuring the HCFG Block

The HCFG block has a series of parameters divided into two categories: operation par ameters and diagnostic parameters.

Figure 3.2 – Operation and diagnostic parameters

HART Communication Operation Parameters

• FIRMWARE_VERSION: A parameter indispensable to solve problems. If something is not working properly, confirm the equipment version before contacting the technical support.

• COMM_BEHAVIOR: Defines the HI302 behavior. It can operate in two ways: if the parameter is Autonomous (default), the HI302 communicates with the HART devices by using the previous

configuration, i.e., in an independent way. The second way uses bypass parameters of HBC block (HART Bypass Communication) to send and receive HART messages. To do so, this parameter should be configured as Bypass.

• COMM_ENABLE: This parameter has two important functions: ♦ To disable the whole HART communication for maintenance and configuration ch anges; ♦ To validate the configuratio n loaded in the equipment and then begin the communication

(afterwards). Its first value is DISABLED. After the configuration download, this parameter should be reset to ENABLED for the new configuration be accepted.

ATTENTION

When changing the channel in the HIRT block or downloading new configurations, this parameter is automatically set on DISABLED, stopping, then, the HART communic ation in all channels. When the download finishes, ENABLED must be set manually. If this procedure is not performed, the HI302 will not work properly.

3.2

• CHANNEL_ACTIVE: This indicates how many HIRT blocks are instantiated for each HART channel. If no HIRT block is instantiated for the channel, the corresponding element of this parameter will display NO and the channel will be deactivated. As a result, there will be no devic e communication or scanning. The LED channel will blink at appro ximately 1/4 Hz. This parameter is useful to check the configuration. The HVT block is also counted in this parameter.

• MASTER_TYPE: This parameter allows for adjusting the channel as a Primary master or as a Secondary master. Remember that each channel is an independent master. In normal conditions,

the channel should be a primary master in order to permit the use of a portable configurator that usually is secondary master.

• RETRIES: This parameter adjusts the number of times the HI302 will try to communicate with a device, before detecting that the device does not respond. The standard value is 3 retries.

HART Communication Diagnostic Parameters

♦ MASTER_SYNCHRONIZED: Indicates if every Master channel has synchronized the

communication layer and if each one is ready to transmit the HART messages in normal operation or in Bypass mode.

♦ CHANNEL_MODE: Indicates if the channel is operating normally or there is any device in

BURST_MODE.

♦ MASTER_STATE: Shows the behavior of the HART state machine at every moment for each

channel

• WATCHING, indicates that the channel is only reading data that passes through the line and are crucial to keep the synchronism if there is an other Master or any device in Burst mode.

• ENABLED, the channel is free to send a HART message.

• USING, indicates that a message was sent and a corresponding res pons e i s e xpected. T he

response has to be sent within the maximum number of retries configured in the RETRIES parameter.

♦ COMM_ERRORS: shows the percentage of detected errors in the communication of each HART

channel. If the error percentage is lower than 0.5%, communication is in high quality.

♦ REQUEST_COUNTER: Totals the number of messages sent by each channel, including the

retries.

♦ RETRIES_COUNTER: Totals the number of repetitions for each channel. A high value in this

parameter (>0.5%) may indicate any installation problem or any comman d not supported b y the device.

♦ INVALID_SOM: Totals the number of invalid SOM (Start of Message) detected in the channel.

A high value in this parameter may indicate installation problems or some device with a problem.

♦ INVALID_RX_FRAMES: Totals the number of HART messages received, but not considered

because of some inconsistency in the message, for example, checksum error.

♦ VALID_RX_FRAMES: Totals the number of valid messages received and processed by the

HI302, even if they are not addressed to it, for example, OACK, OBACK, STX etc.

The counter parameters, used for diagnostic purposes, are always reset when the COMM_ENABLE parameter goes to ENABLED.

Configuring the HIRT Block

This block has a set of parameters that map all of the HART variables that can be accessed by th e universal commands and by some of the most usable “common practice” commands. Remember that there is a HIRT block for each HART device installed and that the configuration may vary according to the model, application type, etc. For more details about the supported comm ands, ref e r to Appendix A.

Basic Configuration

ATTENTION

3.3

HI302 - User’s Manual

3.4

Figure 3.3 – Universal and common practice commands

A minimum set of parameters needs a configuration to allo w the HI302 to work properly. Most of the parameters have standard values that are suitable for many operation cases. Thus, it is not necessary to download them. However, a comprehensive analysis must be done in order to determine the best profile for each device configuration. The HI302 offers several resources that must be understood. The parameters that require configuration to work are the following:

♦ MODE_BLK: Should be set on AUTO. If it is in OS (Out of Service), the communication with the

respective device is interrupted. When the block is set on OS, it returns to the initial identification state. When it is set on AUTO, all the update and identification processes are repeated.

♦ HART_CHANNEL: Indicates the channel on which the de vice is installe d, from 1 to 8. In normal

operation, any change in this parameter will stop the HART communication. See the HCFG.COMM_ENABLE parameter.

♦ POLL_ADDR: Indicates the polling address that has been configured in the device, from 0 to

15. This address is used to recognize the device if the command 0 has been selected in the

ID_CMD parameter.

IMPORTANT

If the HART communication is enabled and this parameter has been written, the HI30 2 will accept the writing in the HART device and will generate a writing transaction. To change this value, without doing it in the device, write DISABLED in the HCFG.COMM_ENABLE parameter or set the block on OS.

♦ HART_TAG: the HART device’s tag that can be configured by the HI302 module or by a

portable configurator. It supports 8 characters and is used by the command 11 to identify the device. The same POLL_ADDR writing observation mentioned previously, applies here.

Basic Configuration

♦ ID_CMD: This parameter indicates to the module which universal comm and identification (0 or

11) will be used to identify the device. The standard value is 0:

• The command 0 uses the “polling address” (POLL_ADDR) and is the most used command.

• The command 11 uses an 8-character tag and can be used provided the device has a tag

configured in the block through the HART_TAG parameter. This option i s indicated when there are devices in multidrop.

IMPORTANT

The identification using TAG is very useful when the device is operating in multidr op mode and the analog signal is enabled, ranging from 4 mA to 20 mA. In this case, the polling address for all devices in the channel should be 0, that is, the identification is impossible through the co mmand 0.

♦ POLL_CTRL: Indicates if the HI302 will keep polling the device after the identification and initia l

fill of the HIRT.

IMPORTANT

The HI302 will poll the device only if the block has p erformed the initial procedure successfully and reached the UPDATE status. See the BLK_EXEC_STATE parameter.

♦ COMMON_CMD_FILTER: This parameter is a set of filters that prevents a HART command

configured and not supported by the device, to be s ent. Their elements should be filled in the HCD block with the definition index of the HART command. See the chapter “Example of Configuration” for more details.

♦ VIEW_SELECTION: Allows the user to choose the group of variables to be updated cyclically in

the polling, according to the following table:

3.5

HI302 - User’s Manual

Dynamic Variables Polling Map

View number 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Needs Configuration? N N Y Y Y Y Y Y YYYYYYYYYYYYYY Y Y Y YYYYYY

Polling cycle [s] 2 3 2 2 2 3 3 3 4 6 1 2 1 1 1 2 2 2 3 5 3 3 3 3 4 4 4 1 1 1 5 Parameter name Updated Parameters

COMM_ERR X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X

DEVICE_STATUS X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X

ADDITIONAL_STATUS X X X X X X X X X X X

LOOP_CURRENT X X X X X X X X X X X X X X

PV_PERC X X X X X X X X X X X X X

PV_UC X X X X X X X X X X X X

PV_VAL X X X X X X X X X X X X

SV_UC X X X X X X X X X X X X

SV_VAL X X X X X X X X X X X X

TV_UC X X X X X X X X X X X X

TV_VAL X X X X X X X X X X X X

QV_UC X X X X X X X X X X X X

QV_VAL X X X X X X X X X X X X

A1_UC X X X X X X X X X X X X X

A1_VAL X X X X X X X X X X X X X

A2_UC X X X X X X X X X X X X X

A2_VAL X X X X X X X X X X X X X

A3_UC X X X X X X X X X X X X X

A3_VAL X X X X X X X X X X X X X

A4_UC X X X X X X X X X X X X X

A4_VAL X X X X X X X X X X X X X

B1_UC X X X X X X X X X X X X X

B1_VAL X X X X X X X X X X X X X

B2_UC X X X X X X X X X X X X X

B2_VAL X X X X X X X X X X X X X

B3_UC X X X X X X X X X X X X X

B3_VAL X X X X X X X X X X X X X

B4_UC X X X X X X X X X X X X X

B4_VAL X X X X X X X X X X X X X

C1_UC X X X X X X X X X X X X X

C1_VAL X X X X X X X X X X X X X

C2_UC X X X X X X X X X X X X X

C2_VAL X X X X X X X X X X X X X

C3_UC X X X X X X X X X X X X X

C3_VAL X X X X X X X X X X X X X

C4_UC X X X X X X X X X X X X X

C4_VAL X X X X X X X X X X X X X

D1_UC X X X X X X X X X X X X

D1_VAL X X X X X X X X X X X X

D2_UC X X X X X X X X X X X X

D2_VAL X X X X X X X X X X X X

D3_UC X X X X X X X X X X X X

D3_VAL X X X X X X X X X X X X

D4_UC X X X X X X X X X X X X

D4_VAL X X X X X X X X X X X X

E1_UC X

E1_VAL X

E2_UC X

E2_VAL X

E3_UC X

E3_VAL X

E4_UC X

3.6

Basic Configuration

Dynamic Variables Polling Map

E4_VAL X

F1_UC X

F1_VAL X

F2_UC X

F2_VAL X

F3_UC X

F3_VAL X

F4_UC X

F4_VAL X

G1_UC X

G1_VAL X

G2_UC X

G2_VAL X

G3_UC X

G3_VAL X

G4_UC X

G4_VAL X

H1_UC X

H1_VAL X

H2_UC X

H2_VAL X

H3_UC X

H3_VAL X

H4_UC X

H4_VAL X

Configuration needed: N means that no additional configuration must be done in order to read/write the VIEW-related parameters. Otherwise, if Y, the corresponding parameters XX_CODE must be set to a proper value in order to tell to HI302 which HART variables are associated with the parameters. This is necessary because the HART 33 command and the HI302 use the stored values at XX_CODE parameters to assembly the HART 33 command. Check the device’s specific documentation to find out the variable codes associated with command 33.

Poling cycle ~ [s]: represents the approximate time that each polling cycle will take for that particular VIEW. This time is evaluated as 1 second per each HART transaction (issued command).

Configuring the HVT Block

The HVT block lists the variables relative to the specific commands of the HART equipment. For its correct operation is necessary that before the specific commands have been configured in the HI302 memory or through HCD/HWPC blocks. Consult the Smar about this options.

The HVT block can be seen as a complement for the HIRT block. It includes all non-mapped variables in the HIRT block. Therefore, it is not necessary to have all of the p arameters configured, except the following:

♦ MODE_BLK: Should be set on AUTO. If it is set on OS, the block operation will stop. When the

block is set on OS, it returns to the initial Identification state. When the block is set on AUTO, the block identification and the update process is repeated if there is a valid TAG in the DEV_TAG_SEL parameter.

♦ DEV_TAG_SEL: This parameter does not need to be configured for t he download. It connects

the HIRT block to the HVT block temporarily, allowing the HVT block to communicate with the HART device. This connection is done through the HART_TAG parameter. If the supe rvisory software has to read the HVT parameters for any device, it should fill the device’s HART_TAG. The HVT block then searches in every HIRT block for a written HART_TAG in order to do an association with it automatically. Then, it identifies the HART device and the specific command configuration to be used, since this configuration is stored in the HI302 flash memory or in any instantiated HCD block. See the chapter about functioning theory for further details.

3.7

HI302 - User’s Manual

HI302-I - Configuring the MAI or AI Blocks

All HI302-I inputs have an input circuit for the 4-20 mA acquisition. So, it is possible to instantiate until 8 AI blocks or 1 multiple analog input block - MAI. These blocks are st andardized and they are registered on Fieldbus F

• AI: to associate the AI block to one of the inputs just c onfigure the CHANNEL parameter with the number of the desired physical input, from 1 to 8.

• MAI: has 8 output parameters that provide the perce ntage value of the analog input. This block needs no configuration to operate, just set up it on AUTO.

See the Function Blocks´ manual for further details about configurations and options for these blocks.

OUNDATION.

HI302-O – Configuring the MAO or AO Blocks

The HI302-O has 8 HART channels in parallel to circuits that control the loop current and the actuators connected to them. The analog outputs can be used through the AO standard bl ocks (until

8) or through 1 MAO block. These blocks are standardized and they are registered on Fieldbus

OUNDATION.

• AO: to associate the AO bloc k to one of the outputs just configure the CHANNEL parameter with the number of the desired output, from 1 to 8.

• MAO: the channel is configured automatically. The input parameter value always has to be written in percentage. Just set up the block on AUTO.

There are other configuration options, for example, the output value in case of failure. See the Function Blocks´ manual for further details about configurations and options for these blocks.

Starting the HI302 Operation

After configuring the block, download it. Upon the download completion, set the HCFG.COMM_ENABLE parameter on ENABLED to enable the configu ration and start the HART communication.

After the download is completed, the configuration should be saved i n the non-volatile memory. Saving is automatic and starts with the download. It will take approximately 20 minutes, according to the configuration size. While the SAVING LED is lit, the HI302 cannot be turned off or reset, otherwise, the configuration will be lost.

If the user has devices whose configuration is already in the HI302 memor y, e.g. Smar devices, go to the chapter about operation and functioning theory. In case the user has to set a specific configuration, see the chapter about advanced configuration, fi rst. For more details about how to configure the HI302, visit our site www.smar.com.

Calibrating the HI302 analog boards

In order to achieve the most accurate operation of the HI 30 2-I or HI302-O, it is im porta nt to calibr ate the analog boards. During the factory tests, a preliminary calibration is done, being sufficient for most applications. However, it may be necessary to perform a new calibration in the field mainly if the operating temperature is extreme. To do so, follow the steps described in the Help of the HCFG.ANALOG_INPUT_TRIM or HCFG.ANALOG_OUTPUT_CAL parameters. See a summary below.

When the calibration is done, it is valid for the pair GLL1193+GLL1205 or GLL1194. If the analog board has been changed for any reason, a new calibration should be done because the calibration data is stored in the base board for that particular analog board (GLL1193).

IMPORTANT

3.8

Basic Configuration

HI302-I Calibration (GLL1205)

To calibrate a GLL1205, the user should use an accurate current source and follow the steps below:

1. Apply a 12 mA current (50% of the 16mA span) to e ach input. The calibration can be done in

only one channel or in all of the 8 channels at once.

2. After stabilizing the current (2 seconds), write the number of the desired channel on the

HCFG.ANALOG_INPUT_TRIM parameter or write All Channels to calibrate all of them at once.

3. Check in the AI/MAI block if the value of the current is 50% (12 mA). If the reading, in any

channel, is incorrect, redo the procedures.

4. If the reading in the 8 channels is 50% (12 mA), write on the HCFG.ANALOG_INPUT_TRIM

parameter the Trimmed and Checked value in order to save the calibration data.

5. Wait until the SAVING Led turns off and then, turn off the device.

HI302-O Calibration (GLL1194)

The user should use an accurate multimeter to calibrate the GLL1194. Follow the steps below:

1. Write 50%/12 mA on all of the input parameters of the AO/MAO block.

2. Measure the current in each loop using the multimeter. Write each read value on the

corresponding element of the HCFG.ANALOG_OUTPUT_CAL[channel] param eter. Write all of the numbers displayed on the multimeter to maximum accuracy (minimum 2 places of decimals).

3. Measure the current again and check if its value has changed, that is, approximately 12 mA.

4. In case the current has changed, write on the HCFG.ANALOG_INPUT_TRIM parameter the

Trimmed and Checked value to save the calibration data.

3.9

HI302 - User’s Manual

3.10

Chapter 4

ADVANCED CONFIGURATION

Specific HART Command Configuration with HCD and HWPC Blocks

The HI302 allows the use of any HART device with a suitable confi guration for reading and writing the necessary variables. As we have seen previously, all of the Universal and some Common Practice commands are available in the HIRT block, therefore no additional configuration is necessary. The whole group of Common Practice and Universal commands depends on extra configurations that can be stored in the HI302 flash memory or in the HCD and HWPC blocks. This chapter contains information about how to create a simple configuration b y using the HCD and the HWPC blocks.

Basic Instructions on HART protocol

HART is a master-slave protocol and is organized around the ISO/OSI 7-layer model for communication protocols (see the table below). The application layer is the topmost layer in the Open Systems Interconnection (OSI) model.

OSI Layer Function HART

Command oriented. Predefined data types and

application procedures.

A binary, byte oriented, Token passing, master/slave protocol.

Simultaneous analog & digital signaling. Normal 4-20 mA copper wiring.

Application

Presentation

Session

Transport

Network

Data Link

Physical

The Application layer in HART defines the commands, responses, data types and status reporting supported by the protocol. In addition, there are certain co nventions in HART (for example how to trim the loop current) that are also considered as part of the Application layer.

Types of HART Commands

The HART Communication Foundation (HCF) arranges the commands into three categories:

• Universal Commands: The Universal Commands must be implemented in the HART devices. These commands have a well-defined format, assuring the interoperability between different systems, for example, some Smar device and a third-party portable configurator. The HIRT block supports all of the Universal commands.

• Common Commands (Common Practice): These commands also have a well-defined structure and syntax. However, it is not mandatory to implement them, tha t is, the user is free t o do it or not according to the device functionality. The configuration of the s tandard commands, used by the HIRT block, implements these commands, for example, the command 33. The device may not support some commands. As a result it is necessary to use the common command filter. See the Appendix B for more details.

Provides the user with network capable applications.

Converts application data between network and local machine formats.

Connection Management Services for applications.

Provides network independent, transparent message transfer

End to end routing of packets. Resolving network addresses.

Establishes data packet structure, framing, error detection, bus arbitration.

Mechanical/electrical connection. Transmits raw bit stream.

4.1

HI302 - User’s Manual

• Specific Commands: These commands allow the user total operation flexibility. Thus, it is possible to know their syntax. To do so, the HI302 has blocks that allow the user to make a configuration to use any accessed variable (reading or writing variable) through the specific commands. See below an example of how to create a configuration.

Describing the HART commands

The structure of the HART command is similar regardless of the category. See below some examples of HART commands and how to create a reading and writing configuration for the variables. For a more detailed explanation, see the device’s manual.

We will use Universal Commands, although any HART command can be described the same way.

IMPORTANT

Get the HART command documentation beforehand, as shown later in this manual. Get these documents from the HART manufacturer.

Since it is a transaction oriented protocol, every HART command has two sections: REQ UEST data and RESPONSE data.

Besides, each section is composed by fields divided into bytes, as you can see in the next table. Each field has a specific size in bytes and a type, such as t he 8-bit integer or a 32-bit number in a floating point. It is important to identify each field type to get the HART command description together.

Setting the definition of the HART Commands

Each HCD block parameter has the definition of one HART command, that is, 50 different commands can be described. This definition has information about the HART Command and about all the elements that compose this command. Each HART op eration, related to a HART command, is composed of two messages: Request, a message from the master to the device, an d Response, the answer for the master’s request. The definition has the following HEXADECIMAL format:

Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8 Byte 9 … Byte N

The first four bytes of the command definition are the header, and they mean:

Byte 1

Byte 2

Byte 3

Byte 4

4.2

Command category. It indicates the command type: Writing (1), reading (0), execution (2) or identification (3) ( 1 byte).

HART Command (1 byte) Extended Command, if existing (2 bytes)

Extended Command, if existing

Figure 4.1 –Syntax for the description of the HART command

The command can have the following values:

 0x00 – READING: command 3 for example.  0x01 – WRITING: command 18 for example.  0x02 – EXECUTION: commands that do not have arguments, neither from the REQUEST nor

the RESPONSE, for example, the command 42.

 0x03 – IDENTIFICATION: the commands used to identify the device, such as 0 or 11. After the definition header, there is the command definition composed of fields with four bytes each

one. Each four byte-field defines a HART variable used in the command sending or received in the answer, as well which block parameter is related to that HA RT variable. In the HCD block , there are definition parameters with 10 and 25 variables. The first 40 parameters only su pport 10 variables, and the remaining 10 parameters support 25 variables.

Byte 1

Byte 2

The data implemented are the following (always with reference to the HART protocol):

Unsigned 8 (converted into unsigned 16) 0x01 0x81

Unsigned24 (converted into unsigned32) 0x03 0x83

IEEE754S, Float Single Precision 0x05 0x85 IEEE754D, Float Double Precision 0x06 0x86 Packed ASCII (converted to ASCII) 0x07 0x87

The first bit of each type defines whether the variable is present in the request or response. For example, an Unsigned 8 used in the request will be 0x01. If used in the response, it will be 0x81.

Configuring the HCD block

Each configuration must receive a code, in order for the configuration to be found, when the HI302 needs to run the HVT block configuration. This code is specific for each HART equipment and should be written in the HCD_CODE parameter. The code is formed by 5 bytes:

 MAN_ID: equipment’s manufacturer ID  DEV_TYPE: device type  UNI_REV: version of the universal HART commands  SPEC_REV: version of the specific command covered by the configuration  SW_REV: resident software version in the HART equipment.

When operating, these 5 bytes are read from the HIRT bl ock in order to find the config uration to be used by the HVT block. Look in the manufacturer’s documentatio n or the reading done by the HIRT block to obtain these values.

The HCD block has the parameter DEVICE_INFO, where the information should be pla ced for the identification of the configuration, such as the device’s name, model, firmware version, etc. This information, as well as the HCD_CODE, is shown in the HVT block when in operation.

Advanced Configuration

Byte 3

Byte 4

Type of data (1 byte)

Length of the STRING or CONSTANT (1 byte)

Extended Command, or CONSTANT if existing (1st byte)

Extended Command, or CONSTANT if existing (2nd byte)

Figure 4.2 –Command definition

Type of Data Request Response

No data 0x00 0x00

Unsigned16 0x02 0x82

Unsigned32 0x04 0x84

ASCII 0x08 0x88

Date 0x09 0x89

Constant 0x0A 0x8A

Coordinate 0x0C -

IMPORTANT

4.3

HI302 - User’s Manual

Figure 4.3 – HCD block configuration

Mapping the HART variable as FOUNDATION Fieldbus parameters

This is the first step. To configure the HCD block, the user should have the HART documentation describing the commands to be used. Using the HART command description, the user should list the HART variables to be accessed, paying attention to th eir type (1 byte, 3 bytes integer, float, packed ASCII, ASCII, etc), length, etc.

HVT Allocation Map and Command Description

It is possible to build a configuration used by the HIRT block. In most situations, it is recommendable to use the standard configuration (5 or 6), since the HCD and HWPC blocks will define specific configurations to be used by the HVT block.

The HVT block has parameters of general use that are arrays with the follo wing type of parameters: Unsigned 8, Unsigned 16, Unsigned 32, Float Single Pre cision and String, with generic names. In order for each of those parameters to have a useful meaning, it is necessary that it is associated to a HART variable. See in the Appendix C, a model of the Allocation map.

Request Parameters

Each Request parameter is described by two types of information: the TYPE (1 byte) and the LENGTH (1 byte), for STRINGS or CONSTANTS, besides the relative index and the sub-index corresponding to the HIRT or HVT block, where the parameter is stored, that is, from which parameter the value will be read to form the HART command. T he parameters are described by their sending sequence in the HART frame. Even if the parameter is from a different t ype, the HI302 converts automatically. Remember that the DATA TYPE should always appear in the documentation of the HART command and not in the parameter type of the FOUNDATION fieldbus block. The parameters are described in order in the HART frame.

Response Parameters

The Response parameters are described the same way as the Request parameters, immediately after.  The most significant bit should be “one” in the RESPONSE DATA TYPE field. The remaining bits indicate the data type that have to be sent via HART command as seen previously. T he data type indicated is the data type that will be “packaged” in HART frame and is not the type of F

OUNDATION fieldbus parameter because it will be conver ted before the HART frame is arranged.

There is an implicit conversion for reading and storage data.

4.4

 When the type of data is Packed ASCII, ASCII or Constant the definition will have a second byte (string length) that will indicate the string length that must be read and saved in characters, or the size of the constant, which can be 1 or 2 bytes.

What about the RESPONSE CODE?

The HI302 has to read the RESPONSE CODE for each transaction concluded successfull y and to update the corresponding parameters (COMM_ERR, RESP_CODE, DEVICE ST ATUS, parameters ’ status DS-65, etc.). The HI302 does not treat the parameters value; it has to be done onl y by the application which is accessing the block at that moment, because each manufacturer can impose a different meaning. So does not worry about the configuration for the response code, for the HI302 reads both bytes automatically.

The mapping and the estimated configuration can be done as it follows:

Advanced Configuration

4.5

HI302 - User’s Manual

4.6

Advanced Configuration

4.7

Command 0

Command 0: universal identifier using the polling address. Request Data

Byte Format Description

None

Response Data

Byte Format Description

0 Unsigned-8 “254” 1 Enum Manufacturer’s ID code. 2 Enum Instrument type.

3 Unsigned-8

Minimum preambles number required by the Master to the Slave. This number includes both preambles used in Asynchronous

Physical Layers (according to the Limit) to detect the beginning of the message. 4 Unsigned-8 Number of the main Review of the Universal Command implemented by the device. 5 Unsigned-8 Review Level of the device. 6 Unsigned-8 Review Level of the device’s software. Levels 254 and 255 are reserved.

Header

Category of the HART Command HART Command Extended Command 1 Extended Command 2

0x00 0x00 0x00 0x00

• The command 0 is originally an IDENTIFICATION command, not a READING command, used only as an example. Since there are no vari ables to be sent on the Request, we will go directly to the Response.

HART Variable Type

HVT Parameter Type Code Length Index Subindex

Constant “254” Unsigned8

Discarded Constant 0x8A 0x00 0x00 0x00

Manufacturer’s ID code. Enum

U8B_ARRAY_1[1] Unsigned8 0x81 0x00 0x0B 0x01

Device’s Type Code. Enum

U8B_ARRAY_1[2] Unsigned8 0x81 0x00 0x0B 0x02

Minimum number of Preambles. Unsigned8

U8B_ARRAY_1[3] Unsigned8 0x81 0x00 0x0B 0x03

Review of the Universal Commands. Unsigned8

U8B_ARRAY_1[4] Unsigned8 0x81 0x00 0x0B 0x04

Device Review. Unsigned8

U8B_ARRAY_1[5] Unsigned8 0x81 0x00 0x0B 0x05

Software Review of the Device. Unsigned8

U8B_ARRAY_1[6] Unsigned8 0x81 0x00 0x0B 0x06

• The first byte received on the response of the command 0 will always be t he constant 254, so it does not need to be mapped to any parameter and will be discarded when the response is processed, so the INDEX RELATIVE will receive the value 0.

• Even if the command has other variables in the sequence, the HI302 only processes the described varia bles. Suppose only the sixth variable is of interest. It is necessary to describe the first five, discarding the values until the sixth. The following variables don’t need description.

Value that should be written in the CMD_00 (Relative Index 11 - 0x0B) parameter of the HCD block:

00 00 00 00 8A 00 00 00 81 00 0B 01 81 00 0B 02 81 00 0B 03 81 00 0B 04 81 00 0B 05 81 00 0B 06

HI302 - User’s Manual

4.8

Command 3

Command 3: reads the loop current and four manufacturer’s pre-defined dynamic variables. Request data

Byte Format Description

None

Response Data

Byte Format Description

0-3 Float Loop Current of the Main Variable (milliamperes) 4 Enum Main Variable Unit Code 5-8 Float Main Variable 9 Enum Secondary Variable Unit Code 10-13 Float Secondary Variable 14 Enum Tertiary Variable Unit Code 15-18 Float Tertiary Variable 19 Enum Quaternary Variable Unit Code 20-23 Float Quaternary Variable

Header

Category of the HART Command HART Command Extended Command 1 Extended Command 2

0x00 0x03 0x00 0x00

• This command does not have variables to be sent with the Request. So, we will go straight to the Response.

HART Variable Type

HVT Parameter Type Code Length Index Sub-index

Loop Current of the Main Variable (mA) Float

FLOAT_ARRAY_1[1] Float 0x85 0x00 0x10 0x01

Main Variable Unit Code Enum

U8B_ARRAY_1[7] Unsigned8 0x81 0x00 0x0B 0x07

Main Variable Float

FLOAT_ARRAY_1[2] Float 0x85 0x00 0x10 0x02

Secondary Variable Unit Code Enum

U8B_ARRAY_1[8] Unsigned8 0x81 0x00 0x0B 0x08

Secondary Variable Float

FLOAT_ARRAY_1[3] Float 0x85 0x00 0x10 0x03

Tertiary Variable Unit Code Enum

U8B_ARRAY_1[9] Unsigned8 0x81 0x00 0x0B 0x09

Tertiary Variable Float

FLOAT_ARRAY_1[4] Float 0x85 0x00 0x10 0x04

Quaternary Variable Unit Code Enum

U8B_ARRAY_1[10] Unsigned8 0x81 0x00 0x0B 0x0A

Quaternary Variable Float

FLOAT_ARRAY_1[5] Float 0x85 0x00 0x10 0x05

• Observe that the Unsigned8 parameters are following thos e used to ma p the variables of the 0 comm and. T hat is not necess ary. Any parameters o f

the U8B_ARRAY_X can be used.

Value that has to be written in the parameter CMD_01 (Index Relative 12 - 0x0C) from the HCD block:

00 03 00 00 85 00 10 01 81 00 0B 07 85 00 10 02 81 00 0B 08 85 00 10 03 81 00 0B 09 85 00 10 04 81 00 0B 0A 85 00 10 05

Advanced Configuration

4.9

Command 13

Command 13: reads the TAG, Descriptor and Date. Request Data

Byte Format Description

None

Response Data

Byte Format Description

0-5 Packed Tag 6-17 Packed Descriptor 18-20 Unsigned-24 Data Code

Header

Category of the HART Command

HART Command Extended Command 1 Extended Command 2

0x00 0x0D 0x00 0x00

• The command 13 reads the TAG variables, Descriptor and Date. The command 18 (described in the next section), writes these variables in the

device. It is important to first describe the reading command and execute the reading before the writing i n order to avoi d that the par a meters need to be initialized by the application before writing in one variable. For exa mple, writing the tag without reading or initialization the Descriptor and the Date would receive the value of the block parameter, which can be read from another device or even trash.

HART Variable Type

HVT Parameter Type Code Length Index Subindex

TAG Packed ASCII

String_01 String 0x87 0x06 0x18 0x00

Descriptor Packed ASCII

String_06 String 0x87 0x0C 0x1D 0x00

Date Unsigned24

Descarted Unsigned32 0x89 0x00 0x16 0x01

• Note that in this description the DATE type is mapped to an Unsigned32. Value that should be written in the CMD_02 (Index Relative 13 - 0x0D) parameter from the HCD block:

00 0D 00 00 87 06 18 00 87 0C 1D 00 89 00 16 01

HI302 - User’s Manual

4.10

Command 18

omando 18: writes the TAG, Descriptor and Data Request Data

Byte Format Description

0-5 Packed Tag 6-17 Packed Descriptor used by the Master for a Register.

18-20 Unsigned-24

Date Code used by the Master for Register (for example, last or

next calibration date).

Response Data

Byte Format Description

0-5 Packed Tag 6-17 Packed Descriptor 18-20 Unsigned-24 Date Code

Note: The values from the response data reflect the real values used by the field devices. Note: Most devices only store the date, and some field devices may not detect an invalid date code.

Header

Category of the HART

Command

HART Command Extended Command 1 Extended Command 2

0x01 0x12 0x00 0x00

• The command 18 has variables which sh ould be sent on Request. The request variables should be defined first, and then, the response variables. Observe that the Bit7 for the Request variables type is "0", while the Response variables has this bit equal to "1".

HART

Variable

Type

HVT Parameter Type Code Length Index Sub-index

TAG Packed ASCII

String_01 String 0x07 0x06 0x18 0x00

Descriptor Packed ASCII

String_06 String 0x07 0x0C 0x1D 0x00

Date Unsigned24

Discarded Unsigned32 0x09 0x00 0x16 0x01

TAG Packed ASCII

String_01 String 0x87 0x06 0x18 0x00

Descriptor Packed ASCII

String_06 String 0x87 0x0C 0x1D 0x00

Date Unsigned24

Discarded Unsigned32 0x89 0x00 0x16 0x01

IMPORTANT: Besides the command description, it is necessary to create a complementary confi guration on the HWPC block so that the HI302 may write on the mapped parameters. Without the HWPC configuration, the variables may only be read.

Value that should be read in the parameter CMD_03 (Index Relative 14 - 0x0E) from the HCD block:

01 12 00 00 07 06 18 00 07 0C 1D 00 09 00 16 01 87 06 18 00 87 0C 1D 00 89 00 16 01

What about the parameter writing?

The HART variables that can be written on the device need special attenti on. Besides the comma nd definition used for reading and/or writing, is needed information about how this variable rel ates with the block parameter where it has been mapped and with the HART writing command. This information is stored in the HWPC block.

Setting the HWPC block Configuration

The HWPC block completes the configuration done in the HCD block. For each HCD block with parameters that can be written, it is necessary to have a corresponding HWPC block with the same code in the definition library HCD_CODE. This value should be written in the HWPC_CODE parameter.

The HWPC block parameters are 20-position string. Eac h string allows 4 writing parameters, and each parameter has 5 bytes. This parameter should have information about HART commands th at are used to write and read the corresponding parameters in the HVT and HI RT blocks. The HWPC block has 30 parameters of this type, allowing the writing in 30 different HART variables. The HWPC has the following structure:

1. The parameter location in the block.

<Byte1>: Parameter relative index in the block. <Byte2>: Parameter Sub-index. In case of simple parameters it always must be null.

2. Parameter Writing Command

<Byte3>: Parameter relative index of the HCD block that defines the command used t o write in the HART device. <Byte4>: Relative position of the HART variable in the HCD block parameter.

3. Parameter Reading Command

<Byte5>: Parameter relative index of the HCD block that defines the command used for this parameter reading, for a reading that confirms if the writing was done with success.

If the parameter is written and there is no corresponding configuration in the HWPC block, no HART command will be generated to change the variable in th e device, even if there is a writing command in the HCD block.

Configuration of the HWPC for the given example

See an example about a configuration for a writing operation for the following HVT parameters:

HVT Parameter Relative

String_01 24 TAG 14 13 String_06 29 Descriptor 14 13

With this information, just transpose these data for one of the HWPC parameters, as in the figur e below:

Index

IMPORTANT

Mapped HART

variable

Advanced Configuration

Written HCD

Index

Written HCD

Index

4.11

HI302 - User’s Manual

Figure 4.4 – HWPC Configuration

4.12

Chapter 5

Initialization

LEDs Status

OPERATION

An introduction on the module firmware, its overall performance, signal LEDs status and work in steady state is presented below. See the parameter HCFG.FIRMWARE_VERSION to know the firmware version.

When initialized, the resident program performs a checkup o n the module for its perfect working condition:

• The hardware’s condition, access to memories, access to UARTs, and analog board’s condition;

• Start up on the fieldbus communication;

• Search for a valid block configuration in the memory. If found, the HART communication is started.

After this stage, the front LEDs reflects the result of the initialization and the self-diagnostic.

LED ON

This LED must remain lit, indicating that the module is supplied and that the HOT SWAP circuit is working normally. If this LED is off and the outside supplying is normal, it indicates that there is some problem with the HOT SWAP circuit, or that the short-circuit protection is working. T urn off the module immediately, restart it a few minutes later and if the problem continues, send the device to maintenance.

LED FAIL

This LED has two statuses:

• OFF: there is no error to be reported, the minimum configurati on has been set, correctly saved on the EEPROM and the HI302 should operate well.

• Blinking: the HI302 has not received the minimum configuration to operate. Send the minimum configuration via Syscon. Another reason is any fatal error th at stops the HI302 operatio n. Turn it off and after a few seconds, restart it. If the problem persists, press the “FCT INIT” button. If these procedures were not effective, send the device to maintenance.

Figure 5. 1 – HI302’s Frontal

5.1

HI302 - User’s Manual

LED SAVING

The HI302 module has a serial EEPROM to store non-volatile data from it s configuration. However, to avoid the premature wear off of the memory, a mirror of its contents in SRAM is used. While this LED remains lit, avoid the HI302 to be switched off or reset, as this will indicate that static data from the SRAM mirror is being saved on the EEPROM.

After sending the configuration to the HI302, this LED may be lit for a f ew minutes while data is being saved permanently on the EEPROM. If it is turned of f or reset, this configuration will be lost, and must be sent again.

H1 LED

This LED indicates that an activity is going on in the fieldbus communication. At each information package sent by the HI302, the LED will blink. If the LED does not blink, it i ndic ates that the HI302 is not communicating with the net. Check the H1 segment configuration (LAS). Then switch off the HI302 and restart it a few seconds later. If it does not return to the “Live L ist” after a few minutes, try a “Fct Init”. If this step fails, send the HI302 to maintenance.

CH#1 to CH#8 LEDs

These LEDs indicate the situation on every HART channel, under the following statuses:

• Unlit: the channel is active but there is no HART communication. The devices of the channe l may have problems or their HIRT blocks are in OS (Out of service) mode. Check the devices and their block configurations.

• Lit: indicates the HART communication is deactivated (the COMM_ENABLE parameter in the HCFG block is DISABLE). This may happen in two situations:

• Blinking regularly and fast (2Hz): indicates that the HI302 has not yet received the minimum configuration, that is, the HCFG block has not been found. Re-download the configur ation or press the Fct Init button to correct the problem.

• Blinking regularly and slow (1/4 Hz): the channel is deactivated because there is no instantiated HIRT block using it. This information is useful to check if there h as been a mistake in the configuration of the HIRT blocks. Check each HART channel configuration on the HIRT blocks.

• Blinking irregularly: In this status the LED blinks according to the HART rate of messages exchanged in the channel. If it remains unlit for long time, means the device may have problems or the configuration may be wrong. See the BLOCK_ERR and BLK_EXEC_STATE parameter of each HIRT block.

After the BLK_EXEC_STATE of the HIRT block is set to UPDAT ED, the HART communication is ended if the polling is disabled on the HIRT block. Consequently, the LED will be off, if there is no other HIRT block using the channel.

Auxiliary Push Buttons

There are 2 auxiliary push buttons inside the front panel, on the topside, just above the conn ectors. The RESET button at left is used to reset and to put the equipment in the Bootloader mode in order to update its firmware. The second push button, located at the right side, Fct Init, is used t o initialize the memory to its factory state. This second button must be carefully used.

ATTENTION

• “On line” configuration changing of channels or devices;

• Creation or exclusion of blocks.

ATTENTION

5.2

Operation

Figure 5. 2 – Auxiliary push buttons

Understanding the HART Communication

To follow the communication operations performed by the HI302, the user should understand the diagnostic parameters from the HIRT block.

BLK_EXEC_STATE parameter

The BLK_EXEC_STATE exist on HIRT, HUT and HVT blocks, and may assume the following values:

• 0x00: IDENTIFICATION, means the HART device is under an identification process, the block communication is stopped (MODE_BLK = OOS) or HCFG.COMM_ENABLE is DISABLE.

• 0x01: OLD DATA, only valid for HIRT and HUT blocks. It means the block has detected a HART device alteration. It sends the command HART 38 to reset the configuration changed flag in the device. If the HI302 has sent the writing request, the block goes straight to UPDATED. If the writing comes from an external source, the IDENTIFICATION and UPDATING processes restarts to guarantee that all block parameters have the most recent values of HART device. After this sequence, the ST_REV parameter is always increased.

The HI302 uses the CONFIGURATION_CHANGED bit (bit 6 of the second byte of the RESPONSE CODE, HART standard) to detect changings in the field device. If the HART device does not set this bit immediately when a configuration chan ging is done, the HI302 ca nnot detect automatically the changing. Thus, if the HI302 is not detecting automatically the configuration changings of the HART device verify if the device is setting this bit. This verificati on can be done with a HART communication monitor.

• 0X02: UPDATING, the block HIRT/HUT is being updated with the HART device’s data. The HART commands are being sent and the information is not yet valid for readi ng. The supervisory software should wait block this process may take a few minutes since it depends on how many HART commands ar e sent to the equipment. For instance, if 60 commands are sent (in the F Y301), interspersed with the HIRT block polling commands the time will be ap proximately 2 minutes. See the Appendix B for further details about the HART commands that was sent during the updating.

• 0X03: UPDATED, if the commands were sent successfully, the block assumes this status. To ensure that the polling and the automatic update work properly, the bl ock should be at th is status. If the block is at another status, check the device configuration, the HART commands us ed, etc. Once the parameters reached UPDATED, all the data is available for reading and writing.

• 0X04: PARTIALLY UPDATED, if the block is at this status, one or more transactions were not don e successfully during the UPDATING process. Make sure the device supports all of the commands sent by HIRT block, otherwise, filter the not supported commands in the COMMON_CMD_FILTER.

• 0X05: NOT RESPONDING, the device does not respond anymore, even performing all retries.

• 0X06: BYPASS, the block has no valid information because the communication is in BYPASS mode

(see COMM_BEHAVIOR in the HCFG block).

• 0X07: DEVICE NOT FOUND, it is only valid for HIRT blocks. During the identification process, the device was not found by the command selected in the ID_CMD parameter.

until the block becomes the BLK_EXEC_STAT E parameter UPDATED. With the HVT

IMPORTANT

5.3

HI302 - User’s Manual

• 0X08: HCD ERROR, maybe there is some configuration error. If it is the HVT block, the user has to verify which HART tag is written in the HVT.DEV_TAG_SEL par ameter. With this tag, the user has to find the HIRT block which has the same tag to obtain more information about this error. If it is the HIRT block, this error may have two causes: error in the HART commands configur ation that are resident in the HI302 or the HART device may be not responding correctly to some com mand of the HI302 configuration.

• 0X09: TAG NOT FOUND, it is only valid for HVT blocks. It indicates that no HIRT block was found for the HART_TAG from the HVT.DEV_TAG_SEL parameter.

• 0X0A: WRITING, the block accepted the recording request and has started the transaction. Set it on OLD DATA and, then change to UPDATE.

BLK_ERROR and DEVICE_STATUS Parameters

The BLOCK_ERR is a parameter of fundamental importan ce for problem dia gnosis b oth in the block operation and the associated HART device. For the HIRT and HVT blocks, according to the last transaction status with the device, the BLOCK_ERR may display the following messages:

STATUS HART bit DEVICE_STATUS parameter BLOCK_ERR parameter

2 Loop Current Saturated Other 3 Loop Current Fixed Local Override 1 Non-Primary Variable Out of Limits Device Needs Maintenance Soon 0 Primary Variable Out of Limits Process variable has BAD status 7 Device Malfunction Device Nee ds Mainte nance Now

Not all bits on the BLOCK_ERR parameter are associated with the HART device failure conditions and associated with the DEVICE_STATUS. Note the following:

• OutOfService: When the block is in OS mode, the BLOCK_ERR will present this bit already set, regardless of the last device or block operating condition.

• ConfigurationError: Indicates that there’s possibly a problem in the configuration or in the HART commands of the HCD block selected on the HCD_SEL parameter. Check this parameter.

• ReadBackFailed: Indicates that the device stopped responding.

HIRT block Operation

Once the configuration is stored in the HI302, the user should write ENABLED in the COMM_ENABLE parameter of the HCFG block in order to operate it. When the communication is enabled, the HI302 performs the following operations:

1. BLK_EXEC_STATE = IDENTIFICATION. Initial block state. From this state the block uses the command configured in the ID_CMD parameter to start the communication with the HART device. If after some RETRIES, the device does not respond, the BLK_EXEC_STATE parameter goes to DEVICE NOT FOUND. Check the block configuration, the device channel, polling address, the TAG, the HART device, etc. .

2. DEVICE_IDENTIFIED = TRUE and BLK_EXEC_STATE = UPDATING. After the initial identification, the basic data are read. The i dentification and the re ading process last approximatel y 10 seconds per device. Remember that, the 8 channels work normally in parall el; therefore, these initial processes last approximately 40 seconds for the 3 2 devices (4 devices per channel). See in the Appendix B, a list of all of the commands sent in this stage. During the UPDATING process, only the reading commands are sent.

3. BLK_EXEC_STATE = UPDATED. Once the data have been identified and updated successfully,

the BLK_EXEC_STATE parameter goes to UPDATED, allowing access to the HIRT parameters Thus, all devices are polled, the dynamic variable values and the device status are up dated, if the HIRT.POLL_CTRL parameter is Enabled. The update frequency depends on the amou nt of HART devices in the channel and the number of HART commands sent on each polling cycle.

5.4

The POLL_CTRL parameter should be set on Enabled to allo w for the HI302 to poll the device. In addition to updating the dynamic variables, the polling also updates the parameters that d epend on the RESPONSE_CODE parameter, for example, DS-65 and DEVICE_STATUS. The polling is very important to detect device configuration changes don e by ot her masters lik e portabl e conf igurators, so, the HI302 can automatically update the data.

4. If any error occurs duri ng the updating process, the block should go to PARTIALLY UPDATED.

See some reasons below:

• The HART device does not support one of the sent commands. Check the commands using the device documentation (see the Appendixes). Since “Common Practice” commands are used, the user should filter them by using the COMMON_CMD_FILT ER parameter.

• There was an error during the communication. Check the HCFG diagnostic parameter to help you to solve the communication problem.

• Set the block on OS and then, change it to AUTO for identification.

5. If the block is set on UPDAT ED, the user can associate the HIRT block with HVT block to read any device variable, since the HI302 supports the suitable specific commands configuration.

6. In normal operation, the alteration flag, located in the Response Code, is checked at each transaction. If this flag is set, the HI302 starts a reading sequence on the parameter of the HIRT block, that is, the BLK_EXEC_STATE parameter goes to IDENTIFICATION. The HVT block does not update automatically and its ST_REV parameter has no useful meaning. At the end of the reading process, the block should be updated and reflecting the device’s data. So, the ST_REV parameter of the corresponding HIRT block is increased and will indicate that a parameter was changed.

HART Variable Writing and Reading

An operation model, based on reading cycles and writing requests, was designed to make the HI302 use as simple as possible.

HART variables Reading Cycles

The variable reading is almost always done in-group because of the HART command structure. Therefore, the HI302 variable readings are done through cycles, that is, the HIRT block always updates several parameters at the same time (except the writing). When the HVT block is executed, all of the reading commands from the device configuration are execut ed at the same time, following the configuration sequence. See the Appendixes.

When the HIRT block detects any change in the device (BLK_EXEC_ST ATE=OLD DATA), it starts an update process and sends again all the reading par ameters of the configuration. The app licative checks if the ST_REV was changed and begins to execute the HVT block for the device.

Writing on parameters that map the HART variables

Unlike the reading, writing on parameters that map HART variables is done separately for each variable.

Not all parameters related to HART variables allow writing. Writing d epends on the device’s HART version. If the user has any doubt about writing on parameters, check the HIRT block documentation as well as the HART commands supported by the device.

Operation

IMPORTANT

5.5

HI302 - User’s Manual

Since some HART commands have variables for writing, the command will be composed of the parameter to be changed and the parameters de scribed in the command defin ition (HCD block). As the parameter does not inform which HART command should be used to write (The writing and reading parameters many times are not the same), it is necessar y an addition al configurat ion for the parameters to be written. Such additional configuration is done in the HWPC block because it has the correlation between these parameters and the HART commands used for writing. T he HWPC has the same identification code as the corresponding HCD, therefore, the entire configur ation for a HART device should have a HCD + HWPC pair. A writing request starts a process with the following stages:

1. After the parameter had received the writing command, the HI302 checks the HWPC block to know whether that parameter can be written, that is, if it has a configuration to write. If the parameter has such a configuration, the HI302 stores the value received in a temporary variable and starts the writing process in the device. If the parameter does not have this configuration, the HI302 returns a standard response indicating that the param eter cannot be written.

IMPORTANT

In case the parameter does not accept writing, check if the HI302 supports the specific commands of the HART device and if the HWPC configuration is correct.

2. If the parameter can be written, the writing request is started, waiting for the next transaction with

the device. The writing request has priority over HART transactions since the block is set on UPDATED. The block status, in this case, goes to WRITING.

3. As soon as possible, the writing command will be set according to the definition in the

corresponding HCD block and will be sent to the device.

IMPORTANT

Despite the fact that the HI302 has responded and the writing was successful, the value read on the parameter continues to be the old one. The parameter will only be updated after the writing confirmation in the HART device.

4. In case the device does not respond, there will be attempts according to the schedule in the HCFG.RETRIES[CHANNEL] parameter. If there is any message saying th at the writing was not performed, the HI302 will ignore the writing request. Even though the device does not re spond to the writing command, the HIRT block will always return to UPDATE.

5. If the writing command response is positive, the block parameter is updated with the new value written in the device. Then, the monitoring will read the new valu e and finis h the writing process successfully. The block status will go to OLD DATA and then, to UPDATED. Then, the ST_REV will be incremented.

6. Note that the time for a writing request can vary a lot:

• If the channel is free and th e writing request was immediately processed, the transaction will last approximately 3 s, if there is no communication error due to the time to send the writing command, read the value and send the command to reset the device’s alteration flag.

• If the channel is busy, the request will wait until the next time to be transmitted. A long timeout is needed, if the transaction that is using the cha nnel has several retries and ea ch retry has many repetitions. So, the user should monitor the BLK_EXEC_STATE parameter.

IMPORTANT

This procedure indicates that the user’s application should monitor the BLK_EXEC_STATE parameter. This parameter changes to WRITING, then to OLD DATA and finally it goes to UPDATED provided the writing was done successfully. At the same time, the parameter value (after the block has returned to UPDATED) should be compared to the written value. So, the operation will be confirmed or not, after a predefined timeout in according to the application.

5.6

Operating the HVT Block

The HVT block is an extension of the HIRT block, because it makes it p ossible to access all of the variables related to common or specific commands. After identifying the devices, the HART variables that are not in the HIRT block may be accessed. To do this, the user must know the allocation map on the HVT block that connects the HART variables on the device with the block parameters, whose names are generic ones. The devices can be fully defined using the HIRT+HVT blocks.

Operation

Figure 5. 3 – Device definition using HIRT + HVT blocks

See below an example of a HVT allocation map for Smar FY301 intelligent positioner:

Index Parameter Name HART Variable Name HART Command Description

11.1 U8B_ARRAY_1[1] EEPROM_CONTROL 39

11.2 U8B_ARRAY_1[2] DISPLAY_CONNECTED 128 Indicates if the display is connected or not

11.3 U8B_ARRAY_1[3] AIR_TO 128,129

11.4 U8B_ARRAY_1[4] LOCAL_KEYS_MODE_CTL 132 Indicates if the local adjustment is enable or not

11.5 U8B_ARRAY_1[5] COORD_GROUP_NUMBER 133

13.14 U8B_ARRAY_3[14] MANIPULATE_VARIABLE_UNIT 216 MV unit

13.15 U8B_ARRAY_3[15] SETPOINT_TRACKING 216 Not available in FY301

13.16 U8B_ARRAY_3[16] SERVO_PID_MODE 216 Indicates if the servo-PID is enable or disable

16.7 FLOAT_ARRAY_1[7] PRESSURE_LOW_LIMIT 244,245 Lower pressure limit for the input sensor

16.8 FLOAT_ARRAY_1[8] POS_VALVE 168 Valve position

16.9 FLOAT_ARRAY_1[9] TRAVEL_DEADBAND 189,190 Travel deadband value

16.10 FLOAT_ARRAY_1[10] TRAVEL_LIMIT 189,190 29 String_06 ACTUATOR_ID_NUMBER 183,184 Actuator identification number

30 String_07 VALVE_ID_NUMBER 185,186 Valve identification number 34 String_11 ORDERING_CODE 173,174 Factory device information

Saves data from RAM to EEPROM or recover data from EEPROM to RAM

Indicates if the valve needs air to open or to close

Select one coordinate to be read from the characterization curve

It is the maximum distance covered by the valve before an alarm is generated

This way, if the user wants to read the AIR_TO variable, he must read the U8B_ARRAY_1[3] parameter. As there is only a single HVT block shared by all of the devices , it use must be triggered, that is, one must choose first the device that will use the HVT block, and then shoot the reading cycle or a writing operation.

Sequence for HVT Reading Cycle

After defining, executing and loading all of the configurations in the HI302, it is now possible to communicate with the devices using the HVT block. The respective HIRT block sho uld have alre ady been identified.

5.7

HI302 - User’s Manual

The HVT block operation is very simple and its use must comply with the following rules:

1. The user’s application must check if the block is available by reading the BLK_EXEC_ST ATE parameter. If the parameter is set on UPDATING, the block is in operation and cannot be used for a new transaction.

2. Write on the DEV_TAG_SEL parameter the 8-character TAG of the HART device that one wishes to access. It must be the same as on the HIRT.HART_TAG parameter;

3. If there is one, the HVT block checks if the written TAG belongs to a HIRT block that corresponds to a device installed in one HI302’s channel. If the TAG was not found, the status will be TAG NOT FOUND and the process will be aborted.

4. After writing on the HART_TAG, the HVT block automatically checks if the specific command configuration is in the memory. Otherwise, the block goes to HCD ERROR.

5. If the HCD block and the HART _TAG were found, the parameter goes to UPDATING and the communication process with the HART device begins. Thus, all of the reading commands will be sent according to the sequence in the configuration.

6. If the device does not respond at the first command, the BLK_EXEC_STATE parameter changes to NOT RESPONDING.

7. If the devic e responds at the first comman d, the status will continue on UPDATING until the las t reading command is sent. If there is an error during the communication, t he BLK_EXEC_STATE will report it and the process will not stop until the last command is sent. The block status will be PARTIALLY UPDATED and the user should identif y the problem, which may be a command configuration error or a non-compatible version.

8. In case the process finishes with no error, the block status will be UPDATED. Thus, the applicative can read all of the block’s parameters accordi ng to the allocation map and execute writing operations as well.

Writing Sequence in HVT Block Parameter

In order to write in a HART variable that is mapped as the HVT block parameter, the user should first perform an updating, that is, a comprehensive reading operation. When the HVT block is UPDATED, follow the same procedure used for writing on HIRT blocks.

IMPORTANT

All the HVT parameters accept reading and writing. However, only the parameters that have writing configuration will generate a HART transaction. The device should support the command configured, even if the HI302 has started a writing transaction. So, if any writing error occurs, check the HVT allocation map (Appendix C) to make sure that the parameter is mapped for a HART variable that can be written.

5.8

Operation

Figure 5. 4 – Writing in HVT block parameters

HI302 versus Portable Programmers (Field Alterations)

The HI302 monitors every device that is working normally in a continuous way and whose HIRT block is in UPDATED with POLL_CTRL=ENABLED. Each HART master channel, when configured as primary by the HCFG.MASTER_TYPE [CHANNEL], permits the simultaneous use of a portable programmer, for example, the Smar HPC401. If some alteration happens on the device, it will report this to the HI302 in its next transaction, through the specific bit in the RE SPONSE CODE. Then the HI302 will take the following actions:

• Will set the block status on OLD DATA (BLK_EXEC_STATE), indicating that the actual data are not valid for reading;

• Will send the HART command 38 to reset the flag that indicates that th e device’s configuration was changed.

• Will start reading all of the parameters on t he HIRT block. After doing this, the HI302 changes to the UPDATED status and will increment the corresponding HIRT.ST_REV, indicating on the user’s applicative that the data must be read again, possibly with the H VT execution for this device.

STATIC REVISION (ST_REV) Parameter

Usually, the ST_REV is only increased if a parameter classified as STATIC, is chan ged. Therefore, the HIRT and HVT blocks do not work that way. Other than the static parameters, any other parameter that maps the HART variable will incr ease the ST_REV of the corresponding HIRT and HVT blocks.

While the HVT parameter is being written occurs the following:  If the writing is accepted, a HART transaction is generated, making t he HART device indicate

the change through the RESPONSE CODE. The parameter ST_REV from the HIRT block associated to the HVT block, and also that parameter of the HVT block will be increased.

 If Polling is en abled, the HIRT block associ ated to the HART device will notice this change and

will automatically be set to OLD DATA, sending the command 38.

 After the command is sent, the HIRT block will start updating the parameters, being set to

IDENTIFICATION and UPDATING. During the UPDATING process, the ST_REV from the HIRT block will be increased indicating that the data were updated and should be read again.

5.9

HI302 - User’s Manual

IMPORTANT

The polling commands do not increase the block’s ST_REV.

Conclusions on the STATIC REVISION:

1. The client application should only monitor the parameters ST_REV from the HIRT blocks, ignoring the ST_REV from the HVT block.

2. If the application writes on the HVT block, it may ignore the increment done on the HVT block ST_REV, as well as the corresponding HIRT block increment.

3. If there is no writing on the HIRT block and the ST_REV was changed, the device information was updated and a new reading should be done in the HIRT and HVT blocks.

HART RESPONSE CODE Conversion to STATUS FOUNDATION Fieldbus

The RESPONSE CODE of the last transaction with HART devices is mapped to the DEVICE_STATUS and COMM_ERR parameters of the HIRT block. In order to use the information about the device’s general status, the DEVICE_STATUS is converted into a corresponding ST AT US FOUNDATION fieldbus to feed the parameters that have STATUS. For example, the PV_MA can be separated into PV_MA.STATUS and PV_MA.VALUE. The PV_MA.STATUS represents the actual condition in which the device provides the PV_MA.VALUE parameter. See the next table:

STATUS HART bit DEVICE_STATUS parameter Status FOUNDATION Fieldbus converted

7 Device Malfunction Bad:DeviceFailure:NotLimited 0 Primary Variable Out of Limits Bad:UncertainNonSpecific:iNotLimited 2 Loop Current Saturated Uncertain:SensorConvNotAccurate:NotLimited 1 Non-Primary Variable Out of Limits Uncertain:Subnormal:NotLimited 3 Loop Current Fixed GoodNonCascade:GoodNCNonSpecific:Constant

• If the block is set at OS, all the parameter will assume the Bad:OutOfService:NotLimited status.

• If the device stops the communication and the block status goes to NOT RESPONDING, all the

status go to Bad:NotConnected:NotLimited.

• If there is no error or alert condition to be informed, the status will assume the following status: GoodNonCascade:GoodNCNonSpecific:NotLimited.

BYPASS Mode

The BYPASS mode using the HBC block was created to allow the HART messages to be sent to any device, through simple writing on a parameter called BYPASS_REQ_N (N is the channel number, from 1 to 8). The written content on the parameter is entirely sent to the channel configured on the HIRT block, as soon as the channel is free. Thus, the application must include in the message the preambles, the delimiter and so on. Only the RESOURCE, HBC and the HCFG blocks are necessary to operate the BYPASS mode. Any HIRT or HVT block instantiated will stay on BYPASS status (BLK_EXEC_STATE parameter) with no function.

IMPORTANT

To use the BYPASS mode, the user should write BYPASS on the HCFG.COMM_BEHAVIOR parameter.

The HCFG.BYPASS_STATUS indicates the situation of the message and may assume the following values:

• IDLE, the channel may send a message using the BYPASS_REQ_N parameter or there is a

message available to be read through the BYPASS_RES_N parameter. Even though, the channel is monitoring another master’s communication or a device in burst mode, it will be available to send a message as soon as is possible.

• BUSY, the application ordered a REQUEST that is being executing,

5.10

Example

Operation

• TIMEOUT, after a predefined number of repetitions, it was not possible to receive a valid

message for the request.

• RESPONSE AVAILABLE, after the programmed number of repeats, it was not possible to

receive a valid response for the sent request.

The HI302 does not perform any integrity or cont ent checkup on the message received. It transmits what it has received to the communication channel . The applicative must ensure the quality of the messages and the response interpretation.

Sequence for Sending a HART message through a BYPASS

• Check if the HCFG.BYPASS_STATUS [N] parameter is on IDLE, TIMEOUT or RESPONSE AVAILABLE. If positive, the message can be written on the HCFG.BYPASS_REQ_N parameter. The HI302 will check if the channel is available and transmit the content of the HCFG.BYPASS_REQ_N parameter.

• While the HCFG.BYPASS_STATUS [N] parameter is on BUSY, the HI302 is waiting the response or repeating the request up to the limit programmed in the HCFG.RETRIES [N].

• T he HCFG.BYPASS_STATUS [N] parameter goes to IDLE if it has received a valid message. It goes to TIMEOUT; in case it has not received a valid response yet.

IMPORTANT

As the message has to be entirely supplied by the applicative writing on the HCFG.BYPASS_REQ_N, the applicative will guarantee that the message is in the right format, with the right address, etc.

Example of HART commands that were sent to the device and the received responses by the device with the address = 0 and DEV_ID = 3E 02 0C 72 29.

The number of initial FF (preambles can vary normally between 3 and 10). Remember the HART frame has the following structure: <Frame Size>, <Preambles>, <Delimiter>, <Address>, <Command>, <Data Size>, <Data>, <Checksum>.

Command #0: 0A FF FF FF FF FF 02 80 00 00 82 Response: FF FF FF FF FF 06 80 00 0E 00 02 FE 3E 02 05 05 03 24 09 00 0C 72 29 31

Command #33: 12 FF FF FF FF FF 82 BE 02 0C 72 29 21 04 01 02 03 04 48 Response: FF FF FF FF FF 86 BE 02 0C 72 29 21 1A 0 0 42 01 39 42 C8 05 14 02 25 42 C8 05 14 03 20 7F FF FF FF 04 39 42 C8 05 14 0E

5.11

HI302 - User’s Manual

5.12

Chapter 6

BASIC FUNCTIONING THEORY

This chapter presents basic concepts on HI302 hardware to help the user to solve field and maintenance problems.

The HI302 Block Diagram

The figure below shows the block diagram of the HI302:

Hardware

Figure 6.1 – HI302 block diagram

This chapter presents a summarized description of the main functional blocks that make up the HI302 module, as a support for electricians and/or maintenance technicians. See below the GLL1193 main board pictures.

Figure 6.2 – GLL1193 Main boards’ picture

6.1

HI302 – User’s Manual

Power Supply, Operation Voltage and Protection

HOT SWAP

The HI302 is equipped with a U22 HOT SWAP controller that allows the insertion or removal of the module with the power supply on. This is important when the HI302 is being supplied by a shared source, e.g., a rack with other HI302 or DF51 modules. In addition to a 5V source, the HI302 should receive a failure signal from the source (/PFAILR), working at a low level. That signal indicates to the HI302 that the feeding has been stopped and the starts a safety procedure for failing feed. The Smar PS-AC and DF50 sources also have this signal. The HOT SWAP controller also monitors the power consumption and, if a problem arises, the feeding is switched off to avoid further damages to the HI302 and the power supply.

ATTENTION

If the HI302 is supplied by a source without the failure signal, the pin should be left open.

Regulators

The HOT SWAP controller receives +5VN voltage from the rack (or external source) and, through the MOS channel-N transistor, delivers +5VD to all digital circuits. A 3V3 (U11) regulator feeds the EPLD (U10). And there is yet a precision 2V5 (U9) power source of reference for the virtual ground cable of the operational amplifiers in the Fieldbus and HART communication circuits.

In the HI302-I and HI302-O modules, there are also a DC-DC (U1) converter and the optical couplers that completely isolate the ground cables of the analog and digital circuits. The DC-DC converter generates, from the +5VD, a non-regulated voltage called +VA (+9V) that is used by the analog inputs (HI302-I), and through a linear regulator generates a +5VA voltage for the other circuits (ADC and DAC). As a voltage reference for converters there is another 4V096 (U8) precision reference.

Protection

The HI302 has advanced specific components for protection against ESD and voltage surges. However, keep in mind that good ground wiring is fundamental.

6.2

Figure 6.3 – HOT SWAP controller

Basic Functioning Theory

Processing Core

Figure 6.4 – ESD protection

Electrostatic Discharge (ESD)

The power input (DS1 and DS2) and all the communication channels are protected against electrostatic discharges by specific components (zener diodes) with high response speed and good power absorbing capacity (24W @ 1ms @ 25 oC). In addition to this protection, there are sparklers built on the printed circuit board, on every LEDs and on all (CN5 and CN6) front connector pins. They are designed to sparkle within 200 to 300V voltages, depending on the air humidity.

Surges, High Voltage and Grounding

Voltage surges, whether inducted or conducted, occur often in industrial environments due to electric motors, frequency inverters semiconductors switching and many other factors. Besides, there is always the danger from atmospheric discharges that may permanently damage the equipment. HI302 modules have components highly efficient against these surges, with high absorption capacity (400W @ 1 ms @ 25oC) and a (typically < 1 ns) good response speed, in addition to the PCI built-in sparklers. However, this protection is practically useless without a good wire grounding.

ATTENTION

Indispensably, a good quality grounding (< 5Ω) must be connected to the system, either on the DIN rail, on the power source, or directly to the module grounding terminal. Without this, all protection for the HI302 module, as well as for other equipment, WILL NOT WORK. Note that grounding resistance must be measured every 2 years.

The core of the HI302 module is based on the 68HC11 (U1) microcontroller running at 16 MHz (Y1): one of the most reliable and well accepted components worldwide. Around the microcontroller, there is the Fieldbus Smar FB3050 (U2) controller. Also there are the 128x8 (U3) SRAM memories and the 512kx8 (U4) FLASH. And to store the module configuration for the functional blocks and the HART commands there is a 32kx8 (U6) synchronous serial memory. A (U5) reset circuit/voltage supervisor is also part of the equipment.

Firmware programming

Programming the firmware in the FLASH memory is done through a RS232 serial interface (U2, on the backup board) by using the bootloader mode on the HC11. The connector is accessed in the module’s lower part, and it can be done by user, if the programming cable and the FBTools, integral to the System302, are available.

6.3

HI302 – User’s Manual

Connector with cover

Connector without cover

Connector cover

Figure 6.5 – Firmware programming connector

To reduce the amount of components, increase reliability and make the hardware more flexible, a EPLD, U10 programmable logic device has been used, including several functions with combinational and sequential logic, such as frequency divider for HART modems, address decoders, etc. This component is supplied with 3V3 and has 5V-compatible inputs and outputs. One of its most important functions is to generate the clock for the HART modems, stemming from the UART clock.

EPLD Programming

Update the EPLD programming in the circuit is also possible, due to the continuous improvement in the equipment, though it should only be done in the factory.

Manual RESET key and FACTORY INIT

In the front of the HI302 module there are two push button keys. One of them (on the left side) is the manual RESET button, connected to the U5, which covers the following components: HC11 (U1), FB3050 (U2), EPLD (U10) and UARTs (U7 and U8). The other key (on the right side) interrupts the HC11, which initializes the memory and brings the whole configuration back to the factory standard. This option is very useful in case of malfunctioning due to configuration errors, as it reinstates the configuration memory in its basic functional status. The calibration data are not lost during the factory init.

6.4

Figure 6.6 – Fct Init

ATTENTION

Does not press the RESET button when the HI302 while the factory init process is going on. Otherwise the entire configuration will be lost. Also, pay close attention to not push the Fct Init button instead of the RESET button.

HI302 Module Resetting

The HI302 module has a very sophisticated resetting system, consisting of a circuit that supervises the U5 supplying voltage and of several built-in mechanisms on the HC11 microcontroller, such as the WATCH DOG clock monitor. In addition, the RESET is used by the U10 EPLD to adjust the firmware programming (resident program). When starting up the module, the EPLD begins the device’s normal operation. If the RESET button is pressed for 5 seconds, the module enters in the BOOTLOADER mode, and is ready to update the resident program on the FBTools. When the RESET button is pressed again, the HI302 module gets back to normal operation.

IMPORTANT

From what was explained above, press the RESET button twice to get the HI302 RESET.

H1 Fieldbus Communication

The Fieldbus communication is done through the FB3050, that access directly the memory via DMA and shares the 16 MHz clock generated by the HC11 (U1). The analog interface is done through the Media Access Unit (MAU). This is a passive interface, i.e., it is not fed by the H1 bus, with capacitive decoupling and galvanic isolation. It is protected against electrostatic discharges and voltage surges. All circuits are fed with +5VD, and some operational use the 2V5 reference.

The communication is indicated by a LED fed by the (U10) EPLD, as the LED blinks at every message transmitted.

HART Communication

The HI302 modules have 8 channels for HART master communication, with capacitive and galvanic isolation (TF3). All channels also are protected against ESD (D14) and surges (Z2, Z3 and Z5). The initial stage on each receptor is a band pass filter (U23A) centralized in approximately 1700 Hz, as the range of HART communication frequencies is from 1200 to 2200 Hz (fundamentals). Next, a comparator (U27A) changes the signal received and amplified in a square wave, for it to be decodified by the Smar HT2012 HART modem (U35). The transmission is made by switching a 22µF electrolytic capacitor that works integrating the signal modulated by the HT2012.

Every HART channel has a LED (L1), controlled by the UART, indicating the several statuses of the channel’s work. Two quadruple UARTs (U7 and U8) totaling 8 independent UARTs concentrate the 8-channel communication.

These UARTs generate a signal of 14.7456 MHz (Y2) used by them and by a divider on the EPLD (U10), that generates the clock for the modems, 460,80 KHz strong.

4-20mA to FOUNDATION Fieldbus Analog Conversion (HI302-I)

The HI302-I model has an additional circuit (GLL1205 backup board) that converts the transmitter’s analog signal by means of a signal conditioning circuit and a low pass filter with a cut frequency of approximately 10Hz (U9A), an AD converter (U7) and a referential voltage source of 4V096 (U8). These circuits are protected against high voltage by zener diodes, against overheating and inverted polarity. This backup board is connected by the CN2 and allows the module to indicate the current measured value by a MAI (or AI) block, to be utilized on any control mesh. All circuits forming the analog acquisition are isolated from the others by a DC-DEC (U1) converter and by (U3, U4...) optical couplers. The reading update is approximately 200 ms.

Basic Functioning Theory

6.5

HI302 – User’s Manual

Figure 6.7 – Signal conditioning and low-pass filter circuit

FOUNDATION Fieldbus to 4-20mA Analog Conversion (HI302-O)

In a similar way, a board with analog output circuits is capable of controlling a current used by actuators, for example. These circuits are protected against high voltage by zener diodes, against overheating and against inverted polarity. The output module uses circuits required by current control (UX), in addition to a (U8) 12 bits DA converter and a referential 4VO96 (U9) voltage source. These circuits make up 8 independent channels for current control working in parallel to HART digital communication. This backup board is connected via CN2 and allows for the module to control the current’s value by means of a MAO (or AO) block, utilized on any control loop. All circuits forming the analog acquisition are isolated from the others by means of a DC-DC (U1) converter and (U3, U4...) optical couplers. The output backup board informs if the current loop is open or not, through the circuit formed by U10. The output update period is approximately 200 ms.

6.6

Chapter 7

Installation

AN EXAMPLE OF HI302 USAGE

There follows an example of how the HI302 can access the variables of the Smar LD301 intelligent pressure transmitter. From this example, users may create more complex configurations. For further details, see the other chapters of this manual.

See below how the LD301 transmitter was connected to the HI302, by using the resistor inside the HI302-I:

Step by Step Configuration

1. When the HI302 is fed by the rack and is s witched on, press the Fct Init button to initialize the factory configuration. The device will reset and then light the yellow LED SAVING and all LEDs on the HART channels. HI302´s current configuration will be lost! While the LED SAVING is lit the HI302 cannot be turned off or reseted.

2. Next, if the HI302 is connected to the FOUNDATION fieldbus bus, the green H1 LED will start blinking quickly, indicating that the communication started. If it does not blink, it may possibly be some problem with the FOUNDATION fieldbus bus. The first time the HI302 is connected to the DFI302, wait approximately 2 minutes until the HI302 is on the Live List.

3. Open the F on the Live List, according to the next figure.

4. Create a configuration that includes one RESOURCE b lock, one HCFG block, one HIRT block and one HVT block. Then, is necessary commission the HI302, as show the figure below.

Figure 7.1 – HI302-I Application Example

OUNDATION fieldbus configurator (Syscon in the ex ample) and notice that the HI 302 is

Figure 7.2 – Live List

Figure 7.3 – HI302 Configuration

7.1

HI302 – User’s Manual

5. Configure the MODE_BLK of RESOURCE and HVT blocks to AUTO.

6. Fill up the basic parameters on the HIRT block so that the HI302 communicates with the HART device. This minimum configuration makes it possibl e for the HI302 to find the device an d start the communication. In fact, let’s see:

• MODE_BLK.TARGET = AUTO, so that the block starts right away executing the mode.  HART_CHANNEL = 1, must be the same physical channel where the device is installed, in this

case is the channel 1.

 POLL_ADDR = 1, assuming this is the device’s address, previously configured in HART

equipment.

 ID_CMD = 0 – Polling address, as the polling address is to be used.

Figure 7.4 – HIRT Block Parameters

7. After filling up the essential parameters, just download the configuration. See the next figure:

Figure 7.5 – Downloading the Configuration

8. After the download, do an “Export Tags”.

7.2

An Example of HI302 Usage

Step by Step Operation

9. After executing the download, the HART communication must be started manually. Open the HCFG block on on-line mode choosing ENABLED on the COMM_ENABLE parameter. When you close the block, choose “No” when the Syscon ask if the user wants to salve the parameter.

10. The HART communication should start immediately aft er the parameter changes to ENABLED. This may be easily checked by the irregular blinki ng in the gree n C H#1 L ED, accor ding to the HART transactions. Note that the CH#2 to CH#8 LEDs blink at the 1/4 Hz frequenc y, to indicate that there is no HIRT block using the channel.

11. Open the HIRT block on on-line mode, notice that the BLK_EXEC_STATE parameter, from IDENTIFICATION, changes to UPDATING and after to UPDATED. If not, check if the block is being executed, notice if the MODE_BLK.ACTUAL parameter is AUTO. Other wise, redo the configuration from the step 6.

12. After the device’s initial identification the HI302 will continuously send some com mands doing the equipment polling.

13. When on UPDATED, just proceed as if with any common parameter of writing, in order to write in a parameter, for example, MESSAGE. Note that the BLK_EXEC_STATE parameter passes by three states: WRITING, OLD DATA and UPDATED. In normal conditions, the block must always return to UPDATED, to indicate that the data in the block are the same ones as the writing values in the HART device.

Figure 7.6 – Export Tags

Figure 7.7 – HCFG Block

7.3

HI302 – User’s Manual

Figure 7.8 – HIRT Block

14. After the device related to the HIRT block has been identified, it is also possible to read and write on the specific variables, by using the HVT block on on-line mode. The HVT block must also have both the MODE_BLK.TARGET and MODE_BLK.ACTUAL = AUTO. Then, just write the device HART TAG (HART_TAG parameter of HIRT block), in the DEV_TAG_SEL (DEV_TAG_SEL = LD301-1A) parameter, to start reading the specific variables in the HVT parameters. Refer to the allocation map from the HVT block to the device, so that you can relate the HVT param eters to the variables on the HART device. The allocation maps for all equipment with the configuration built-i n the HI302 are shown in the Appendix C.

15. As soon as HART_TAG is written, the HVT block starts the up date, by sending all the reading commands in the configuration, to the LD301. See that the BLK_EXEC_STATE parameter changes to UPDATING and then goes to UPDATED at the end of the process, which lasts about 2 minutes. Moreover, it shows on the HCD_DEVICE_INFO and HCD_SELECTED parameters information about the selected configuration.

16. To make some writing, the process is the same as for the HIRT. T he next figure sho ws the HVT being updated.

7.4

An Example of HI302 Usage

Figure 7.9 – Updating the HVT

7.5

HI302 – User’s Manual

7.6

Chapter 8

Installation

Problem Solution

When do I have to use the 250Ω resistor in series with the loop?

When do I have to use the active impedance PSI301P?

The instrument is correctly installed; it works normally, communicates with a portable programmer, but it does not communicate with the HI302.

Configuration

Problem Solution

I cannot instantiate the MAI/MAO block.

After sending the configuration to the HI302, the HART communication does not work.

What is the correct procedure to remove a device for maintenance?

TROUBLESHOOTING

• Increase the impedance measured from the HI302 terminals if it is less than 250Ω.

Maybe, it is necessary to increase the supply voltage.

• See the “Impedance x Minimum Supply Voltage” graphic in the Chapter 2 for further details.

• The active impedance should be used when the total loop current prevents the use of a resistor. This happens when using a multidrop connection with the device’s analog output enabled (varying from 4 to 20 mA) or the number of devices is more than 4 even in fixed current mode. See an example in the Chapter 2.

• Place the portable programmer terminals on the HI302 corresponding channel and check whether it communicates correctly. If it works, it may be a problem with the HI302. If not, check the equipment and the installation.

• This problem may happen especially with actuators (a low impedance device). Probably a high impedance device, such as a transmitter or an indicator, in the loop is preventing the communication. The solution lies in connecting a capacitor (0.1 to 1μF x 200V) in parallel to the high impedance device that is preventing the communication.

• If it does not solve the problem, check the wiring and the configuration in the corresponding HIRT block.

• Check the firmware version in the HCFG.FIRMWARE_VERSION parameter. Only the HI302-I supports the MAI block. The HI302-O supports the MAO block. The HI302-N supports neither the MAI nor the MAO blocks.

• Check if the correct DD is installed in the configurator and is being used.

• Check if the HART channel LEDs are lit. The HCFG.COMM_ENABLE parameter

must be on DISABLED. Write the ENABLED value manually to start operating the HI302.

• Check if the HIRT blocks parameters are set as follow:

o MODE_BLK.ACTUAL = AUTO; o BLOCK_ERR = PowerUp; o BLK_EXEC_STATE = IDENTIFICATION.

• Set the block to OS (MODE_BLK = OS). Thus, the channel will not be occupied trying to communicate with devices that are not being used.

8.1

Troubleshooting

Operation

Problem Solution

The HIRT block does not change from the IDENTIFICATION status.

The HIRT block does not change from DEVICE NOT FOUND status.

Once set at UPDATED, the HI302 does not start to poll the device or the variables have not been updated.

The HVT block does not start UPDATING when writing the TAG on the DEV_TAG_SEL parameter.

The read value does not correspond to the HART device variable.

I cannot write in the parameter.

When attempting to program a new firmware (a new version of the resident program), the FBTools displays an error message.

• Check if the block is working properly: MODE_BLK.ACTUAL = AUTO and BLOCK_ERR = PowerUp.

• Check if the HART communication is enabled in the HCFG.COMM_ENABLE parameter.

• The device was not found by using the command selected in the HIRT.ID_CMD parameter.

• The POLL_ADDR or the HART_TAG may be wrong. Check them.

• Check if the Polling is enabled in the HIRT.POLL_CTRL parameter.

• Check if the VIEW selected in the HIRT.VIEW_SELECTION parameter

corresponds to the right VIEW to update the desired dynamic variables. Each VIEW reads different HART variables and updates a different group of parameter under a different polling cycle.

• Check if the dynamic variables are from A to D group, check the configuration code of these variables

• Check if the block is working: MODE_BLK.ACTUAL = AUTO and BLOCK_ERR = PowerUp.

• Check if the TAG that has been written on the DEV_TAG_SEL parameter is the HART_TAG and not the HIRT block TAG.

• Check if the HI302 has the configuration for the desired HART device The HI302 uses the MAN_ID, DEV_TYPE, UNI_REV, SPEC_REV and SW_REV parameters to find the configuration in the memory.

• Check if BLK_EXEC_STATE = UPDATED. The parameters related to the HART variable are valid if the BLK_EXEC_STATE = UPDATED.

• For the HVT block, make sure the read parameter corresponds to the desired variable. See the HVT block allocation map.

• Does the parameter correspond to a HART variable that can be written? Is this reflected in the current device’s configuration? Check them.

• Even for the HIRT block, check if the device supports the HART command used for writing. See on the Appendix section a detailed explanation about the commands used by the HIRT block for writing.

• Check if the HI302 is in Bootloader mode. In this mode, only the ON (green), SAVING (yellow), and H1 (green) LEDs must be lit. To access the Bootloader mode, press the RESET button for 5 seconds, with the module started up. By pressing again the RESET button after the programming is done, the module will start executing the new resident program.

8.2

Questions and Answers

Next see some of the most common questions about the HI302:

1. Does the HART communication interfere in the 4-20mA control signal?

No. The HART communication is imposed by a modulated signal in FSK (Frequency Shift Keying) over the current signal generated or received by the device, in a frequency usually ranging from 500 Hz to 4 KHz. According to the theory of communications, a signal modulated in FSK has an average value equal to 0, and therefore no disturbance is caused on the control signal. Thus, the HI302 module may be connected to any existing installation. The wiring used in the HI302’s installation may be a noise receiver source and cause interference in the control loop. To avoid such problem, the user should use a shielded cable with the minimum length and with good electrical connection.

2. Does the HI302 work with third-party devices, that is, those not made by Smar?

Yes. HI302 was designed to work with any devices that comply with HCF (HART Communication Foundation) standard. The most used universal and common practice commands are supported by the HI302 through the HIRT block, with no need for a special command configuration. If the user wants to use the device’s complete set of commands (Common Practice and Specific Commands), a specific configuration must be loaded, based on the device documentation. For Smar devices, this configuration is already built in the HI302’s memory.

3. Can I link the PV_VAL parameter in my FOUNDATION fieldbus strategy?

Yes. The HIRT block has 8 parameters which can be used in the control strategy: PV_VAL, SV_VAL, TV_VAL, QV_VAL, A1_VAL, A2_VAL, A3_VAL and A4_VAL. The updating time of these parameters depend on the HART commands quantity exchanged with the device.

4. Are the HI302 channels isolated among themselves?

The HI302-N model has channels isolated among them and they can be connected to different I/O systems with different power supplies with independent grounding. The grounding of the eight channels of the HI302-I and HI302-O are internally connected, thus the HART channels are not isolated among themselves.

5. Which dynamic variables of the HART device can the HI302 read and how the user can access them?

The HI302 has a group of parameters that can be updated during the polling, according to the VIEW selected in the HIRT.VIEW_SELECTION parameter. The VIEWs use the HART 33 command to access the variables listed in the HART device. Actually, any HART variable, accessible by the 1, 2, 3 or 33 commands, can be read by the HI302. The variables accessible by the command 33 require the configuration of the HIRT block XX_CODE parameters. For example, the user wants to read the TEMP_MAX variable, which the manufacturing code is 12. Then, configure the A1_CODE parameter with 12 and select the VIEW_02. Thus, the variable TEMP_MAX will be read in the A1_VAL parameter, and in turn its unit on the A1_UC parameter.

6. How many HI302 modules can be installed on the same H1 bus?

We suggest up to 4 HI302 per H1 bus (maximum). For example, up to 16 HI302 can be installed in one DF62.

7. Can other types of devices be installed on the same H1 channel?

Yes, as long as all limitations and restrictions are considered regarding the time for blocks and parameters supervising, publication of links, etc. The HI302 macrocycle is very large (~1s) because the HIRT block execution takes a lot of time (~50 ms).

8. How many HART devices can be connected to a HI302?

We suggest the installation of one HART instrument for each HI302 channel. Consult us about multidrop mode, that is, with more than one HART instrument per channel.

9. What is the difference among the HI302-N, HI302-I and HI302-O?

The three models work on the same basic hardware and firmware platform, the difference being on the analog conversion board installed over the main board and in the block analog support:

• On the HI302-N model there is no analog conversion, only HART communication.

• On the HI302-I, the circuit converts 4-20mA to F

• On the HI302-O, the installed circuit converts from F

MAO block.

HI302 – User’s Manual

OUNDATION fieldbus, through a MAI block.

OUNDATION fieldbus to 4-20mA, by using a

8.3

Troubleshooting

10. Wh at is the Update Periodicity of the HART variables on the HI302 blocks?

This period of time depends on a series of factors such as: number of devices per channel, communication errors, presence of another master in the channel, a device in Burst Mode, number of the selected VIEW, etc. Generally, a HART transaction lasts about 800 ms to be finished. See in the VIEW table, the average time to update the dynamic variables.

11. Does th e HI302 let Portable Programmers to be used, such as the HPC401?

Yes. Since the HPC401 is a Secondary Master, it is possible to have it connected to a HI302 channel without any problems, provided this channel is configured as a Primary Master.

12. Is necessary to use the active impedance DF53 to install the HI302?

No, the HI302 does not need the H1 bus power supply, thus the DF53 is not necessary. However the BT302 should always be used.

8.4

Appendix A

A.1

HCFG - HART CONFIGURATION & DIAGNOSTIC

Index Parameter Data Type Valid Range / Options Default Value Units Store / Mode Description

BLOCK_STRUCTURE DS-64 NA S

ST_REV Unsigned16 0 None S / RO

TAG_DESC OctString(32) Spaces NA S

STRATEGY Unsigned16 0 None S

ALERT_KEY Unsigned8 1 to 255 0 None S

MODE_BLK DS-69 O/S NA S See Mode’s Parameter

BLK_ERR Bitstring(2) None D / RO

FIRMWARE_VERSION VisibleString(32)

0 NA D / RO Useful for information and diagnostic purposes.

COMM_BEHAVIOR Enumerated

0x00: Autonomous 0x01: Bypass

Autonomous NA S

Autonomous means the normal behavior where the database is built automatically. If set to Bypass the device depends on external applications to send HART commands and the block HBC must be used.

COMM_ENABLE Enumerated

0x01 Enabled 0x00: Disabled

Disabled NA S

After a download or if a channel has been changed in a HIRT block, this parameter will be set to Disabled automatically. Set it to ENABLE to start HART communication. Caution: this parameter must not be

saved OFFLINE and downloaded. It must always be written in ONLINE mode only!

CHANNEL_ACTIVE Enumerated[8]

0x00: No 0x01: 1 0x02: 2 0x0F: 15

No NA D / RO

This parameter shows how many HIRT blocks have been configured to use the corresponding channel. If no block is using the channel, it will remain deactivated.

COMM_ERRORS Float[8]

0 % D / RO

Shows the percentage of communication errors. Up to

0.5% is acceptable for more than 10000 requests.

MASTER_TYPE Enumerated[8]

0x01: Primary 0x00: Secondary

Primary NA S HART Master Type, normally Primary.

RETRIES Unsigned8[8] 3 to 10 3 None S

Number of retries if slave does not respond before slave timeout or if any error is received. Increase the number to make the communication more reliable in noisy environments.

MASTER_SYNCHRONIZED Boolean[8]

0x01: Synchronized 0x00: Not synchronized

Not synchronized NA D / RO

FACTORY USE - Synchronized means normal operation.

CHANNEL_MODE Enumerated[8]

0x00: Normal 0x01: Burst Mode

Normal None D / RO

FACTORY USE - This parameter shows if any burst mode device was detected on the resp ective channel.

MASTER_STATE Enumerated[8]

0x00: Watching 0x01: Enabled 0x02: Using

Watching None D / RO

FACTORY USE - It's the Master State Machine behavior at each moment.

HI302 – User’s Manual

A.2

Index Parameter Data Type Valid Range / Options Default Value Units Store / Mode Description

REQUEST_COUNTER Unsigned32[8]

0 None D / RO

FACTORY USE - Counts the number of requests made to all devices on that channel.

RETRIES_COUNTER Unsigned32[8]

0 None D / RO

FACTORY USE - Counts the number of retries to all devices on each channel.

INVALID_SOM Unsigned32[8]

0 None D / RO

FACTORY USE - Counts the number of invalid Start Of Messages captured in that channel.

INVALID_RX_FRAMES Unsigned32[8]

0 None D / RO

FACTORY USE - It totalizes the number of INVALID frames received by each channel, whichever the error.

VALID_RX_FRAMES Unsigned32[8]

0 None D / RO

FACTORY USE - It totalizes the number of VALID frames received by each channel.

ANALOG_INPUT_TRIM Enumerated

0x00: Channel 1, 0x01: Channel 2, 0x02: Channel 3, 0x03: Channel 4, 0x04: Channel 5, 0x05: Channel 6, 0x06: Channel 7, 0x07: Channel 8, 0x08: All Channels, 0x09: Not Trimmed, 0x0A: Trimmed and

Checked

Not Trimmed NA S

FACTORY USE - Used to calibrate the analog inputs when applicable. Apply a stable signal of 12 mA (+/-

0.005 mA) to the channel (or to all channels at once) and write to this parameter accordingly to the channel you want to calibrate (or All Channels if you want to calibrate all at once). After calibrate and test write this

parameter to Trimmed and Checked to save the data.

ANALOG_OUTPUT_CAL Float[8]

1.00 mA S

FACTORY USE - This array is used to calibrate the analog outputs when applicable. Using a precision miliamperemeter (+/- 1uA) put all outputs in 50% by actuating in MAO block. Using the value the meter is reading, write it in the corresponding element of this array, always with at least 2 decimal, in mA (should be ~ 12 mA). After written the value look at the meter again and confirm the reading now is 12.0 mA. After calibrate

and test write ANALOG_INPUT_TRIM parameter to Trimmed and Checked to save the calibration data.

UPDATE_EVT DS-73 NA D This alert is generated by any change to the static data.

BLK_ALM DS-72 NA D

The alarm block 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 will set the Active status in the Status attribute. As soon as the Unreported status is cleared by the alert reporting ta sk, another block alert may be reported without clearing the Active status, if the subcode has changed.

Appendix A

A.3

HIRT - HART INFORMATION & DYNAMIC DATA and HUT – HART Universal Transducer

Index Parameter Data Type Valid Range / Options

Default/

Value

Units

Store

/Mode

Description

HART

Read

HART Write

BLOCK_STRUCTURE DS-64 NA S

ST_REV Unsigned16 0 None S / RO

TAG_DESC OctString(32) Spaces NA S

STRATEGY Unsigned16 0 None S

ALERT_KEY Unsigned8 1 to 255 0 None S

MODE_BLK DS-69 O/S NA S See Mode’s Parameter

BLK_ERR Bitstring(2) None D / RO

HART_CHANNEL Unsigned8 1 to 8 1 None S HART channel where the device is attached to.

ID_CMD Enumerated

0: 0 - Polling Address 11: 11 - HART Tag

0 - Polling

Address

None S

Selects the HART Universal Command used to identify the device associated with this block.

LAST_HART_WRITE_STATUS

Enumerated

0x00: No Command-Specific Errors 0x05: Too Few Data Bytes Received 0x07: In Write Protection Mode 0x08: Warning: Update Failure 0x20: Busy 0x40: Command Not Implemented 0x81: Undefined Comm Error 0x82: Buffer Overflow 0x84: Reserved Comm Error 0x88: Longitudinal Parity Error 0x90: Framing Error 0xA0: Overrun Error 0xC0: Vertical Parity Error

0x00: No

Command-

Specific

Errors

None D / RO

This parameter always reflects the first byte of the Response Code (Command Response Summary) of THE LAST WRITE HART COMMAND ISSUED and must be checked to ensure the write operation has been succeeded.

POLL_ADDR Unsigned8 0 to 15 0 None S Device's Polling (short) Address.

7 6

HART_TAG VisibleString(8) Spaces NA S Device's TAG.

13 18

POLL_CTRL Boolean

0x01: Polling Enabled 0x00: Polling Disabled

Polling

Enabled

NA S Real Time Data Polling Control.

HI302 – User’s Manual

A.4

Index Parameter Data Type Valid Range / Options

Default/

Value

Units

Store

/Mode

Description

HART

Read

HART Write

VIEW_SELECTION Enumerated

0x00: VIEW_00, 0x01: VIEW_01 0x02: VIEW_02, 0x03: VIEW_03 0x04: VIEW_04, 0x05: VIEW_05 0x06: VIEW_06, 0x07: VIEW_07 0x08: VIEW_08, 0x09: VIEW_09 0x0A: VIEW_10, 0x0B: VIEW_11 0x0C: VIEW_12, 0x0D: VIEW_13 0x0E: VIEW_14, 0x0F: VIEW_15 0x10: VIEW_16, 0x11: VIEW_17 0x12: VIEW_18, 0x13: VIEW_19 0x14: VIEW_20, 0x15: VIEW_21 0x16: VIEW_22, 0x17: VIEW_23 0x18: VIEW_24, 0x19: VIEW_25 0x1A: VIEW_26, 0x1B: VIEW_27 0x1C: VIEW_28, 0x1D: VIEW_29

VIEW_00 None S

Selects the set of parameters to be updated at each polling cycle. See HI302's user manual for further information about each VIEW.

COMMON_CMD_FILTER Unsigned8[5]

0 None S

This parameter has 5 positions to ignore commands present in configuration, but not supported by the device. See HI302´s User Manual for a complete list of that commands.

BLK_EXEC_STATE Enumerated

0x00: Identification 0x01: Old Data 0x02: Updating 0x03: Updated 0x04: Partially Updated 0x05: Not Responding 0x06: Bypass 0x07: Device Not Found 0x08: HCD Error 0x09: TAG Not Found 0x0A: Writing

Identification None D / RO

Status of parameter updates information and HART communication. Normal condition is UPDATED.

COMM_ERR BitString(8)

0x00: No

Command-

Specific

Errors

None D / RO

First byte of the last transaction’s Response Code if communication error has occurred (Bit7 = 1).

All All

Appendix A

A.5

Index Parameter Data Type Valid Range / Options

Default/

Value

Units

Store

/Mode

Description

HART

Read

HART Write

DEVICE_STATUS BitString(8)

0x01: Primary Variable Out of Limits 0x02: Non-Primary Variable Out of

Limits

0x04: Loop Current Saturated 0x08: Loop Current Fixed 0x10: More Status Available 0x20: Cold Start 0x40: Configuration Changed 0x80: Device Malfunction

0 NA D / RO

Second byte of the last transaction’s Response Code. See HART equipment's Manual or HART specification for further details.

All All

ADDITIONAL_STATUS OctString(6) 0 NA D / RO

Cyclic read depends on chosen VIEW. Device specific Additional Status. See device’s specific documentation for further details.

MAN_ID Enumerated HC TABLE 8 0 None D / RO

Manufacturer ID Code. Used to select specific configuration for HVT block.

(0, 11)

DEV_TYPE Unsigned8 0 None D / RO

Manufacturer Device Type Code. Used to select specific configuration for HVT block.

(0, 11)

UNI_REV Unsigned8 0 None D / RO

Revision Level of the HART Universal Commands. Used to select specific configuration for HVT block.

(0, 11)

SPEC_REV Unsigned8 0 None D / RO

Revision Level of the Device Specific. Used to select specific configuration for HVT block.

(0, 11)

SW_REV Unsigned8 0 None D / RO

Software Revision Level. Used to select specific configuration for HVT block.

(0, 11)

HRDW_REV Unsigned8 0 None D / RO Hardware Revision Level.

(0, 11)

FLAGS BitString(8) HC TABLE 11 0 NA D / RO Flags (manufacturer’s specific).

(0, 11)

DEV_ID OctString(3) 0 NA D / RO Device ID Number.

(0, 11)

LOOP_CURRENT DS-65 0 mA D

Cyclic read depends on chosen VIEW. Loop Current Value (mA).

LOOP_CURRENT.VALUE: loop mA last value, LOOP_CURRENT.STATUS: HART Response

Code converted to FOUNDATION fieldbus status. See HI302´s User Manual for further det ails.

LOOP_TEST Float 0 mA D

Write the desired current value in mA to enter fixed current mode. Write 0 to exit fixed current mode.

LOOP_CMODE Enumerated HC TABLE 16 0 None D

Loop Current Mode. See device’s specific documentation.

7 6

MESSAGE VisibleString(32) Spaces NA D Message for general purpose.

12 17

DESCRIPTOR VisibleString(16) Spaces NA D Descriptor, text for general purpose.

13 18

DATE_INFO Date

1/1/2001

00:00:00:0000 NA D Date (Only Day/Month/Year are considered).

13 18

WRITE_PCODE Enumerated HC TABLE 7 0 None D / RO

Write Protect Code. See device’s specific documentation.

PLDC Enumerated HC TABLE 8 0 None D / RO Private Label Distributor Code.

HI302 – User’s Manual

A.6

Index Parameter Data Type Valid Range / Options

Default/

Value

Units

Store

/Mode

Description

HART

Read

HART Write

PV_ACF Enumerated HC TABLE 26 0 None D / RO

PV Analog Channel Flags. See device’s specific documentation.

FAN OctString(3) 0 NA D Final Assembly Number.

16 19

DEV_TEST Enumerated

0x00: Invoke Self Test

0 None D Write to perform a device self test.

DEV_RESET Unsigned8

0x00: Reset Device

0 None D Write to perform a device Master RESET.

BURST_MODE Enumerated HC TABLE 9 0 None D It allows to control device's Burst Mode

109

PV_ULRUC Enumerated HC TABLE 2 0 None D PV Upper & Lower Range Value Units Code

15 35

PV_RANGE DS-68 {0, 0, 0, 0} XD_SCALE D

PV_RANGE.EU_100: HART PV Upper Range Value, PV_RANGE.EU_0: HART PV Lower Range Value, PV_RANGE_UNITS_INDEX: HART PV Range (Upper & Lower) Value Units Code translated to fieldbus table,

PV_RANGE.DECIMAL: no meaning.

15 35, 44

PV_CAL_POINT_L Enumerated

0x00: Set PV Zero

0 None D

Write to this parameter to set PV Zero (invoke HART Command 43).

PV_SENSOR_SN OctString(3) 0 NA D PV Sensor Serial Number.

14 49

PV_SENSOR_LMSUC Enumerated HC_TABLE 2 0 None D / RO

PV Sensor Limits and Minimum Span Units Code.

PV_SENSOR_MSPAN Float 0 49 D / RO PV Minimum Span.

PV_SENSOR_RANGE DS-68 {0, 0, 0, 0} XD_SCALE D / RO

PV_SENSOR_RANGE.EU_100: PV Upper Sensor Limit, PV_SENSOR_RANGE.EU_0: PV Lower Sensor Limit. PV_SENSOR_RANGE.UNITS_INDEX: PV Sensor limits and Minimum Span Units Code translated to Fieldbus table.

PV_SENSOR_RANGE.DECIMAL: no mean.

PV_ASC Enumerated HC TABLE 6 0 None D / RO PV Alarm Select code.

PV_TFC Enumerated HC TABLE 3 0 None D PV Transfer Function Code.

15 47

PV_DV Float 0 s D PV Damping Value.

15 34

PV_PERC DS-65 0 % D / RO

Cyclic read depends on chosen VIEW. PV Percent of Range.

PV_PERC.VALUE: the percentage PV value, PV_PERC.Status: HART Response Code

converted to FOUNDATION fieldbus status.

PV_UC Enumerated HC TABLE 2 0 None D PV Units Code.

15 44

PV_VAL DS-65 0 PV_UC D / RO

Cyclic read depends on chosen VIEW. PV_VAL.Value : actual PV value in engineering

units, PV_VAL.Status: HART Response Code converted to F

OUNDATION fieldbus status.

SV_UC Enumerated HC TABLE 2 0 None D / RO SV Units Code.

Appendix A

A.7

Index Parameter Data Type Valid Range / Options

Default/

Value

Units

Store

/Mode

Description

HART

Read

HART Write

SV_VAL DS-65 0 SV_UC D / RO

Cyclic read depends on chosen VIEW. SV_VAL.Value: SV actual value, SV_VAL.Status: HART Response Code converted to FOUNDATION fieldbus status.

TV_UC Enumerated HC TABLE 2 0 None D / RO TV Units Code.

TV_VAL DS-65 0 TV_UC D / RO

Cyclic read depends on chosen VIEW. TV_VAL.Value: TV actual value, TV_VAL.Status: HART Response Code converted to FOUNDATION fieldbus status.

QV_UC Enumerated HC TABLE 2 0 None D / RO QV Units Code.

QV_VAL DS-65 0 QV_UC D / RO

Cyclic read depends on chosen VIEW. QV_VAL.Value: TV actual value, QV_VAL.Status: HART Response Code converted to FOUNDATION fieldbus status.

A1_CODE Unsigned8 0 None S Selects variable to appear on A1_VAL

A1_UC Enumerated HC TABLE 2 0 None D / RO A1 variable Units Code.

A1_VAL DS-65 0 A1_UC D / RO

OUTPUT PARAMETER. Cyclic read depends on chosen VIEW and A1_CODE.

A2_CODE Unsigned8 0 None S Selects variable to appear on A2_VAL

A2_UC Enumerated HC TABLE 2 0 None D / RO A2 variable Units Code.

A2_VAL DS-65 0 A2_UC D / RO

Cyclic read depends on chosen VIEW and A2_CODE.

A3_CODE Unsigned8 0 None S Selects variable to appear on A3_VAL

A3_UC Enumerated HC TABLE 2 0 None D / RO A3 variable Units Code.

A3_VAL DS-65 0 A3_UC D / RO

Cyclic read depends on chosen VIEW and A3_CODE.

A4_CODE Unsigned8 0 None S Selects variable to appear on A4_VAL

A4_UC Enumerated HC TABLE 2 0 None D / RO A4 variable Units Code.

A4_VAL DS-65 0 A4_UC D / RO

Cyclic read depends on chosen VIEW and A4_CODE.

B1_CODE Unsigned8 0 None S Selects variable to appear on B1_VAL

B1_UC Enumerated HC TABLE 2 0 None D / RO B1 variable Units Code.

B1_VAL DS-65 0 B1_UC D / RO

Cyclic read depends on chosen VIEW and B1_CODE.

B2_CODE Unsigned8 0 None S Selects variable to appear on B2_VAL

B2_UC Enumerated HC TABLE 2 0 None D / RO B2 variable Units Code.

B2_VAL DS-65 0 B2_UC D / RO

Cyclic read depends on chosen VIEW and B2_CODE.

B3_CODE Unsigned8 0 None S Selects variable to appear on B3_VAL

B3_UC Enumerated HC TABLE 2 0 None D B3 variable Units Code.

HI302 – User’s Manual

A.8

Index Parameter Data Type Valid Range / Options

Default/

Value

Units

Store

/Mode

Description

HART

Read

HART Write

B3_VAL DS-65 0 B3_UC D / RO

Cyclic read depends on chosen VIEW and B3_CODE.

B4_CODE Unsigned8 0 None S Selects variable to appear on B4_VAL

B4_UC Enumerated HC TABLE 2 0 None D / RO B4 variable Units Code.

B4_VAL DS-65 0 B4_UC D / RO

Cyclic read depends on chosen VIEW and B4_CODE.

C1_CODE Unsigned8 0 None S Selects variable to appear on C1_VAL

C1_UC Enumerated HC TABLE 2 0 None D / RO C1 variable Units Code.

C1_VAL DS-65 0 C1_UC D / RO

Cyclic read depends on chosen VIEW and C1_CODE.

C2_CODE Unsigned8 0 None S Selects variable to appear on C2_VAL

C2_UC Enumerated HC TABLE 2 0 None D / RO C2 variable Units Code.

C2_VAL DS-65 0 C2_UC D / RO

Cyclic read depends on chosen VIEW and C2_CODE.

C3_CODE Unsigned8 0 None S Selects variable to appear on C3_VAL

C3_UC Enumerated HC TABLE 2 0 None D / RO C3 variable Units Code.

C3_VAL DS-65 0 C3_UC D / RO

Cyclic read depends on chosen VIEW and C3_CODE.

C4_CODE Unsigned8 0 None S Selects variable to appear on C4_VAL

C4_UC Enumerated HC TABLE 2 0 None D / RO C4 variable Units Code.

C4_VAL DS-65 0 C4_UC D / RO

Cyclic read depends on chosen VIEW and C4_CODE.

D1_CODE Unsigned8 0 None S Selects variable to appear on D1_VAL

D1_UC Enumerated HC TABLE 2 0 None D / RO D1 variable Units Code.

D1_VAL DS-65 0 D1_UC D / RO

Cyclic read depends on chosen VIEW and D1_CODE.

D2_CODE Unsigned8 0 None S Selects variable to appear on D2_VAL

D2_UC Enumerated HC TABLE 2 0 None D / RO D2 variable Units Code.

100

D2_VAL DS-65 0 D2_UC D / RO

Cyclic read depends on chosen VIEW and D2_CODE.

101

D3_CODE Unsigned8 0 None S Selects variable to appear on D3_VAL

102

D3_UC Enumerated HC TABLE 2 0 None D / RO D3 variable Units Code.

103

D3_VAL DS-65 0 D3_UC D / RO

Cyclic read depends on chosen VIEW and D3_CODE.

104

D4_CODE Unsigned8 0 None S Selects variable to appear on D4_VAL

105

D4_UC Enumerated HC TABLE 2 0 None D / RO D4 variable Units Code.

106

D4_VAL DS-65 0 D4_UC D / RO

Cyclic read depends on chosen VIEW and D4_CODE.

Appendix A

A.9

Index Parameter Data Type Valid Range / Options

Default/

Value

Units

Store

/Mode

Description

HART

Read

HART Write

107

E1_CODE Unsigned8 0 None S Selects variable to appear on E1_VAL

108

E1_UC Enumerated HC TABLE 2 0 None D / RO E1 variable Units Code.

109

E1_VAL DS-65 0 E1_UC D / RO

Cyclic read depends on chosen VIEW and E1_CODE.

110

E2_CODE Unsigned8 0 None S Selects variable to appear on E2_VAL

111

E2_UC Enumerated HC TABLE 2 0 None D / RO E2 variable Units Code.

112

E2_VAL DS-65 0 E2_UC D / RO

Cyclic read depends on chosen VIEW and E2_CODE.

113

E3_CODE Unsigned8 0 None S Selects variable to appear on E3_VAL

114

E3_UC Enumerated HC TABLE 2 0 None D / RO E3 variable Units Code.

115

E3_VAL DS-65 0 E3_UC D / RO

Cyclic read depends on chosen VIEW and E3_CODE.

116

E4_CODE Unsigned8 0 None S Selects variable to appear on E4_VAL

117

E4_UC Enumerated HC TABLE 2 0 None D / RO E4 variable Units Code.

118

E4_VAL DS-65 0 E4_UC D / RO

Cyclic read depends on chosen VIEW and E4_CODE.

119

F1_CODE Unsigned8 0 None S Selects variable to appear on F1_VAL

120

F1_UC Enumerated HC TABLE 2 0 None D / RO F1 variable Units Code.

121

F1_VAL DS-65 0 F1_UC D / RO

Cyclic read depends on chosen VIEW and F1_CODE.

122

F2_CODE Unsigned8 0 None S Selects variable to appear on F2_VAL

123

F2_UC Enumerated HC TABLE 2 0 None D / RO F2 variable Units Code.

124

F2_VAL DS-65 0 F2_UC D / RO

Cyclic read depends on chosen VIEW and F2_CODE.

125

F3_CODE Unsigned8 0 None S Selects variable to appear on F3_VAL

126

F3_UC Enumerated HC TABLE 2 0 None D F3 variable Units Code.

127

F3_VAL DS-65 0 F3_UC D / RO

Cyclic read depends on chosen VIEW and F3_CODE.

128

F4_CODE Unsigned8 0 None S Selects variable to appear on F4_VAL

129

F4_UC Enumerated HC TABLE 2 0 None D / RO F4 variable Units Code.

130

F4_VAL DS-65 0 F4_UC D / RO

Cyclic read depends on chosen VIEW and F4_CODE.

131

G1_CODE Unsigned8 0 None S Selects variable to appear on G1_VAL

132

G1_UC Enumerated HC TABLE 2 0 None D / RO G1 variable Units Code.

133

G1_VAL DS-65 0 G1_UC D / RO

Cyclic read depends on chosen VIEW and G1_CODE.

134

G2_CODE Unsigned8 0 None S Selects variable to appear on G2_VAL

HI302 – User’s Manual

A.10

Index Parameter Data Type Valid Range / Options

Default/

Value

Units

Store

/Mode

Description

HART

Read

HART Write

135

G2_UC Enumerated HC TABLE 2 0 None D / RO G2 variable Units Code.

136

G2_VAL DS-65 0 G2_UC D / RO

Cyclic read depends on chosen VIEW and G2_CODE.

137

G3_CODE Unsigned8 0 None S Selects variable to appear on G3_VAL

138

G3_UC Enumerated HC TABLE 2 0 None D / RO G3 variable Units Code.

139

G3_VAL DS-65 0 G3_UC D / RO

Cyclic read depends on chosen VIEW and G3_CODE.

140

G4_CODE Unsigned8 0 None S Selects variable to appear on G4_VAL

141

G4_UC Enumerated HC TABLE 2 0 None D / RO G4 variable Units Code.

142

G4_VAL DS-65 0 G4_UC D / RO

Cyclic read depends on chosen VIEW and G4_CODE.

143

H1_CODE Unsigned8 0 None S Selects variable to appear on H1_VAL

144

H1_UC Enumerated HC TABLE 2 0 None D / RO H1 variable Units Code.

145

H1_VAL DS-65 0 H1_UC D / RO

Cyclic read depends on chosen VIEW and H1_CODE.

146

H2_CODE Unsigned8 0 None S Selects variable to appear on H2_VAL

147

H2_UC Enumerated HC TABLE 2 0 None D / RO H2 variable Units Code.

148

H2_VAL DS-65 0 H2_UC D / RO

Cyclic read depends on chosen VIEW and H2_CODE.

149

H3_CODE Unsigned8 0 None S Selects variable to appear on H3_VAL

150

H3_UC Enumerated HC TABLE 2 0 None D / RO H3 variable Units Code.

151

H3_VAL DS-65 0 H3_UC D / RO

Cyclic read depends on chosen VIEW and H3_CODE.

152

H4_CODE Unsigned8 0 None S Selects variable to appear on H4_VAL

153

H4_UC Enumerated HC TABLE 2 0 None D / RO H4 variable Units Code.

154

H4_VAL DS-65 0 H4_UC D / RO

Cyclic read depends on chosen VIEW and H4_CODE.

155

UPDATE_EVT DS-73 NA D

This alert is generated by any change to the static data.

156

BLK_ALM DS-72 NA D

The alarm block is used for all configuration, hardware, and connection failure or system problems in the block. The cause o f the alert is entered in the subcode field. The first alert to become active will set 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.

Appendix A

A.11

IMPORTANT

The HIRT and HUT blocks are apparentely equals, but they have some important differences:

• The HIRT block is a function block, that is, can be used in control strategies in systems which support “manufacturer specific” function blocks. The HUT block is a transducer block to be used in systems which does not work with the HIRT block. In this case, the HART variables can be used only for supervision.

• The HIRT block lasts macrocycle’s time to be executed. If you need de crease the application macrocycle check the possibility to use the HUT block instead of HIRT block.

• The both blocks’ parameters are absolutely the same, except the following: PV_VAL, SV_VAL, TV_VAL, QV_VAL, A1_VAL, A2_VAL, A3_VA and A4_VAL. In the HIRT block, these parameters can be linked in the strategy while with the HUT block it is not possible.

HI302 – User’s Manual

A.12

HVT – HART Variable Template

Index Parameter Data Type Valid Range / Options Default Value Units Store / Mode Description

BLOCK_STRUCTURE DS-64 NA S

ST_REV Unsigned16 0 None S / RO

TAG_DESC OctString(32) Spaces NA S

STRATEGY Unsigned16 0 None S

ALERT_KEY Unsigned8 1 to 255 0 None S

MODE_BLK DS-69 O/S NA S See Mode’s Parameter

BLK_ERR Bitstring(2) None D / RO

DEV_TAG_SEL VisibleString(8) Spaces NA S

Write here a valid HIRT.HART_TAG from an installed device to start HVT on demand reading.

HCD_SELECTED OctString(5) 0 None D / RO

This code is used to identify the specific configuration associat ed w ith the chosen device. This code is read from HIRT block and is a combination of MAN_ID, DEV_TYPE, UNI_REV, SPEC_REV, SW_REV.

HCD_DEVICE_INFO VisibleString(32) Spaces NA D / RO This parameter shows comment related to select ed specific configuration.

BLK_EXEC_STATE Unsigned8

0x00: Identification 0x01: Old Data 0x02: Updating 0x03: Updated 0x04: Partially Updated 0x05: Not Responding 0x06: Bypass 0x07: Device Not Found 0x08: HCD Error 0x09: TAG Not Found 0x0A: Writing

0 None D / RO Reflects the execution progress or error conditions. See also BLK_ERR.

U8B_ARRAY_1 Unsigned8[20] 0 None D First array used for 8-bit variables

U8B_ARRAY_2 Unsigned8[20] 0 None D Second array used for 8-bit variables

U8B_ARRAY_3 Unsigned8[20] 0 None D Third array used for 8-bit variables

U8B_ARRAY_4 Unsigned8[20] 0 None D Fourth array used for 8- bit variables

U8B_ARRAY_5 Unsigned8[20] 0 None D Fifth array used for 8-bit variables

FLOAT_ARRAY_1 FloatingPoint[20] 0 None D First array used for Floating Point variables

FLOAT_ARRAY_2 FloatingPoint[20] 0 None D Second array used for Floating Point variables

FLOAT_ARRAY_3 FloatingPoint[20] 0 None D Third array used for Floating Point variables

FLOAT_ARRAY_4 FloatingPoint[20] 0 None D Fourth array used for Floating Point variables

FLOAT_ARRAY_5 FloatingPoint[20] 0 None D Fifth array used for Floating Point variables

U16B_ARRAY_1 Unsigned16[20] 0 None D First array of 16-bit (2-byte) values

U32B_ARRAY_1 Unsigned32[10] 0 None D First array of 32-bit variables

U32B_ARRAY_2 Unsigned32[10] 0 None D Second array of 32-bit variables

String_01 VisibleString(8) Spaces NA D First general string (8 characters)

String_02 VisibleString(8) Spaces NA D 8 characters general use string

String_03 VisibleString(8) Spaces NA D 8 characters general use string

String_04 VisibleString(8) Spaces NA D 8 characters general use string

String_05 VisibleString(8) Spaces NA D 8 characters general use string

String_06 VIsibleString(16) Spaces NA D 16 characters general use string

Appendix A

A.13

Index Parameter Data Type Valid Range / Options Default Value Units Store / Mode Description

String_07 VisibleString(16) Spaces NA D 16 characters general use string

String_08 VIsibleString(16) Spaces NA D 16 characters general use string

String_09 VisibleString(16) Spaces NA D 16 characters general use string

String_10 VIsibleString(16) Spaces NA D 16 characters general use string

String_11 VisibleString(32) Spaces NA D 32 characters general use string

String_12 VisibleString(32) Spaces NA D 32 characters general use string

String_13 VisibleString(32) Spaces NA D 32 characters general use string

String_14 VisibleString(32) Spaces NA D 32 characters general use string

String_15 VisibleString(32) Spaces NA D 32 characters general use string

String_16 VisibleString(32) Spaces NA D 32 characters general use string

String_17 VisibleString(32) Spaces NA D 32 characters general use string

String_18 VisibleString(32) Spaces NA D 32 characters general use string

String_19 VisibleString(32) Spaces NA D 32 characters general use string

String_20 VisibleString(32) Spaces NA D 32 characters general use string

UPDATE_EVT DS-73 NA D This alert is generated by any change to the static data.

BLK_ALM DS-72 NA D

The alarm block 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 will set 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.

HI302 – User’s Manual

A.14

HCD – HART Command Definition

Index Parameter Data Type Valid Range / Options Default Value Units Store / Mode Description

BLOCK_STRUCTURE DS-64 NA S

ST_REV Unsigned16 0 None S / RO

TAG_DESC OctString(32) Spaces NA S

STRATEGY Unsigned16 0 None S

ALERT_KEY Unsigned8 1 to 255 0 None S

MODE_BLK DS-69 O/S NA S See Mode’s Parameter

BLK_ERR Bitstring(2) None D / RO

HCD_CODE OctString(5) 0 None S

This code identifies uniquely this configuration and must be formed by combining MAN_ID, DEV_TYPE, UNI_REV, SPEC_REV and SW_REV of the targeted device.

DEVICE_INFO VisibleString(32) Spaces NA S

This parameter stores the device name or any other comment related to this set of command definitions.

CMD_00 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_01 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_02 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_03 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_04 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_05 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_06 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_07 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_08 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_09 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_10 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_11 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_12 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_13 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_14 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_15 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_16 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_17 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_18 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_19 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_20 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_21 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_22 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_23 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_24 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_25 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_26 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_27 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_28 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

Appendix A

A.15

Index Parameter Data Type Valid Range / Options Default Value Units Store / Mode Description

CMD_29 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_30 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_31 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_32 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_33 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_34 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_35 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_36 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_37 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_38 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_39 OctString(44) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_40 OctString(104) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_41 OctString(104) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_42 OctString(104) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_43 OctString(104) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_44 OctString(104) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_45 OctString(104) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_46 OctString(104) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_47 OctString(104) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_48 OctString(104) Request and Response parameters 0 NA S See HART Command configuration parameters.

CMD_49 OctString(104) Request and Response parameters 0 NA S See HART Command configuration parameters.

UPDATE_EVT DS-73 NA D This alert is generated by any change to the static data.

BLK_ALM DS-72 NA D

The alarm block 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 will set 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.

HI302 – User’s Manual

A.16

HWPC – HART Write Parameter Configuration

Index Parameter Data Type Valid Range / Options Default Value Units Store / Mode Description

BLOCK_STRUCTURE DS-64 NA S

ST_REV Unsigned16 0 None S / RO

TAG_DESC OctString(32) Spaces NA S

STRATEGY Unsigned16 0 None S

ALERT_KEY Unsigned8 1 to 255 0 None S

MODE_BLK DS-69 O/S NA S See Mode’s Parameter

BLK_ERR Bitstring(2) None D / RO

HWPC_CODE OctString(5) 0 None S Must be equal to the associated HCD.

WPC_00 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_01 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_02 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_03 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_04 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_05 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_06 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_07 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_08 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_09 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_10 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_11 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_12 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_13 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_14 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_15 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_16 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_17 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_18 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_19 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_20 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_21 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_22 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_23 Unsigned8[20] 0 None S See parameter to command correlation description.

WPC_24 Unsigned8[20] 0 None S See parameter to command correlation description.

UPDATE_EVT DS-73 NA D This alert is generated by any change to the static data.

BLK_ALM DS-72 NA D

The alarm block 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 will set the Active status in the Status attribut e. 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.

Appendix A

A.17

HBC - Hart Bypass Communication

Index Parameter Data Type Valid Range / Options Default Value Units Store / Mode Description

BLOCK_STRUCTURE DS-64 NA S

ST_REV Unsigned16 0 None S / RO

TAG_DESC OctString(32) Spaces NA S

STRATEGY Unsigned16 0 None S

ALERT_KEY Unsigned8 1 to 255 0 None S

MODE_BLK DS-69 O/S NA S See Mode’s Parameter

BLK_ERR Bitstring(2) None D / RO

BYPASS_STATUS Enumerated[8]

0x00: Idle, 0x01: Busy, 0x02: Timeout, 0x03: Response Available

Idle None D / RO This array shows the status of HART channels.

REQUEST_1 OctString(100)

NA D

Write the HART frame into this parameter to send it through the channel 1.

RESPONSE_1 OctString(100)