Hart Driver Manual

HART
ProLinx Gateway HART Master
July 07, 2009
DRIVER MANUAL
Important Installation Instructions

Power, Input and Output (I/O) wiring must be in accordance with Class I, Division 2 wiring methods, Article 501-4 (b) of the National Electrical Code, NFPA 70 for installation in the U.S., or as specified in Section 18-1J2 of the Canadian Electrical Code for installations in Canada, and in accordance with the authority having jurisdiction. The following warnings must be heeded: A B C D WARNING - EXPLOSION HAZARD - SUBSTITUTION OF COMPONENTS MAY IMPAIR SUITABILITY FOR CLASS I, DIV. 2; WARNING - EXPLOSION HAZARD - WHEN IN HAZARDOUS LOCATIONS, TURN OFF POWER BEFORE REPLACING OR WIRING MODULES, and WARNING - EXPLOSION HAZARD - DO NOT DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN SWITCHED OFF OR THE AREA IS KNOWN TO BE NONHAZARDOUS. "THIS DEVICE SHALL BE POWERED BY CLASS 2 OUTPUTS ONLY.
All ProLinx Products

WARNING EXPLOSION HAZARD DO NOT DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN SWITCHED OFF OR THE AREA IS KNOWN TO BE NON-HAZARDOUS. AVERTISSEMENT RISQUE D'EXPLOSION AVANT DE DCONNECTER L'EQUIPMENT, COUPER LE COURANT OU S'ASSURER QUE L'EMPLACEMENT EST DSIGN NON DANGEREUX.
Markings
UL/cUL cUL ISA 12.12.01 Class I, Div 2 Groups A, B, C, D C22.2 No. 213-M1987
243333 CL I Div 2 GPs A, B, C, D Temp Code T5 II 3 G Ex nA nL IIC T5 X 0 C <= Ta <= 60 C
183151
II Equipment intended for above ground use (not for use in mines). 3 Category 3 equipment, investigated for normal operation only. G Equipment protected against explosive gasses.
ProLinx Gateways with Ethernet Ports

Series C ProLinx Gateways with Ethernet ports do NOT include the HTML Web Server. The HTML Web Server must be ordered as an option. This option requires a factory-installed hardware addition. The HTML Web Server now supports: 8 MB file storage for HTML files and associated graphics files (previously limited to 384K) 32K maximum HTML page size (previously limited to 16K)
To upgrade a previously purchased Series C model:

Contact your ProSoft Technology distributor to order the upgrade and obtain a Returned Merchandise Authorization (RMA) to return the unit to ProSoft Technology.
To Order a ProLinx Plus gateway with the -WEB option:

Add -WEB to the standard ProLinx part number. For example, 5201-MNET-MCM-WEB.
Your Feedback Please

We always want you to feel that you made the right decision to use our products. If you have suggestions, comments, compliments or complaints about the product, documentation or support, please write or call us. ProSoft Technology 5201 Truxtun Ave., 3rd Floor Bakersfield, CA 93309 +1 (661) 716-5100 +1 (661) 716-5101 (Fax) www.prosoft-technology.com Copyright ProSoft Technology, Inc. 2009. All Rights Reserved. HART Driver Manual July 07, 2009 ProSoft Technology , ProLinx , inRAx , ProTalk, and RadioLinx are Registered Trademarks of ProSoft Technology, Inc. All other brand or product names are or may be trademarks of, and are used to identify products and services of, their respective owners.
ProSoft Technology Product Documentation

In an effort to conserve paper, ProSoft Technology no longer includes printed manuals with our product shipments. User Manuals, Datasheets, Sample Ladder Files, and Configuration Files are provided on the enclosed CD, and are available at no charge from our web site: www.prosoft-technology.com Printed documentation is available for purchase. Contact ProSoft Technology for pricing and availability. Asia Pacific: +603.7724.2080 Europe, Middle East, Africa: +33 (0) 5.3436.87.20 Latin America: +1.281.298.9109 North America: +1.661.716.5100
Contents Driver Manual
HART ProLinx Gateway HART Master
Contents
Important Installation Instructions ....................................................................................................... 2 Your Feedback Please........................................................................................................................ 3 ProSoft Technology Product Documentation ...................................................................................3
1
1.1 1.2 1.3 1.4 1.5
Start Here
7
System Requirements ...............................................................................................7 Package Contents .....................................................................................................8 Mounting the Module on the DIN-rail ........................................................................8 Connecting Power to the Unit ...................................................................................9 Install ProSoft Configuration Builder Software .......................................................... 9
2
2.1 2.2 2.3
Functional Overview
11
HART Channels ......................................................................................................11 HART Channel Specifications.................................................................................13 Module Internal Database .......................................................................................15
3
3.1 3.2 3.3 3.4 3.5 3.6 3.7
Configure the Gateway
25
Module Entries ........................................................................................................27 Printing a Configuration File ....................................................................................28 [HART PORT x].......................................................................................................28 [HART PORT x COMMANDS] ................................................................................31 Data Map.................................................................................................................39 HART Command Entry Formats .............................................................................41 Downloading a File from PC to the Gateway ..........................................................42
4
4.1 4.2 4.3 4.4 4.5 4.6 4.7
Error/Status Data
43
HART LED Indicators ..............................................................................................43 Viewing Error and Status Data................................................................................43 Configuration Error Word Table ..............................................................................43 Port 0 General Status Data .....................................................................................44 Port 1 General Status Data .....................................................................................44 Error/Status Data Structure .....................................................................................45 Module Error Codes ................................................................................................47
5
5.1 5.2 5.3 5.4 5.5 5.6 5.7
Reference
51
HART Universal Commands ...................................................................................51 HART Common Practice Commands .....................................................................64 ProLinx HART Field Connections ...........................................................................93 HART Status Data Map.........................................................................................102 Module Status Values ...........................................................................................105 Module Status Data Map.......................................................................................107 Virtual Addresses Assigned to Status Data Areas................................................108
ProSoft Technology, Inc. July 7, 2009
Page 5 of 119
HART ProLinx Gateway HART Master 6

6.1 6.2 6.3
Contents Driver Manual 111
Support, Service & Warranty
How to Contact Us: Technical Support................................................................. 111 Return Material Authorization (RMA) Policies and Conditions ............................. 112 LIMITED WARRANTY .......................................................................................... 113
Index
117
Page 6 of 119
Start Here Driver Manual
Start Here
In This Chapter
System Requirements .............................................................................7 Package Contents ................................................................................... 8 Mounting the Module on the DIN-rail ....................................................... 8 Connecting Power to the Unit.................................................................. 9 Install ProSoft Configuration Builder Software......................................... 9
1.1
System Requirements
The ProSoft Configuration Builder for the HART module requires the following minimum hardware and software components: Pentium II 450 MHz minimum. Pentium III 733 MHz (or better) recommended Supported operating systems: o Microsoft Windows XP Professional with Service Pack 1 or 2 o Microsoft Windows 2000 Professional with Service Pack 1, 2, or 3 o Microsoft Windows Server 2003 128 Megabytes of RAM minimum, 256 Megabytes of RAM recommended 100 Megabytes of free hard disk space (or more based on application requirements) 256-color VGA graphics adapter, 800 x 600 minimum resolution (True Color 1024 768 recommended) CD-ROM drive

Page 7 of 119
1.2
Package Contents
The following components are included with your HART module, and are all required for installation and configuration. Important: Before beginning the installation, please verify that all of the following items are present.
Qty. 1 1 Varies Part Name Cable Cable Part Number Cable #15, RS232 Null Modem Part Description ProLinx communication gateway module For RS232 Connection to the CFG Port HART Module PLX-####
Cable #9, Mini-DIN8 For DB9 Connection to Modules Port. One DIN to to DB9 Male DB-9M cable included per configurable serial port Adapter 1454-9F Adapters, DB9 Female to Screw Terminal. For RS422 or RS485 Connections to each serial application port of the Module Contains sample programs, utilities and documentation for the HART module.
Varies
Adapter
ProSoft Solutions CD
If any of these components are missing, please contact ProSoft Technology Support for replacement parts.
1.3
Mounting the Module on the DIN-rail
ProLinx 5000/6000 Series Module
Page 8 of 119
1.4
Connecting Power to the Unit
WARNING: Ensure that you do not reverse polarity when applying power to the module. This will cause damage to the modules power supply.
1.5
Install ProSoft Configuration Builder Software

You must install the ProSoft Configuration Builder (PCB) software in order to configure the module. You can always get the newest version of ProSoft Configuration Builder from the ProSoft Technology web site. To install ProSoft Configuration Builder from the ProSoft Web Site 1 2 3 4 5 Open your web browser and navigate to http://www.prosofttechnology.com/pcb Click the DOWNLOAD HERE link to download the latest version of ProSoft Configuration Builder. Choose "SAVE" or "SAVE FILE" when prompted. Save the file to your Desktop, so that you can find it easily when you have finished downloading. When the download is complete, locate and open the file, and then follow the instructions on your screen to install the program.
If you do not have access to the Internet, you can install ProSoft Configuration Builder from the ProSoft Solutions CD-ROM, included in the package with your module. To install ProSoft Configuration Builder from the Product CD 1 2 Insert the ProSoft Solutions Product CD into the CD drive of your PC. Wait for the startup screen to appear. On the startup screen, click PRODUCT DOCUMENTATION. This action opens an explorer window.
Page 9 of 119
HART ProLinx Gateway HART Master 3 4
Click to open the UTILITIES folder. This folder contains all of the applications and files you will need to set up and configure your module. Double-click the SETUPCONFIGURATIONTOOL folder, double-click the "PCB_*.EXE" file and follow the instructions on your screen to install the software on your PC. The information represented by the "*" character in the file name is the PCB version number and, therefore, subject to change as new versions of PCB are released.
Note: Many of the configuration and maintenance procedures use files and other utilities on the CD-ROM. You may wish to copy the files from the Utilities folder on the CD-ROM to a convenient location on your hard drive.
1.5.1 Using the Help System

Most of the information needed to help you use ProSoft Configuration Builder is provided in a Help System that is always available whenever you are running ProSoft Configuration Builder. The Help System does not require an Internet connection. To view the help pages, start ProSoft Configuration Builder, open the HELP menu, and then choose CONTENTS.
Page 10 of 119
Functional Overview Driver Manual
Functional Overview
In This Chapter
HART Channels .................................................................................... 11 HART Channel Specifications ............................................................... 13 Module Internal Database ..................................................................... 15
The HART Master Protocol exists in 4 and 8 channel implementations. This driver can be configured on an individual channel basis to operate as a HART Master Station and supports all the available HART commands including Universal, Common Practice and Device Specific Commands. Each HART channel is independently configured to interface with the internal database in the module.
HART is a registered trademark of the HART Communication Foundation
2.1
HART Channels
The ProLinx module supports the HART protocol as a Master on up to 8 channels per interface card. Each channel is individually configurable.
The relationship between the port labeling on the front of the ProLinx module and the application is as follows:
Port Label Debug Port 0 Channel 1 Channel 2 Channel 3 Channel 4 Channel 5 Function Debug/configuration Communications Port 0 Hart Port 0 Hart Port 1 Hart Port 2 Hart Port 3 Hart Port 4
Page 11 of 119

Port Label Channel 6 Channel 7 Channel 8 Function Hart Port 5 Hart Port 6 HART Port 7
The HART protocol uses the Bell 202 standard frequency shift keying (FSK) signal to communicate at 1200 baud, superimposed at a low level on the 4 to 20 mA analog measurement signal. Having an average value of zero, an FSK signal causes no interference with the analog value. The HART devices are powered from this 4 to 20 mA analog loop. All HART protocol channels in the ProLinx module generate the Bell 202 FSK signal to communicate in multi-drop mode with up to 15 HART devices and provide up to 300 mA supply for the analog loop in multi-drop mode. Refer to the Reference chapter for ProLinx HART field connection information. User configured commands determine the HART commands to be issued on each channel to the HART devices. Up to 100 commands can be defined for each port. Data read from the devices are placed in the virtual database. Any write requests or device specific command for the HART slave devices are sourced with data from the virtual database or from a configured constant data block. In the commands it can be specified whether to use the HART devices short or long address. If the long address is selected, the device is polled first with short address to ask for the long one. Then the device is polled with the long address. The module does all this processing of the address automatically. The module can be configured to place slave devices that are not responding to commands from the master ports at a lower priority. If the module recognizes that a slave device has failed to respond to a message after the user defined retry count, it will mark the slave as "in communication failure" and set the error delay time to the specified value. Each time that the error delay time expires, the slave will be polled and if the answer is successful, the slave is placed again in an active status. This facility can improve communication throughput on the HART network. In a HART network, it is possible to have two masters. The ProLinx module fully supports the existence of a second master, but it can reduce the throughput on the HART network. This facility is enabled or disabled in the modules configuration. If the ability to have a second master on the network is disabled, then the maximum throughput is achieved.
Page 12 of 119
2.2
HART Channel Specifications

Type Internal Database Communication parameters Specifications 4000 registers (words) available Number of HART Preambles: 2 to 50 Enable Handheld: Y or N Primary Master: Y or N Configurable Parameters per Channel Short Address Retries Long Address Retries Retries After Error Poll Time After Error Number of Commands Slave List Error Pointer HART Commands supported Universal Command Set 00 01 02 03 06 11 12 13 14 15 16 17 18 19 33 34 35 36 37 38 39 40 41 42 43 44 Read Unique Identifier Read Primary Variable Read Current And Percent Of Range Read Dynamic Variables Write Polling Address Read Unique Identifier Associated With Tag Read Message Read Tag Descriptor Date Read PV Sensor Info Read Output Information Read Final Assembly Number Write Message Write Tag Descriptor Date Write Final Assembly Number Read Transmitter Variables Write Damping Value Write Range Values Set Upper Range Value Set Lower Range Value Reset Configuration Changed Flag EEprom Control Enter Exit Fixed Current Mode Perform Transmitter Self Test Perform Master Reset Set Pv Zero Write Pv Units General Parameters (Software Configurable)
Common Practice Command Set
Page 13 of 119

Type Specifications 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 108 109 110 Command List Trim Dac Zero Trim Dac Gain Write Transfer Function Read Additional Transmitter Status Write Pv Sensor Serial Number Read Dynamic Variable Assignments Write Dynamic Variable Assignments Set Transmitter Variable Zero Write Transmitter Variable Units Read Transmitter Variable Information Write Transmitter Variable Damping Value Write Transmitter Variable Sensor Serial Number Read Unit Tag Descriptor Date Write Unit Tag Descriptor Date Write Number Of Response Preambles Write Burst Mode Command Number Burst Mode Control Read All Dynamic Variables
Up to 100 command per channel, each fully configurable for function, slave address, register to/from addressing and word count for Floating Point or Integer Data Error codes returned by the HART protocol available on an individual command basis. In addition, a slave status list is maintained per active channel. User configurable polling of commands, including disabled, continuous, on change of data (write only) and dynamically user or automatic enabled.
Status Data
Polling of command list
The ProLinx HART module supports version 5 of the HART protocol.
Page 14 of 119
2.3
Module Internal Database

Central to the functionality of the module is the internal database. This database is shared between all the ports on the module and is used as a conduit to pass information from one device on one network to one or more devices on another network. This permits data from devices on one communication port to be viewed and controlled by devices on another port. In addition to data from the slave and master ports, status and error information generated by the module can also be mapped into the internal database.
2.3.1 HART Channel Driver Access to Database

The following illustration describes the flow of data between the HART channel drivers and the internal database.
HART Slaves HART Master Databases Other Protocol
Virtual Database
Write Read for Write Command Response Read Read
Write for Read Command
Other Driver
HART Driver Slave Device
Command List
Request
The HART Master driver uses the database in two ways: A read command issued to a slave device by the master driver will return the slave data into the internal database A write command issued to a slave device by the master driver use the data in the internal database to write to the slave device
In addition to data from the master HART channels, detailed status and error information generated by the module can also be mapped into the internal database.
2.3.2 Auto-Polling
This feature is enabled by setting the AUTO-POLL CODE (in the configuration file) to a value of P (point-to-point) or M (multi-drop). If the value N is entered for the parameter, the auto-poll feature is disabled. When the feature is disabled, the channel will only execute the commands enabled in the user command list. When the auto-polling mode is enabled, the module will automatically acquire data from the HART instruments attached to a channel without the use of user commands. If user commands are present and enabled when the feature is enabled, they will also be executed independent of auto-polling.
Page 15 of 119
With the auto-poll feature enabled, the module automatically generates the following HART commands and stores the data in the module's database at the user-specified location:
CMD 0 3 13 14 15 Description Read Unique Identifier Read Current and Four Dynamic Variables Read Tag, Descriptor and Date Read PV Sensor Information Read Output Information
If the unit is set for point-to-point mode, the module will automatically gather the information for the device with the polling address (short address) of zero and place the data into the database. Each device requires a 50-word database area with the format shown in the following table.
DB Byte Offset 0 1 2 3 4 5 6 7 8 9 10 11 to 13 14 Type byte byte byte byte byte byte byte byte byte byte byte byte byte Description Auto-polling command status bits Last first status byte received from device Last second status byte received from device Manufacture ID Code Device Type Code Minimum number of preambles Universal Command Major Rev # Device Revision Level Software Revision Level Hardware Revision Level/Physical Signaling Code Device Flags Device ID Minimum number of preambles to be sent with the response message from the slave to the master. Maximum number of device variables Configuration Change Counter Extended Field Device Status Primary variable units code Secondary variable units code Tertiary variable units code Quaternary variable units code Tag name Descriptor Byte Cnt 1 1 1 1 1 1 1 1 1 1 1 3 1 Data Source App Resp Resp CMD 0 CMD 0 CMD 0 CMD 0 CMD 0 CMD 0 CMD 0 CMD 0 CMD 0 CMD 0 Use of Data Status Status Status LongAddress LongAddress Msgconstruction Msgchoice Info Info Info Info Long Address
15 16 to 17 18 19 20 21 22 23 to 30 31 to 46
byte word byte byte byte byte byte byte byte
1 2 1 1 1 1 1 8 16
CMD 0 CMD 0 CMD 0 CMD 3 CMD 3 CMD 3 CMD 3 CMD 13 CMD 13
Info Info Info Cfg Cfg Cfg Cfg Info Info
Page 16 of 119

DB Byte Offset 47 to 49 50 to 52 53 54 55 56 57 58 59 Type byte byte byte byte byte byte byte byte byte Description Tag/Descriptor data Transducer serial number Transducer limits and min span units code PV alarm selection code PV transfer function code PV upper and lower range value units code Write protection code Private label distributor code PV analogchannel flag TOTAL BYTE COUNT TOTAL WORD COUNT DB Byte Offset 60 to 63 64 to 67 68 to 71 72 to 75 76 to 79 80 to 83 84 to 87 88 to 91 92 to 95 96 to 99 Type float float float float float float float float float float Description Primary variable value Secondary variable value Tertiary variable value Quaternary variable value Upper transducer limit Lower transducer limit Minimum span PV upper range value PV lower range value PV damping value (in seconds) TOTAL FLOAT BYTE COUNT TOTAL FLOAT WORD COUNT DB Regs/Device Max DB Regs/channel for 15 Devices Max DB Regs for HART Card Byte Cnt 3 3 1 1 1 1 1 1 1 60 30 Byte Cnt 4 4 4 4 4 4 4 4 4 4 40 20 50 750 3000 Data Source CMD 3 CMD 3 CMD 3 CMD 3 CMD 14 CMD 14 CMD 14 CMD 15 CMD 15 CMD 15 Data Source CMD 13 CMD 14 CMD 14 CMD 15 CMD 15 CMD 15 CMD 15 CMD 15 CMD 15

Use of Data Info Info Info Info Info Info Status Info Info
Use of Data Status Status Status Status Cfg Cfg Cfg Cfg Cfg Cfg
The following table defines the auto-polling command status bits:

Bit # 0 1 2 3 4 5 6 7 Description Long Address Set (command 0 successful) Command 13 successful (configuration) Command 14 successful (configuration) Command 15 successful (configuration) Command 3 successful (data polling) Reserved Reserved Reserved
Page 17 of 119
HART ProLinx Gateway HART Master The following topics describe the modes of module operation. Auto-Poll Disabled Mode
If the auto-polling feature is disabled (Auto-Poll Code = N), the module functions as shown in the following diagram:
Only the user commands are executed and all data is placed in and sourced from the module's internal database. The user is responsible for constructing all commands to control and monitor the instruments attached to the channel. Point-to-Point Mode Important: If the HART device address is 0 you must configure the channel for Point-to-Point mode.
In point-to-point mode, the module only polls for a single instrument with a polling address of zero. When the instrument is found by the channel, it continuously polls for the data using command 3. Occasionally, it will poll for the configuration information for the device. This is accomplished with HART commands 13, 14 and 15. Less frequently, the channel will perform a HART command 0 request to see if any of the data for the instrument has changed. If communications is lost with the device, the module will try to establish communications with the device using command 0. If user commands are present and enabled, they will be executed after each data poll.
Page 18 of 119
When the point-to-point mode of auto-polling is enabled (Auto-Poll Code = P), the following diagram applies to the channel operation:
Page 19 of 119
HART ProLinx Gateway HART Master Multi-drop Mode
Important: If the HART device address is between 1 and 15, you must configure the channel for multi-drop mode. If the unit is set for multi-drop mode, the module will poll each unit attached to the channel starting with polling address 1. The parameter MAX DEVICE COUNT in the configuration determines the maximum slave address number to be polled in multi-drop mode. For example, if the MAX DEVICE COUNT parameter is set to 3, the channel will poll for polling addresses 1, 2, and 3. It is important when assigning the device polling addresses for instruments on a channel to start with 1 and successfully increase the value by one until the last instrument is assigned an address. If you set the MAX DEVICE COUNT parameter to 2, and assign the two instruments addresses 1 and 15, the polling address 15 will never be used (only addresses 1 and 2). Therefore, the second instrument will never be polled and will be in communication failure. Up to 15 instruments can be assigned to a single channel (polling address 1 to 15).
Page 20 of 119
If the module is configured for multi-drop auto-polling (Auto-Poll Code = M), the following diagram applies:
In multi-drop mode, the channel will poll for instruments 1 to the value set in the MAX DEVICE COUNT parameter. For each device found, it will continuously poll for data using command 3. After a certain number of iterations, the HART Driver will ready the configuration data for the next device (if there is one). Each time configuration information is acquired, it will be for a different slave device if more than 1 slave is recognized by the channel. Less frequently, the channel will poll for devices not found in the original search of the network using HART command 0. If communications is lost with all devices, the module will try to establish communications with the devices using command 0. If user commands are present and enabled, they will be executed after the data polling of the devices.
Page 21 of 119
HART ProLinx Gateway HART Master Multi-drop Mode Example:
The intent is to show when using Multi-drop mode how the Auto-Poll DB Address and Max Device Count parameters should be used. If the configuration file sets the following parameters:
Parameter DB Address Status Auto-Poll DB Address Max Device Count DB Address Status Auto-Poll DB Address Max Device Count DB Address Status Auto-Poll DB Address Max Device Count DB Address Status Auto-Poll DB Address Max Device Count Value 3660 400 15 3661 1200 15 3662 2000 15 3663 2800 15 [HART PORT 3] [HART PORT 2] [HART PORT 1] [HART PORT 0] Config File Section
The HART database has the following structure.
The configuration file for this example shows that when the MAX Device Address parameter is configured as 15, the module will reserve 800 words for each channel (15 devices x 50 words each) even though not all devices may be present on the network.
Page 22 of 119
2.3.3 HART Command List

The HART Command List specifies the commands to be executed to the HART devices connected to a channel. A HART command can be seen as an outgoing message to the HART devices that provides Write Data for a specific command or a response message that carries process data (Read Data) back to the module. The ProLinx module supports three kinds of data blocks in the Universal and Common Practice commands. These data blocks are: Integers IEEE 754 Floating Point Numbers (32 bits) Packed ASCII character strings
The Packed ASCII character strings are unpacked and placed with the integers data block. For all commands, it is possible to select where the Write Data comes from; it can be in the modules internal database or it can be configured as a fixed data block in the command. For response messages from HART devices, it is possible to configure where the Floating Point Data and Integer Data will be placed in the modules internal database, but this is only possible for the Universal and Common Practice commands. In the case of Device Specific commands, all the Read Data is placed in the Integer data section. See HART Command Support for a listing of supported HART commands.
Page 23 of 119
Page 24 of 119
Configure the Gateway Driver Manual
Configure the Gateway

In This Chapter
Module Entries ...................................................................................... 27 Printing a Configuration File .................................................................. 28 [HART PORT x]..................................................................................... 28 [HART PORT x COMMANDS]............................................................... 31 Data Map............................................................................................... 39 HART Command Entry Formats............................................................ 41 Downloading a File from PC to the Gateway......................................... 42
To begin, start PROSOFT CONFIGURATION BUILDER (PCB).
Page 25 of 119
If you have used other Windows configuration tools before, you will find the screen layout familiar. PCBs window consists of a tree view on the left, and an information pane and a configuration pane on the right side of the window. When you first start PCB, the tree view consists of folders for DEFAULT PROJECT and DEFAULT LOCATION, with a DEFAULT MODULE in the Default Location folder. The following illustration shows the PCB window with a new project.
Page 26 of 119
Configure the Gateway Driver Manual Your first task is to add the HART module to the project. 1 2
Use the mouse to select DEFAULT MODULE in the tree view, and then click the right mouse button to open a shortcut menu. On the shortcut menu, choose CHOOSE MODULE TYPE. This action opens the CHOOSE MODULE TYPE dialog box.
3 4
In the PRODUCT LINE FILTER area of the dialog box, select the ProLinx Series (4000, 5000, or 6000) for your gateway. In the SELECT MODULE TYPE dropdown list, select your gateway, and then click OK to save your settings and return to the ProSoft Configuration Builder window.
3.1
Module Entries
To configure module parameters 1 2 3 4 Click on the plus sign next to the icon to expand module information.
icon to open the EDIT dialog box. Double-click the To edit a parameter, select the parameter in the left pane and make your changes in the right pane. Click OK to save your changes.
Page 27 of 119
3.2
Printing a Configuration File

To print a configuration file: 1 2 3 4 Select the MODULE icon, and then click the right mouse button to open a shortcut menu. On the shortcut menu, choose VIEW CONFIGURATION. This action opens the VIEW CONFIGURATION window. On the VIEW CONFIGURATION window, open the FILE menu, and choose PRINT. This action opens the PRINT dialog box. On the PRINT dialog box, choose the printer to use from the dropdown list, select printing options, and then click OK.
3.3
[HART PORT x]
The [HART PORT 0], [HART PORT 1], [HART PORT 2], [HART PORT 3] [HART PORT 4], [HART PORT 5], [HART PORT 6] and [HART PORT 7] sections of the configuration set the HART channel communication parameters, define the protocol specifics and set the command list parameters. The parameters are the same for all 8 sections. The command list for each HART channel is entered in a different section in the file.
3.3.1 Enabled
Y or N This parameter enables or disables the specific HART channel. If the parameter is set to "Y", the channel will be utilized. If set to "N", the channel will not be used.
Page 28 of 119
3.3.2 Preambles
2 to 50 This parameter defines the number of 0xFF characters (preambles) that will be placed at the start of each HART frames.
3.3.3 Primary Master

Yes or No This parameter specifies the Link Quiet / Slave Timeout. If set to Yes, the selected Link Quiet / Slave Timeout is 305 milliseconds which corresponds to the Primary Master. If set to No, then this time is 380 milliseconds which corresponds to the Secondary Master.
3.3.4 Retry Count

0 to 10 This parameter sets the number of retries for a command if the command response is not received from the slave device. This parameter is normally set to a value of 3. The module will accept values of 0 to 10.
3.3.5 DB Address Status

-1, 0 to 3999 This parameter is utilized to set the database address in the module where the status word for the channel will be placed. If the parameter is set to -1, the word value will not be placed in the database. If a value from 0 to 3999 is set for the parameter, the status word for the channel will be placed at the specified database offset. This word is bit mapped with each bit representing a slave device. The bit will be set if slave device has a communication error.
3.3.6 Command Count

0 to 99 This parameter sets the number of user commands to be utilized. The first command in the list is always reserved for the auto-poll command so the user should configure this value considering one command for the auto-poll. For example, if the user configures two commands, the command count parameter should be set as 3. This parameter can be set from 0 to 99. If the parameter is set to a value other than 0, commands should be present in the [HART PORT x COMMANDS] section.
Page 29 of 119
3.3.7 Auto-Poll Code

P, M or N This parameter sets the auto-poll mode of the channel. If the parameter is set to P, the module will automatically poll device 0 in point-to-point mode. If the parameter is set to M, the module will automatically poll devices 1 to n (n=value of parameter Max Device Count). If the parameter is set to N, the auto-polling option will be disabled and only commands in the command list will be utilized for the channel. In the auto-poll mode, the module will automatically execute HART commands 0, 3, 13, 14 and 15.
3.3.8 Auto-Poll DB Address

0 to 3700 This parameter sets the starting address for the data obtained by the auto-poll feature. Each device on a channel requires 50 words in the database. The data area selected must not overlap any portion of the database used by other channels or the module.
3.3.9 Auto-Poll Swap Float

0 to 3 This parameter swaps the floating-point data values received by the auto-poll feature.
Swap Code 0 1 2 3 Description None - No Change is made in the byte ordering (1234 = 1234) Words - The words are swapped (1234=3412) Words & Bytes - The words are swapped then the bytes in each word are swapped (1234=4321) Bytes - The bytes in each word are swapped (1234=2143)
Depending on the host processor using the data, the proper swap code must be utilized to present the data in the correct format.
3.3.10 Max Device Count

1 to 15 This parameter sets the maximum number of slave devices to be utilized for the auto-poll feature. In point-to-point mode, the parameter should be set to a value of 1. In multi-drop mode, the parameter should be set from 1 to 15 to represent the number of slave devices attached to the channel.
Page 30 of 119
3.4
[HART PORT x COMMANDS]

The [HART PORT x COMMANDS] sections of the CFG file set the user defined HART channel command lists. These lists poll slave devices attached to the HART channels. The module supports numerous commands.
3.4.1 Command List Overview

The HART module uses a command list to interface with HART slave devices. The commands in the list specify the slave device to be addressed the function to be performed (read or write) the registers in the internal database to be associated with the device data.
There is a separate command list for each HART channel, with up to 99 commands allowed per channel. The command list is processed from top (command #0) to bottom. A poll interval parameter is associated with each command to specify a minimum delay time in seconds between the issuance of a command. For example, a poll interval of 10 executes the command no more frequently than every 10 seconds. Write commands have a special feature, as they can be set to execute only if the data in the write command changes. If the register data values in the command have not changed since the command was last issued, the command will not be executed. If the data in the command has changed since the command was last issued, the command will be executed. Use of this feature can lighten the load on the HART network. In order to implement this feature, set the enable code for the command to a value of 2.
Page 31 of 119
The module supports all the Universal (page 51) and Common Practice (page 64) commands, as well as device specific commands. A Device Specific command is supported without any translation of the data.
3.4.2 HART Command Entry Formats

Refer to HART Command Support (page 34) for a complete discussion of the HART commands supported by the module, and the structure and content of the data returned for each command. The following illustration shows a command list section of the CFG file:
3.4.3 Enable
0, 1, 2, 3, 4, 5 This field defines whether the command is to be executed and under what conditions.
Code 0 Description The command is disabled and will not be executed in the normal polling sequence. This can be used to process a command from a bursting slave device. Causes the command to be executed each scan of the command list if the Poll Interval Time is set to zero. If the Poll Interval time is set, the command will be executed, when the interval timer expires. The command will execute only if the internal data associated with the command changes. This value is valid only when there is a specified "Write DB Address" (see below) with a non zero byte count for write commands. The HART module will send the command if either the HART module OR the HART device is powered up. This is mainly used for configuration of HART devices on startup.
Page 32 of 119

Code 4 Description
Places the command in enabled mode. This option is valid only if there is a specified "Enabled DB Address" (see below). If the Virtual Database word specified in "Enabled DB Address" has "-1" the command will be executed otherwise it will not. Places the command in one shot enabled mode. This option is valid only if there is a specified "Enabled DB Address" (see below). If the Virtual Database word specified in "Enabled DB Address" has a value of "-1" the command will be executed otherwise it will not. When the command has been successful the Virtual Database word specified in "Enabled DB Address" will be written with "0", so the command will be executed only once.
3.4.4 Float DB Address

0 to 3998 This field specifies the internal database register where the floating point values returned by the command will be placed.
3.4.5 Poll Interval

0 to 65535 This parameter specifies the minimum interval to execute continuous commands (Enable code of 1). The parameter is entered in units of seconds. Therefore, if a value of 10 is entered for a command, the command will execute no more frequently than every 10 seconds.
3.4.6 FP Word Count

-1 to 125 This parameter specifies the number of words from the floating point data returned by a HART command that will be placed on the Virtual Database. If this parameter is 0 no data will be written to the Database. If this parameter is -1 then all the floating point data will be written in the integer block of data. Special care should be taken with this number, because is a word count and a floating point value is 2 words long. For example if you execute a HART command 3 which takes 5 floating point values from the device, you should place a word count of 10 words.
3.4.7 Swap Code

0, 1, 2, 3 This parameter defines the byte order of each four-byte group of data received. This parameter is helpful when dealing with floating-point or other multi-register values, as there is no standard byte order for storing these data types. The following table describes the values and their associated operations:
Page 33 of 119

Swap Code 0 1 2 3 Description None - No Change is made in the byte ordering (1234 = 1234) Words - The words are swapped (1234=3412)
Words & Bytes - The words are swapped then the bytes in each word are swapped (1234=4321) Bytes - The bytes in each word are swapped (1234=2143)
3.4.8 Short Address

1 to 15 This parameter specifies the HART slave node address on the network to be considered. Values of 1 to 15 are permitted. If the device to be addressed only accepts long address, then the parameter "Use Long" should be selected so the module can ask for the long address with the short one and then execute the command.
3.4.9 Function Code

0 to 255 This parameter specifies the HART function to be executed. Any HART function can be executed, even device specific ones, but only supported commands will return formatted data and classified in floating point data and integer data. Commands Supported by the Module The format of each command in the list is independent on the function being executed. All parameters in the command table must be entered. Only one parameter is optional, the Fixed Data field, which contains data to be sent to a HART device. The tables below list the functions supported by the module: HART Universal Commands Set
Command 00 01 02 03 06 07 08 09 11 12 13 14 15 Definition Read Unique Identifier Read Primary Variable Read Current And Percent Of Range Read Dynamic Variables Write Polling Address Read Loop Configuration Read Dynamic Variable Classifications Read Device Variables with Status Read Unique Identifier Associated With Tag Read Message Read Tag Descriptor Date Read PV Sensor Info Read Output Information
Page 34 of 119

Command 16 17 18 19 20 21 22 Definition Read Final Assembly Number Write Message Write Tag Descriptor Date Write Final Assembly Number Read Long Tag Read Unique Identifier Associated With Long Tag Write Long Tag
HART Common Practice Commands Set

Command 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 Definition Read Transmitter Variables Write Damping Value Write Range Values Set Upper Range Value Set Lower Range Value Reset Configuration Changed Flag EEPROM Control Enter Exit Fixed Current Mode Perform Transmitter Self Test Perform Master Reset Set PV Zero Write PV Units Trim DAC Zero Trim DAC Gain Write Transfer Function Read Additional Transmitter Status Write PV Sensor Serial Number Read Dynamic Variable Assignments Write Dynamic Variable Assignments Set Transmitter Variable Zero Write Transmitter Variable Units Read Transmitter Variable Information Write Transmitter Variable Damping Value Write Transmitter Variable Sensor Serial Number Read Unit Tag Descriptor Date Write Unit Tag Descriptor Date Write Number Of Response Preambles Read Analog Channel and Percent of Range Read Dynamic Variables and PV Analog Ch Read Analog Channels Read Analog Channel Information
Page 35 of 119

Command 64 65 66 67 68 69 70 71 72 73 74 75 76 79 80 81 82 83 105 106 107 108 109 110 Definition Write Analog Channel Additional Damping Value Write Analog Channel Range Values Enter/Exit Fixed Analog Channel Mode Trim Analog Channel Zero Trim Analog Channel Gain Write Analog Channel Transfer Function Read Analog Channel Endpoint Values Lock Device Squawk Find Device Read I/O System Capabilities Poll Sub-Device Read Lock Device State Write Device Variable Read Device Variable Trim Points Read Device Variable Trim Guidelines Write Device Variable Trim Point Reset Device Variable Trim Read Burst Mode Configuration Flush Delayed Responses Write Burst Device Variables Write Burst Mode Command Number Burst Mode Control Read All Dynamic Variables
3.4.10 Int. DB Address

0 to 3999 This field specifies the internal database register where the integer or packed ASCII string values returned by the command will be placed. If the Floating Point Word Count parameter is "-1", then all the data returned by the HART command will be placed in this address without any formatting.
3.4.11 Int Word Count

0 to 125 This parameter specifies the number of words from the integer or packed ASCII string data returned by a HART command that will be placed on the Virtual Database. If this parameter is "0", no data will be written to the Database.
Page 36 of 119
3.4.12 Swap Code

3.4.13 Use Long

0 or 1 This parameter defines if the command will be executed with short or long address. If the value is "0", then the configured command will be executed using the Short Address specified. If the value is "1" then the specified Short Address will be used only to ask for the long address and that will be used to execute the configured command.
3.4.14 Enable DB Address

0 to 3999 This field specifies the internal database register to be used to enable the execution of a command. This parameter is only used if "Enable" is "4" or "5". If the value of this database register is "-1", then the command will be executed, otherwise it will not. If the "Enable" value is "5", then after the successful execution of the command this value will become "0"
3.4.15 Done DB Address

-1 to 3999 This field specifies the internal database register to be used to signal the successful execution of a command. When a command is successfully executed a "-1" is written to this register. This "Done DB Address" can be shared with the "Enable DB Address" of another command to do a chained command execution.
3.4.16 Write DB Address

-1 to 3999
Page 37 of 119
This field specifies the internal database register to be as a source of data for HART command which includes data. It is possible to include data with every HART command, but it depends of the command and of the device if it will accept this data. If this value is "-1", it indicates that there will not be data with the command or that it will not come from database.
3.4.17 Swap Code

3.4.18 Byte Count

0 to 250 This parameter specifies the number of bytes to be sent to a HART device in the command. If the command has no data then this value should be "0". If the value of this field is different of "0" and "Write DB Address" is different of "1" then the data for the command will be taken from the Virtual Database. If the value of this field is different of "0" and "Write DB Address" is "-1" then the data for the command will be from the "Fixed Data" field for the command.
3.4.19 Fixed Data

Up to 250 HEX values separated by space This parameter is a string of HEX values to be sent with the HART command. There should be at least the number of bytes specified in the "Byte Count" parameter. The bytes should be written in hexadecimal format and separated by a space. This data will be sent if the Parameter "Write DB Address" is "-1" and "Byte Count" is greater than "0", and it will be sent in the same order that they are written.
Page 38 of 119
3.5
Data Map
The [DATA MAP] section allows you to copy data between areas in the modules internal database. You can copy to 100 registers at a time, and you can configure up to 200 separate copy commands. For example, you can copy data from the error or status tables in upper memory to internal database registers in the User Data memory area. You can also rearrange the byte and/or word order during the copy process so that data such as floating-point values can be converted to the correct format for a specific protocol. You can also use the Data Map to condense widely dispersed data into one contiguous data block, making it easier to access.
Page 39 of 119
3.5.1 Internal Database Re-mapping

Depending on the application, you may need to copy data from one section of the modules internal database to another section. The [Data Map] section of the CFG file allows a user to selectively copy data registers, one register up to 100 registers at a time, from one internal database to another. Up to 200 entries can be made in the [Data Map] section, providing a wide and powerful range of functionality.
3.5.2 From Address

0 to 3999 This field specifies the internal database register to copy from. This address can range from the Data area as well as the Status Data Area of the product
3.5.3 To Address
0 to 3999 The destination for the copy is always going to be the Register Data area.
3.5.4 Register Count

1 to 100 This parameter specifies the number of registers to copy.
3.5.5 Swap Code

0, 1, 2, 3 There may be a need to swap the order of the bytes in the registers during the copy process in order to change from alignment of bytes between dissimilar protocols. This parameter is helpful when dealing with floating-point or other multi-register values, as there is no standard method of storage of these data types in slave devices. The following table defines the values and their associated operations:
Page 40 of 119
3.5.6 Delay Preset

This parameter sets an interval for each [Data Map] copy operation. The value you put for the Delay Preset is not a fixed amount of time. It is the number of firmware scans that must transpire between copy operations. The firmware scan cycle can take a variable amount of time, depending on the level of activity of the protocol drivers running on the ProLinx gateway and the level of activity on the gateways communications ports. Each firmware scan can take from 1 to several milliseconds to complete. Therefore, [Data Map] copy operations cannot be expected to happen at regular intervals. If multiple copy operations (several rows in the [Data map] section) happen too frequently or all happen in the same update interval, they could delay the process scan of the gateway protocols, which could result in slow data updates or missed data on communications ports. To avoid these potential problems, you should set the Delay Preset to different values for each row in the [Data Map] section and set them to higher, rather than lower, numbers. For example, Delay Preset values below 1000 could begin to cause a noticeable delay in data updates through the communications ports. And you should not set all Delay Presets to the same value. Instead, use different values for each row in the [Data Map] such as 1000, 1001, and 1002 or any other different Delay Preset values you like. This will prevent the copies from happening concurrently and prevent possible process scan delays.
3.6
HART Command Entry Formats

Refer to HART Command Support (page 34) for a complete discussion of the HART commands supported by the module, and the structure and content of the data returned for each command. The following illustration shows a command list section of the CFG file:
Page 41 of 119
3.7
Downloading a File from PC to the Gateway

To download a file from the Configuration Builder to the gateway: 1 Verify that your PC is connected to the gateway with a null-modem serial cable connected to the serial port on your PC and the serial port on the gateway Open the PROJECT menu, and then choose MODULE. On the MODULE menu, choose DOWNLOAD. Wait while ProSoft Configuration scans for communication ports on your PC. When the scan is complete, the DOWNLOAD dialog box opens.
2 3
4 5
Select the port to use for the download. Click the DOWNLOAD button.
Page 42 of 119
Error/Status Data Driver Manual
Error/Status Data
In This Chapter
HART LED Indicators ............................................................................ 43 Viewing Error and Status Data .............................................................. 43 Configuration Error Word Table............................................................. 43 Port 0 General Status Data ................................................................... 44 Port 1 General Status Data ................................................................... 44 Error/Status Data Structure ................................................................... 45 Module Error Codes .............................................................................. 47
The module error/status data areas are discussed in this section. The module contains three areas related to this data. The user defines the location of these data sets in the virtual database of the module. The error/status data contains module data, the six command error list data sets contain the errors associated with each respective command list and the four slave status list tables contain the communication status of each ports slave devices.
4.1
HART LED Indicators

LED CH1 to CH4 State Green Flashing Off Description The module either sending or receiving data over that channel. The module is waiting to receive data on that channel.
4.2
Viewing Error and Status Data

The following topics list the register addresses that contain error and status data. You use the Database View option to view the contents of these registers. Refer to the ProLinx Reference Guide for detailed information on viewing error and status registers.
4.3
Configuration Error Word Table 4.3.1 HART Configuration Error Word

Bit 0 1 2 Code 0x0001 0x0002 0x0004 Description Enabled not set to Y or N Enable Handheld not set to Y or N Primary Master not set to Y or N
Page 43 of 119

Bit 3 4 5 6 7 8 9 10 11 12 13 14 15 Code 0x0008 0x0010 0x0020 0x0040 0x0080 0x0100 0x0200 0x0400 0x0800 0x1000 0x2000 0x4000 0x8000 Description Invalid Preambles (1 to 50) Invalid Short Address Retries (0 to 50) Invalid Long Address Retries (0 to 50) Invalid Retries After Error (0 to 50) Invalid Poll Time After Error (0 to 10000) Invalid DB Address Status Invalid Command Count Memory Error in allocating commands Memory Error in allocating command fixed data Memory Error in allocating TX/RX buffers HART Board not found Cannot initialize HART channel reserved
4.4
Port 0 General Status Data

Status Register 10700 10701 10702 10703 10704 10705 10706 10707 10708 10709 10710 10711 to 10799 Description State Comm State Device Status (bit mapped) Device Poll List (bit mapped) Device With Long Address (bit mapped) Current Command Command Request Count Command Response Count Configuration Error Word Current Error Code Last Error Code No Valid Data
4.5
Port 1 General Status Data

Status Register 10900 10901 10902 10903 10904 10905 10906 10907 Description State Comm State Device Status (bit mapped) Device Poll List (bit mapped) Device With Long Address (bit mapped) Current Command Command Request Count Command Response Count
Page 44 of 119

Status Register 10908 10909 10910 10911 to 10999 Description Configuration Error Word Current Error Code Last Error Code No Valid Data
4.5.1 General Status Data (Ports 2 through 7)

The following table lists the register address ranges for ports 2 through 7. The register descriptions are the same as listed in the previous table.
Port 2 3 4 5 6 7 Address Range 11100 to 11299 11300 to 11499 11500 to 11699 11700 to 11899 11900 to 12099 12100 to 12299
4.6
Error/Status Data Structure

The error/status data table is located at the virtual address assigned by the user. If the address is set to -1 or the frequency parameter is set to 0, the data will not be placed in the database. It will only be available through the Configuration/Debug Port. If valid address and frequency values are assigned, the module will update the data area. The data area will be initialized with zeros whenever the processor is initialized. This occurs during a cold-start (power-on), reset (reset push-button pressed) or a warm-boot operation (commanded or loading of new configuration). The following table shows the structure of the 44-word error/status data area.
Word 16 17 18 19 20 21 22 23 24 25 26 Description Number of Command Requests Number of Command Responses Devices in Poll Devices Status Configuration Error Current Error Last Error Number of Command Requests Number of Command Responses Devices in Poll Devices Status HART CHANNEL 0
HART CHANNEL 1
Page 45 of 119

Word 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 Description Configuration Error Current Error Last Error Number of Command Requests Number of Command Responses Devices in Poll Devices Status Configuration Error Current Error Last Error Number of Command Requests Number of Command Responses Devices in Poll Devices Status Configuration Error Current Error Last Error
HART CHANNEL 2
HART CHANNEL 3
4.6.1 HART Command List Error Data

Each command in the command list for each HART channel has a word value for a status/error code. This error data list can be read using the Configuration/Debug Port and can be placed in the modules internal database. Accessing the Debug capabilities of the module is accomplished easily by connecting a PC to the Debug port and loading a terminal program such as ProSoft Configuration Builder or Hyperterminal. This status/error code is the first word of the Integer Data Block returned from every HART command executed. This word has information about the execution of the command by the HART device. Refer to later sections containing Error Codes to interpret the status/error codes present in the integer data area. Port 0 Command List Errors
Status Register 10800 10899 Description Command List Errors
Page 46 of 119
Error/Status Data Driver Manual Port 1 Command List Errors
Port 1 Command List errors are found in registers 11000 through 11099.
4.6.2 Slave List Status

The configuration parameter "DB Address Status" defines the register address in the virtual database where the status data for each HART channel will be placed. This word has one bit for each HART device and if this bit is in "1" it means that the corresponding HART device is not answering to the poll.
Bit HART Device 15 15 14 14 13 13 12 12 11 11 10 10 9 9 8 8 7 7 6 6 5 5 4 4 3 3 2 2 1 1 0 Res
The bit 0 of the "Slave List Status" is reserved for future use and is always 0.
4.7
Module Error Codes

The module error codes are listed in this section. Error codes returned from the HART device are placed at the first word of the integer data block in the Virtual Database. The error codes are formatted in the word as follows: If the mostsignificant bit of the word contains "1", then the most significant byte has a communication error code. The least-significant byte of the word will contain "0". If the most-significant bit of the word contains "0", the most significant byte contains a command error code. In this case, the least-significant byte contains a device malfunction information. If this word value is "-1" (or 0xFFFF), it means that the command timed out. Use the error codes returned for each command in the list to determine the success or failure of the command. If the command fails, use the error code to determine the cause of failure.
4.7.1 Protocol Error Codes

These are error codes that are part of the HART protocol. The standard HART error codes are shown in the following tables: Error Code Word First Byte
7 6 5 4 3 2 1 0 7
Second Byte
6 5 4 3 2 1 0
Bit 7 of First Byte = 1 COMMUNICATION ERROR First Byte Bit 6 Bit 5 Bit 4 Parity Error Overrun Error Framing Error
Page 47 of 119

Bit 7 of First Byte = 1 COMMUNICATION ERROR Bit 3 Bit 2 Bit 1 Bit 0 Second Byte Bit 0 To Bit 7 All 0 Checksum Error Reserved Rx Buffer Overflow Undefined
Bit 7 of First Byte = 0 Command Error First Byte Bits 6 To 0 (not Bit-mapped): 0 1 2 3 4 5 6 7 8 to 15 16 32 64 Second Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Device Malfunction Configuration Changed Cold Start Unused Output Current Fixed Analog Output Saturated Variable (not Primary) Out Of Limits Primary Variable Out of Limits No Error Undefined Invalid Selection Passed Parameter Too Large Passed Parameter Too Small Too Few Data Bytes Received Transmitter-specific Command Error In Write-protect Mode Command Specific Errors (see Below) Access Restricted Device Is Busy Command Not Implemented
Page 48 of 119

Command Specific Errors 8 Update Failed Update In Progress Set to Nearest Possible Value 9 Applied Process Too High Lower Range Value Too High Not in Fixed Current Mode 10 Applied Process Too Low Lower Range Value Too Low Multi-drop Not Supported 11 In Multi-drop Mode
Invalid Transmitter Variable Code Upper Range Value Too High 12 13 14 Invalid Unit Code Upper Range Value Too Low Both Range Values Out of Limits Pushed Upper Range Value Over Limit Span Too Small
Page 49 of 119
Page 50 of 119
Reference Driver Manual
Reference
In This Chapter
HART Universal Commands ................................................................. 51 HART Common Practice Commands .................................................... 64 ProLinx HART Field Connections.......................................................... 93 HART Status Data Map ....................................................................... 102 Module Status Values ......................................................................... 105 Module Status Data Map ..................................................................... 107 Virtual Addresses Assigned to Status Data Areas............................... 108
5.1
HART Universal Commands
COMMAND 00 - Read Unique Identifier

Description This command gets the long address of the HART device plus other manufacturer information like Manufacturer ID, Device Type Code, Software Revision, Hardware Revision, and so on. Write Parameters NONE Floating Point Data Returned NONE Integer Data Returned
Word 0 1 2 3 4 5 6 High Byte STATUS WORD Constant "254" Manufacturer Device Type Code Universal Command Revision Software Revision Device Function Flags Device ID Number 2 Manufacturer Identification Code Number of Preambles Transmitter Specific Command Revision Hardware Revision Device ID Number 1 Device ID Number 3 Low Byte
Page 51 of 119
COMMAND 01 - Read Primary Variable

Description This command gets the device Primary Variable and the Primary Variable Units Write Parameters NONE Floating Point Data Returned
Word 0 1 High Byte Primary Variable Value Low Byte
Integer Data Returned

Word 0 1 High Byte STATUS WORD Primary Variable Units Code 0 Low Byte
Page 52 of 119
COMMAND 02 - Read Current And Percent Of Range

Description This command gets the current of the loop that is forced by the HART device and the Percent of Range of the Current. Write Parameters NONE Floating Point Data Returned
Word 0 1 2 3 Percent of Range High Byte Current (mA) Low Byte

Word 0 High Byte STATUS WORD Low Byte
Page 53 of 119
COMMAND 03 - Read Dynamic Variables

Description This command gets the current and four (predefined) dynamic Variables. Write Parameters NONE Floating Point Data Returned
Word 0 1 2 3 4 5 6 7 8 9 Fourth Variable Third Variable Second Variable Primary Variable High Byte Current (mA) Low Byte

Word 0 1 2 High Byte STATUS WORD Primary Variable Units Code Third Variable Units Code Second Variable Units Code Fourth Variable Units Code Low Byte
Page 54 of 119
COMMAND 06 - Write Polling Address

Description This command sets the polling address of a HART device. Extreme care should be taken when you use this command because you can loose the communication with the device. Write Parameters
Word 0 High Byte Polling Address Low Byte Polling Address
Floating Point Data Returned NONE Integer Data Returned

Word 0 1 High Byte STATUS WORD Polling Address 0 Low Byte
Page 55 of 119
COMMAND 12 - Read Message

Description This command reads an ASCII message contained in the HART Device and written by the Write Message command 17. Write Parameters NONE Floating Point Data Returned NONE Integer Data Returned
Word 0 1 2 . . . 14 15 High Byte STATUS WORD Message ASCII Character 0 Message ASCII Character 2 . . . Message ASCII Character 28 Message ASCII Character 30 Message ASCII Character 29 Message ASCII Character 31 Message ASCII Character 1 Message ASCII Character 3 Low Byte
Page 56 of 119
COMMAND 13 - Read Tag, Descriptor and Date

Description This command reads an ASCII Tag which identifies the device, an ASCII descriptor of the device and the last Date it has been configured. Write Parameters NONE Floating Point Data Returned NONE Integer Data Returned
Word 0 1 2 3 4 5 . . . 12 13 14 High Byte STATUS WORD TAG ASCII Character 0 TAG ASCII Character 2 TAG ASCII Character 4 TAG ASCII Character 6 Descriptor ASCII Character 0 . . . Descriptor ASCII Character 14 Date Date Message ASCII Character 15 Date 0 TAG ASCII Character 1 TAG ASCII Character 3 TAG ASCII Character 5 TAG ASCII Character 7 Message ASCII Character 1 Low Byte
Page 57 of 119
COMMAND 14 - Read PV Sensor Info

Description This command gets information about the Primary Variable sensor, like limits and span. Write Parameters NONE Floating Point Data Returned
Word 0 1 2 3 4 5 Minimum Span Lower Sensor Limit High Byte Upper Sensor Limit Low Byte

Word 0 1 2 High Byte STATUS WORD Sensor Serial Number 0 Sensor Serial Number 2 Sensor Serial Number 1 Unit Codes for Sensor Limits and Span Low Byte
Page 58 of 119
COMMAND 15 - Read Output Information

Description This command gets information about the Primary Variable Output Information. Write Parameters NONE Floating Point Data Returned
Word 0 1 2 3 4 5 Damping Value (Sec) Lower Range Value High Byte Upper Range Value Low Byte

Word 0 1 2 2 High Byte STATUS WORD Alarm Select Code Primary Variable Range Units Code Private-Label Distributor Code Transfer Function Code Write-Protect Code 0 Low Byte
Page 59 of 119
COMMAND 16 - Read Final Assembly Number

Description This command reads the final assembly number of the HART device. Write Parameters NONE Floating Point Data Returned NONE Integer Data Returned
Word 0 1 2 High Byte STATUS WORD Final Assembly Number 0 Final Assembly Number 2 Final Assembly Number 1 0 Low Byte
Page 60 of 119
COMMAND 17 - Write Message

Description This command writes an ASCII message contained in the HART Device and that can be read with command 12. Write Parameters
Word 0 1 . . . 11 High Byte Packed ASCII Message Byte 0 Packed ASCII Message Byte 2 . . . Packed ASCII Message Byte 22 Packed ASCII Message Byte 23 Low Byte Packed ASCII Message Byte 1 Packed ASCII Message Byte 3

Page 61 of 119
COMMAND 18 - Write Tag, Descriptor and Date

Description This command writes an ASCII Tag which identifies the device, an ASCII descriptor of the device and the last Date it has been configured. Write Parameters
Word 0 1 2 3 . . . 8 9 10 High Byte Packed ASCII TAG Byte 0 Packed ASCII TAG Byte 2 Packed ASCII TAG Byte 4 Packed ASCII Descriptor Byte 0 . . . Packed ASCII Descriptor Byte 10 Date Date Packed ASCII Descriptor Byte 11 Date 0 Low Byte Packed ASCII TAG Byte 1 Packed ASCII TAG Byte 3 Packed ASCII TAG Byte 5 Packed ASCII Descriptor Byte 1

Page 62 of 119
COMMAND 19 - Write Final Assembly Number

Description This command writes the final assembly number of the HART device. Write Parameters
Word 0 1 High Byte Final Assembly Number 0 Final Assembly Number 2 Low Byte Final Assembly Number 1 Final Assembly Number 2
Floating Point Data Returned: NONE Integer Data Returned

Word 0 1 2 High Byte STATUS WORD Final Assembly Number 0 Final Assembly Number 2 Final Assembly Number 1 0 Low Byte
Page 63 of 119
5.2
HART Common Practice Commands
COMMAND 33 - Read Transmitter Variables

Description This command gets four user selected dynamic Variables. Write Parameters
Word 0 1 High Byte Transmitter Variable Code For Slot 0 Transmitter Variable Code For Slot 2 Low Byte Transmitter Variable Code For Slot 1 Transmitter Variable Code For Slot 3
Floating Point Data Returned

Word 0 1 2 3 4 5 6 7 Variable for Slot 3 Variable for Slot 2 Variable for Slot 0 High Byte Variable for Slot 0 Low Byte

Word 0 1 2 3 4 High Byte STATUS WORD Transmitter Variable Code For Slot 0 Transmitter Variable Code For Slot 1 Transmitter Variable Code For Slot 2 Transmitter Variable Code For Slot 3 Units Code for Slot 0 Variable Units Code for Slot 1 Variable Units Code for Slot 2 Variable Units Code for Slot 3 Variable Low Byte
Page 64 of 119
COMMAND 34 - Write Damping Value

Description This command writes the damping value of a HART device. Write Parameters
Word 0 1 High Byte Floating Point Damping Value (Sec) Low Byte

Word 0 1 High Byte Floating Point Damping Value (Sec) Low Byte

Page 65 of 119
COMMAND 35 - Write Range Values

Description This command writes the Upper and Lower range of the Primary Variable Write Parameters
Word 0 1 2 3 4 High Byte Range Units Code Floating Point Upper Range Value (Byte 1) Floating Point Upper Range Value (Byte 3) Floating Point Lower Range Value (Byte 1) Floating Point Lower Range Value (Byte 3) Low Byte Floating Point Upper Range Value (Byte 0) Floating Point Upper Range Value (Byte 2) Floating Point Lower Range Value (Byte 0) Floating Point Lower Range Value (Byte 2) Floating Point Lower Range Value (Byte 3)

Word 0 1 2 3 Lower Range Value High Byte Upper Range Value Low Byte

Word 0 1 High Byte STATUS WORD Range Units Code 0 Low Byte
Page 66 of 119
COMMAND 36 - Set Upper Range Value

Description This command is similar in effect to push the SPAN button of the HART device but doing it remotely through the HART network. Write Parameters NONE Floating Point Data Returned NONE Integer Data Returned
Page 67 of 119
COMMAND 37 - Set Lower Range Value

Description This command is similar in effect to push the ZERO button of the HART device but doing it remotely through the HART network. Write Parameters NONE Floating Point Data Returned NONE Integer Data Returned
Page 68 of 119
COMMAND 38 - Reset Configuration Changed Flag

Description This command resets the status bit that indicates that configuration has been changed. Write Parameters NONE Floating Point Data Returned NONE Integer Data Returned
Page 69 of 119
COMMAND 39 - EEPROM Control

Description This command operates over the EEPROM changing its settings. Write Parameters
Word 0 High Byte EEPROM Control Code Low Byte EEPROM Control Code

Word 0 1 High Byte STATUS WORD EEPROM Control Code 0 Low Byte
Page 70 of 119
COMMAND 40 - Enter Exit Fixed Current Mode

Description This command writes the damping value of a HART device. Write Parameters
Word 0 1 High Byte Floating Point Current (mA) Low Byte


Page 71 of 119
COMMAND 41 - Perform Transmitter Self Test

Description This command starts the HART device Self Test to find if there is any problem with the device hardware. Write Parameters NONE Floating Point Data Returned NONE Integer Data Returned
Page 72 of 119
COMMAND 42 - Perform Master Reset

Description This command performs a master reset in the HART device. Write Parameters NONE Floating Point Data Returned NONE Integer Data Returned
Page 73 of 119
COMMAND 43 - Set PV Zero

Description This command forces the Primary Value to Zero. Write Parameters NONE Floating Point Data Returned NONE Integer Data Returned
Page 74 of 119
COMMAND 44 - Write PV Units

Description This command changes the setting of the Primary Variable units. Write Parameters
Word 0 High Byte Primary Variable Units Code Low Byte Primary Variable Units Code

Page 75 of 119
COMMAND 45 - Trim DAC Zero

Description This command calibrates the device Digital to analog converter zero. This is done by writing the same current value that is measured in the loop. Write Parameters
Word 0 1 High Byte Floating Point measured current (mA) Low Byte


Page 76 of 119
COMMAND 46 - Trim DAC Gain

Description This command calibrates the device Digital to analog converter gain. This is done by writing the same current value that is measured in the loop. Write Parameters
Word 0 1 High Byte Floating Point Measured Current (mA) Low Byte


Page 77 of 119
COMMAND 47 - Write Transfer Function

Description This command changes the setting of the Transfer Function of the HART device. Write Parameters
Word 0 High Byte Transfer Function Code Low Byte Transfer Function Code

Word 0 1 High Byte STATUS WORD Transfer Function Code 0 Low Byte
Page 78 of 119
COMMAND 48 - Read Additional Transmitter Status

Description This command gets extended information about the status of the Transmitter. This information is specific for each transmitter. Write Parameters NONE Floating Point Data Returned NONE Integer Data Returned
Word 0 1 2 . . . 13 High Byte STATUS WORD Additional Status (Byte 0) Additional Status (Byte 2) . . . Additional Status (Byte 24) 0 Additional Status (Byte 1) Additional Status (Byte 3) Low Byte
Page 79 of 119
COMMAND 49 - Write PV Sensor Serial Number

Description This command changes the sensor serial number of the Primary Variable. Write Parameters
Word 0 1 High Byte Sensor Serial Number (Byte 0) Sensor Serial Number (Byte 2) Low Byte Sensor Serial Number (Byte 1) Sensor Serial Number (Byte 2)

Word 0 1 2 High Byte STATUS WORD Sensor Serial Number (Byte 0) Sensor Serial Number (Byte 2) Sensor Serial Number (Byte 1) 0 Low Byte
Page 80 of 119
COMMAND 50 - Read Dynamic Variable Assignments

Description This command gets the actual assignment of the Dynamic Variables returned with command 3. Write Parameters NONE Floating Point Data Returned NONE Integer Data Returned
Word 0 1 2 High Byte STATUS WORD Transmitter Variable Code For Primary Variable Transmitter Variable Code For Third Variable Transmitter Variable Code For Second Variable Transmitter Variable Code For Fourth Variable Low Byte
Page 81 of 119
COMMAND 51 - Write Dynamic Variable Assignments

Description This command sets the assignment of the Dynamic Variables returned with command 3. Write Parameters
Word 0 1 High Byte Transmitter Variable Code For Primary Variable Transmitter Variable Code For Third Variable Low Byte Transmitter Variable Code For Second Variable Transmitter Variable Code For Fourth Variable

Word 0 1 2 High Byte STATUS WORD Transmitter Variable Code For Primary Variable Transmitter Variable Code For Third Variable Transmitter Variable Code For Second Variable Transmitter Variable Code For Fourth Variable Low Byte
Page 82 of 119
COMMAND 52 - Set Transmitter Variable Zero

Description This command forces a selected transmitter variable to zero. Write Parameters
Word 0 High Byte Transmitter Variable Code Low Byte Transmitter Variable Code

Page 83 of 119
COMMAND 53 - Write Transmitter Variable Units

Description This command changes a selected transmitter variable unit. Write Parameters:
Word 0 High Byte Transmitter Variable Code Low Byte Transmitter Variable Units Code

Word 0 1 High Byte STATUS WORD Primary Variable Units Code Transmitter Variable Units Code Low Byte
Page 84 of 119
COMMAND 54 - Read Transmitter Variable Information

Description This command gets information about any selected transmitter variable sensor. Write Parameters
Word 0 High Byte Transmitter Variable Code Low Byte Transmitter Variable Code

Word 0 1 2 3 4 5 Transmitter Variable Damping Value (Sec) Transmitter Variable Lower Limit High Byte Transmitter Variable Upper Limit Low Byte

Word 0 1 1 2 High Byte STATUS WORD Transmitter Variable Code Sensor Serial Number 1 Unit Code for Limits Sensor Serial Number 0 Sensor Serial Number 2 0 Low Byte
Page 85 of 119
COMMAND 55 - Write Transmitter Variable Damping Value

Description This command writes the Damping Value of a user selected transmitter variable. Write Parameters
Word 0 1 2 High Byte Transmitter Variable Code Transmitter Variable Damping Value (Byte 1) Transmitter Variable Damping Value (Byte 3) Low Byte Transmitter Variable Damping Value (Byte 0) Transmitter Variable Damping Value (Byte 2) Transmitter Variable Damping Value (Byte 3)

Word 0 1 High Byte Transmitter Variable Damping Value Low Byte

Word 0 1 High Byte STATUS WORD Transmitter Variable Code 0 Low Byte
Page 86 of 119
COMMAND 56 - Write Transmitter Variable Sensor Serial Number

Description This command writes the Serial Number of a user selected transmitter variable. Write Parameters
Word 0 1 High Byte Transmitter Variable Code Transmitter Variable Sensor Serial Number (Byte 1) Low Byte Transmitter Variable Sensor Serial Number (Byte 0) Transmitter Variable Sensor Serial Number (Byte 2)

Word 0 1 2 High Byte STATUS WORD Transmitter Variable Code Transmitter Variable Sensor Serial Number (Byte 1) Transmitter Variable Sensor Serial Number (Byte 0) Transmitter Variable Sensor Serial Number (Byte 2) Low Byte
Page 87 of 119
COMMAND 57 - Read Unit Tag Descriptor Date

Description This command reads an ASCII Tag which identifies the device, an ASCII descriptor of the device and the last Date it has been configured. Write Parameters NONE Floating Point Data Returned NONE Integer Data Returned
Page 88 of 119
COMMAND 58 - Write Unit Tag Descriptor Date

Description This command writes an ASCII Tag which identifies the device, an ASCII descriptor of the device and the last Date it has been configured. Write Parameters:
Word 0 1 2 3 . . . 8 9 10 High Byte Packed ASCII TAG Byte 0 Packed ASCII TAG Byte 2 Packed ASCII TAG Byte 4 Packed ASCII Descriptor Byte 0 . . . Packed ASCII Descriptor Byte 10 Date Date Packed ASCII Descriptor Byte 11 Date 0 Low Byte Packed ASCII TAG Byte 1 Packed ASCII TAG Byte 3 Packed ASCII TAG Byte 5 Packed ASCII Descriptor Byte 1

Page 89 of 119
COMMAND 59 - Write Number Of Response Preambles

Description This command sets the number of preambles that the HART slave will use in every command response. Write Parameters
Word 0 High Byte Number of Response Preambles Low Byte Number of Response Preambles

Word 0 1 High Byte STATUS WORD Number of Response Preambles 0 Low Byte
Page 90 of 119
COMMAND 108 - Write Burst Mode Command Number

Description This command sets the command number that the HART device will use in Burst Mode. Write Parameters
Word 0 High Byte Burst Mode Command Number Low Byte Burst Mode Command Number

Word 0 1 High Byte STATUS WORD Burst Mode Command Number 0 Low Byte
Page 91 of 119
COMMAND 109 - Burst Mode Control

Description This command sets the HART device Burst Mode. Write Parameters
Word 0 High Byte Burst Mode Control Code Low Byte Burst Mode Control Code

Word 0 1 High Byte STATUS WORD Burst Mode Control Code 0 Low Byte
1 = ON 0 = Off
Page 92 of 119
COMMAND 110 - Read All Dynamic Variables

Description This command gets all dynamic Variables. Write Parameters NONE Floating Point Data Returned
Word 0 1 2 3 4 5 6 7 Fourth Variable Third Variable Second Variable High Byte Primary Variable Low Byte

Word 0 1 2 High Byte STATUS WORD Primary Variable Units Code Third Variable Units Code Second Variable Units Code Fourth Variable Units Code Low Byte
5.3
ProLinx HART Field Connections

HART field instruments are divided into four categories; A through D, depending on power requirements and whether the device sinks or sources a bias or operating current from the network. The following table defines the categories:
Type A B C D Description Type A field instruments sink direct current from the network and receive operating power from the network. Type B field instruments sink direct current from the network but receive no operating power from the network. Type C field instruments source direct current to the network and receive no operating power from the network. Type D field instruments neither source nor sink direct current from the network, nor receive operating power from the network.
On a given network, A, B, and D devices may be combined. C and D devices may also be combined. A or B field instruments should not be combined with C devices.
Page 93 of 119
5.3.1 Network Power Supply Requirements

Type A B C D Network Power Supply Required Required Must not be used. Not required, but may be used.
Note: The ProSoft 5107/5207 HART interface may be used with any HART field device. Connections for HART Devices (Types A, B, C and D) The ProLinx HART interface card has power supply input terminals for powering the devices in a network. This external power supply must be properly sized to supply current to all the HART devices in the network. A good rule of thumb is that each HART device may require as much as 20mA. Therefore, if you plan to place 10 HART devices in a network, you must provide a 24VDC power supply that can supply at least 200mA of output current. WARNING: Whenever the HART module is used in multi-drop mode (2 to 15 instruments per channel), each of the instruments 4 to 20mA analog signal is lost. Notes 1 All four channels on the unit must be either Master Powered (Power Mode A) or must be Loop or Self powered (Power Mode B). You cannot mix Power Mode A and Power Mode B on the same unit. You can mix Loop powered and Self powered instruments on the same unit. However, you cannot mix Loop powered and Self powered instruments on the same channel. For Master Powered, Multi-drop Mode and Point to Point Mode, a 1K, 1W resistor must be connected across the + and - input terminals of each HART channel. Resistors are supplied with each product. When configuring loop powered instruments in a Power Mode B type multidrop network, use only one power supply per HART channel if you wish to maintain channel to channel isolation. If channel to channel isolation is not required, the same power supply may be used for all four channels. However, a separate series resistor is required for each channel. An appropriately sized resistor must be connected in series with the power supply for each channel. The value and power rating of the resistor is dependant upon the number of instruments in the loop and the length and gauge of the pair of wires connecting the instruments to the unit. 250 Ohm, 3 Watt is a good, first choice value. If field instrument wiring is shielded, terminate shields at the ground terminals of the HART connector. Do not terminate the shields at the instrument.
Page 94 of 119
Reference Driver Manual 5
For multi-drop applications, the 1K resistor should be normally used when one transmitter is connected to the port. If you increase the number of devices connected to a single port, you may need to reduce the size of the resistor.
Page 95 of 119
Page 96 of 119
Page 97 of 119
Page 98 of 119
Page 99 of 119
Page 100 of 119
ProLinx HART Connection Diagram for Multiple Single and Loop-Powered Devices, Digital Signal Only (A, B, C, or D Types) This type of connection is NOT recommended, but has been used to mix A, B, C, and D types of HART devices. Note: This type of connection may have problems associated with the lowering of AC impedance, lower immunity to electrical noise, and lower supply voltage to A and B type devices.
5.3.2 Example Field Terminations

Up to 15 instruments per channel Multi-drop Mode (address 1 to 15) One instrument per channel
Point to Point Mode (address 0 to 15) OK Install 1K resistor
Power Mode A 24VDC connected to HART power terminals 1 and 2 on terminal block Power Mode B HART power terminals 1 and 2 on terminal block left open
Master Powered instruments on all 4 channels
OK Install 250 1K
Point to Point Mode with Analog (address 0 only) OK
Loop Powered instruments on 1 or more channels Self Powered instruments on 1 or more channels
OK
OK
Not possible
OK
OK - differential or single ended analog signal OK -differential or single ended analog signal
Page 101 of 119
5.4
HART Status Data Map

The word addresses in the following topics are virtual addresses. To view the contents of these registers, use the Data Map section (page 39) of the module configuration file to map these values into the 4000 word database.
5.4.1 Port 0 General Status Data

Status Register 10700 10701 10702 Name State Comm State Device Status (bit mapped) Description Port 0 state machine value (used for debugging) Port 0 communication state machine value (used for debugging) Each bit in this word corresponds to a slave address on the network starting at bit 1 for slave address 1. Bit 0 is not used. If the bit is set, the slave is in error. If the bit is clear (0), the slave is not in error. Each bit in this word corresponds to a slave address on the network starting at bit 1 for slave address 1. Bit 0 is not used. If the bit is set, the slave is in the poll list. If the bit is clear (0), the slave is not in the poll list. Each bit in this word corresponds to a slave address on the network starting at bit 1 for slave address 1. Bit 0 is not used. If the bit is set, the slave uses the long address. If the bit is clear (0), the slave does not use the long address. This field contains the index of the current command to execute. This field contains the total number of request messages issued on the port.
10703
Device Poll List (bit mapped)
10704
Device With Long Address (bit map)
10705 10706 10707 10708 10709 10710 10711 10799
Current Command Command Request Count
Command Response This field contains the total number of response Count messages received from devices on the network. Configuration Error Word Current Error Code Last Error Code No Valid Data Configuration error word (see HART Configuration Error Word (page 43)) Current error code for port Last error code reported for port
5.4.2 Port 0 Command Errors

Page 102 of 119
5.4.3 Port 1 General Status Data

Status Register 10900 10901 10902 Name State Comm State Device Status (bit mapped) Description Port 1 state machine value (used for debugging) Port 1 communication state machine value (used for debugging) Each bit in this word corresponds to a slave address on the network starting at bit 1 for slave address 1. Bit 0 is not used. If the bit is set, the slave is in error. If the bit is clear (0), the slave is not in error. Each bit in this word corresponds to a slave address on the network starting at bit 1 for slave address 1. Bit 0 is not used. If the bit is set, the slave is in the poll list. If the bit is clear (0), the slave is not in the poll list. Each bit in this word corresponds to a slave address on the network starting at bit 1 for slave address 1. Bit 0 is not used. If the bit is set, the slave uses the long address. If the bit is clear (0), the slave does not use the long address. This field contains the index of the current command to execute. This field contains the total number of request messages issued on the port.
10903
Device Poll List (bit mapped)
10904
Device With Long Address (bit map)
10905 10906 10907 10908 10909 10910 10911 10999
Current Command Command Request Count
Command Response This field contains the total number of response Count messages received from devices on the network. Configuration Error Word Current Error Code Last Error Code No Valid Data Configuration error word (see HART Configuration Error Word (page 43)) Current error code for port Last error code reported for port
5.4.4 Port 1 Command Errors

5.4.5 Port 2 Data

Status Register 11100 11299 Description Same as above
Page 103 of 119
5.4.6 Port 3 Data

5.4.7 Port 4 Data

5.4.8 Port 5 Data

5.4.9 Port 6 Data

5.4.10 Port 7 Data

Page 104 of 119
5.5
Module Status Values

5.5.1 Normal Operation

Status Register 0x00 Description Interface operational
5.5.2 Interface Crash Codes

Status Register 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0A 0X0B Description 2-second interface timeout Bad interface opcode Interface data error Interface test error Interface x-fer done error Bad interface path Bad interface state Bad interface length Global data length error Global data address error Global data not present
5.5.3 Fatal Crash Codes

Status Register 0x81 0x82 0x83 0x84 0x85 0x86 0x87 0x88 0x89 0x8A 0X8B 0X8C 0X8D 0X8E 0X8F Description PROM checksum error Internal RAM data test error External RAM data test error External RAM address test error Bad confidence test index External Int0 event error External Int1 event error DMA Int0 event error Comm. Int event error Xmit-no good event error No response timeout MAC State No response timeout MAC idle Receive OK MAC state Transmit OK MAC state No receive buffer free
Page 105 of 119

Status Register 0X90 0X91 0X92 0X93 0X94 0X95 0X96 0X97 0X98 Description Bad input transfer length Reserved rev buffer error Bad trans control state Bad word request bit Node queue overflow Bad data queue error Empty data path error Bad path search index Bad data slave path
5.5.4 Peer Status Codes

Status Register 0 32 64 96 128 Description Monitor link operation Normal link operation Never getting token Sole station Duplicate station
5.5.5 Global Out Update Status

Status Register 0x01 0x02 0x04 0x08 0x10 0x20 0x40 0x80 Description Updating all OK Not assigned Not assigned Global update timeout (not trasmitted in 500 milliseconds) Global data not configured (length set to zero) Not assigned Invalid Global Data Length (Length > 32 words) Not assigned
Page 106 of 119
5.6
Module Status Data Map

5.6.1 General Module Status Data

Status Register 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4019 No Valid Data Production Run Number (ASCII) Operating System Rev (ASCII) Revision (ASCII) Description Program Cycle Counter Product Name (ASCII)
5.6.2 HTTP Port 80 Status

Status Register 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 Description Reserved Reserved Reserved Number of Request Packets Number of Response Packets Reserved Reserved Reserved Reserved Reserved
5.6.3 SNTP Client Status

Status Register 4030 4031 4032 4033 4034 Description Time is valid Request count Response count Computation count Clock set count
Page 107 of 119

Status Register 4035 4036 4039 Description Timeout error count No Valid Data
5.6.4 Wireless SNTP Client Status

Status Register 4040 4041 4042 4043 4044 4045 4046 4049 Description Time is valid Request count Response count Computation count Clock set count Timeout error count No Valid Data
5.7
Virtual Addresses Assigned to Status Data Areas

Driver Module MODBUS Plus MCM MNET DFCM DFNT RIO adapter DNP Slave DNP Net Server IEC-101 Slave IEC-104 Server Profibus Slave Profibus Master Master HART BACnet Radio Reserved ASCII Reserved IEC-103 Master Start Address 4000 4100 4400 6000 6300 7900 9000 9900 10000 10100 10200 10300 10400 10500 10700 12300 12500 12600 13000 13100 14000 End Address 4099 4399 5999 6299 7899 8999 9099 9999 10099 10199 10299 10399 10499 10699 12299 12499 12599 12999 13099 13999 14089 Reserved Length Comment 100 300 1600 300 1600 1100 100 100 100 100 100 100 100 200 1600 200 100 400 100 900 90 Cmds
Page 108 of 119

Driver Master DH485 Master IEC-101 Master Master RIO Scanner ControlNet Reserved EGD Reserved EGD Wireless Reserved DFNT Wireless Reserved 15500 16000 17500 18000 19500 19900 19500 15999 17400 17999 19400 19899 21000 65535 500 1400 500 1400 400 1100 48036 Start Address 15000 14100 14200 End Address 15499 14199 14299

Reserved Length Comment 500 100 100 Cmds Cmds Cmds
Exchange status Exchange status
Page 109 of 119
Page 110 of 119
Support, Service & Warranty Driver Manual
Support, Service & Warranty

In This Chapter
How to Contact Us: Technical Support................................................ 111 Return Material Authorization (RMA) Policies and Conditions............. 112 LIMITED WARRANTY......................................................................... 113
ProSoft Technology, Inc. (ProSoft) is committed to providing the most efficient and effective support possible. Before calling, please gather the following information to assist in expediting this process: 1 2 3 1 Product Version Number System architecture Network details Module configuration and contents of file o Module Operation o Configuration/Debug status information o LED patterns Information about the processor and user data files as viewed through and LED patterns on the processor. Details about the serial devices interfaced, if any.
If the issue is hardware related, we will also need information regarding:
2 3
6.1
How to Contact Us: Technical Support

Internet Asia Pacific +603.7724.2080, support.asia@prosoft-technology.com Languages spoken include: Chinese, English Europe (location in Toulouse, France) +33 (0) 5.34.36.87.20, support.EMEA@prosoft-technology.com Languages spoken include: French, English North America/Latin America (excluding Brasil) (location in California) +1.661.716.5100, support@prosoft-technology.com Languages spoken include: English, Spanish For technical support calls within the United States, an after-hours answering system allows pager access to one of our qualified technical and/or application support engineers at any time to answer your questions. Brasil (location in Sao Paulo) +55-11-5084-5178, eduardo@prosoft-technology.com Languages spoken include: Portuguese, English Web Site: www.prosoft-technology.com/support E-mail address: support@prosoft-technology.com
Page 111 of 119
6.2
Return Material Authorization (RMA) Policies and Conditions

The following RMA Policies and Conditions (collectively, "RMA Policies") apply to any returned Product. These RMA Policies are subject to change by ProSoft without notice. For warranty information, see "Limited Warranty". In the event of any inconsistency between the RMA Policies and the Warranty, the Warranty shall govern.
6.2.1 All Product Returns:

a) In order to return a Product for repair, exchange or otherwise, the Customer must obtain a Returned Material Authorization (RMA) number from ProSoft and comply with ProSoft shipping instructions. b) In the event that the Customer experiences a problem with the Product for any reason, Customer should contact ProSoft Technical Support at one of the telephone numbers listed above (page 111). A Technical Support Engineer will request that you perform several tests in an attempt to isolate the problem. If after completing these tests, the Product is found to be the source of the problem, we will issue an RMA. c) All returned Products must be shipped freight prepaid, in the original shipping container or equivalent, to the location specified by ProSoft, and be accompanied by proof of purchase and receipt date. The RMA number is to be prominently marked on the outside of the shipping box. Customer agrees to insure the Product or assume the risk of loss or damage in transit. Products shipped to ProSoft using a shipment method other than that specified by ProSoft or shipped without an RMA number will be returned to the Customer, freight collect. Contact ProSoft Technical Support for further information. d) A 10% restocking fee applies to all warranty credit returns whereby a Customer has an application change, ordered too many, does not need, and so on.
6.2.2 Procedures for Return of Units Under Warranty:

A Technical Support Engineer must approve the return of Product under ProSofts Warranty: a) A replacement module will be shipped and invoiced. A purchase order will be required. b) Credit for a product under warranty will be issued upon receipt of authorized product by ProSoft at designated location referenced on the Return Material Authorization.
6.2.3 Procedures for Return of Units Out of Warranty:

a) Customer sends unit in for evaluation b) If no defect is found, Customer will be charged the equivalent of $100 USD, plus freight charges, duties and taxes as applicable. A new purchase order will be required.
Page 112 of 119
c) If unit is repaired, charge to Customer will be 30% of current list price (USD) plus freight charges, duties and taxes as applicable. A new purchase order will be required or authorization to use the purchase order submitted for evaluation fee. The following is a list of non-repairable units: o 3150 - All o 3750 o 3600 - All o 3700 o 3170 - All o 3250 o 1560 - Can be repaired, only if defect is the power supply o 1550 - Can be repaired, only if defect is the power supply o 3350 o 3300 o 1500 - All
6.3
LIMITED WARRANTY
This Limited Warranty ("Warranty") governs all sales of hardware, software and other products (collectively, "Product") manufactured and/or offered for sale by ProSoft, and all related services provided by ProSoft, including maintenance, repair, warranty exchange, and service programs (collectively, "Services"). By purchasing or using the Product or Services, the individual or entity purchasing or using the Product or Services ("Customer") agrees to all of the terms and provisions (collectively, the "Terms") of this Limited Warranty. All sales of software or other intellectual property are, in addition, subject to any license agreement accompanying such software or other intellectual property.
6.3.1 What Is Covered By This Warranty

a) Warranty On New Products: ProSoft warrants, to the original purchaser, that the Product that is the subject of the sale will (1) conform to and perform in accordance with published specifications prepared, approved and issued by ProSoft, and (2) will be free from defects in material or workmanship; provided these warranties only cover Product that is sold as new. This Warranty expires three years from the date of shipment (the "Warranty Period"). If the Customer discovers within the Warranty Period a failure of the Product to conform to specifications, or a defect in material or workmanship of the Product, the Customer must promptly notify ProSoft by fax, email or telephone. In no event may that notification be received by ProSoft later than 39 months. Within a reasonable time after notification, ProSoft will correct any failure of the Product to conform to specifications or any defect in material or workmanship of the Product, with either new or used replacement parts. Such repair, including both parts and labor, will be performed at ProSofts expense. All warranty service will be performed at service centers designated by ProSoft.
Page 113 of 119
b) Warranty On Services: Materials and labor performed by ProSoft to repair a verified malfunction or defect are warranteed in the terms specified above for new Product, provided said warranty will be for the period remaining on the original new equipment warranty or, if the original warranty is no longer in effect, for a period of 90 days from the date of repair.
6.3.2 What Is Not Covered By This Warranty

a) ProSoft makes no representation or warranty, expressed or implied, that the operation of software purchased from ProSoft will be uninterrupted or error free or that the functions contained in the software will meet or satisfy the purchasers intended use or requirements; the Customer assumes complete responsibility for decisions made or actions taken based on information obtained using ProSoft software. b) This Warranty does not cover the failure of the Product to perform specified functions, or any other non-conformance, defects, losses or damages caused by or attributable to any of the following: (i) shipping; (ii) improper installation or other failure of Customer to adhere to ProSofts specifications or instructions; (iii) unauthorized repair or maintenance; (iv) attachments, equipment, options, parts, software, or user-created programming (including, but not limited to, programs developed with any IEC 61131-3, "C" or any variant of "C" programming languages) not furnished by ProSoft; (v) use of the Product for purposes other than those for which it was designed; (vi) any other abuse, misapplication, neglect or misuse by the Customer; (vii) accident, improper testing or causes external to the Product such as, but not limited to, exposure to extremes of temperature or humidity, power failure or power surges; or (viii) disasters such as fire, flood, earthquake, wind and lightning. c) The information in this Agreement is subject to change without notice. ProSoft shall not be liable for technical or editorial errors or omissions made herein; nor for incidental or consequential damages resulting from the furnishing, performance or use of this material. The user guide included with your original product purchase from ProSoft contains information protected by copyright. No part of the guide may be duplicated or reproduced in any form without prior written consent from ProSoft.
6.3.3 Disclaimer Regarding High Risk Activities

Product manufactured or supplied by ProSoft is not fault tolerant and is not designed, manufactured or intended for use in hazardous environments requiring fail-safe performance including and without limitation: the operation of nuclear facilities, aircraft navigation of communication systems, air traffic control, direct life support machines or weapons systems in which the failure of the product could lead directly or indirectly to death, personal injury or severe physical or environmental damage (collectively, "high risk activities"). ProSoft specifically disclaims any express or implied warranty of fitness for high risk activities.
Page 114 of 119
6.3.4 Intellectual Property Indemnity

Buyer shall indemnify and hold harmless ProSoft and its employees from and against all liabilities, losses, claims, costs and expenses (including attorneys fees and expenses) related to any claim, investigation, litigation or proceeding (whether or not ProSoft is a party) which arises or is alleged to arise from Buyers acts or omissions under these Terms or in any way with respect to the Products. Without limiting the foregoing, Buyer (at its own expense) shall indemnify and hold harmless ProSoft and defend or settle any action brought against such Companies to the extent based on a claim that any Product made to Buyer specifications infringed intellectual property rights of another party. ProSoft makes no warranty that the product is or will be delivered free of any persons claiming of patent, trademark, or similar infringement. The Buyer assumes all risks (including the risk of suit) that the product or any use of the product will infringe existing or subsequently issued patents, trademarks, or copyrights. a) Any documentation included with Product purchased from ProSoft is protected by copyright and may not be duplicated or reproduced in any form without prior written consent from ProSoft. b) ProSofts technical specifications and documentation that are included with the Product are subject to editing and modification without notice. c) Transfer of title shall not operate to convey to Customer any right to make, or have made, any Product supplied by ProSoft. d) Customer is granted no right or license to use any software or other intellectual property in any manner or for any purpose not expressly permitted by any license agreement accompanying such software or other intellectual property. e) Customer agrees that it shall not, and shall not authorize others to, copy software provided by ProSoft (except as expressly permitted in any license agreement accompanying such software); transfer software to a third party separately from the Product; modify, alter, translate, decode, decompile, disassemble, reverse-engineer or otherwise attempt to derive the source code of the software or create derivative works based on the software; export the software or underlying technology in contravention of applicable US and international export laws and regulations; or use the software other than as authorized in connection with use of Product. f) Additional Restrictions Relating To Software And Other Intellectual Property In addition to compliance with the Terms of this Warranty, Customers purchasing software or other intellectual property shall comply with any license agreement accompanying such software or other intellectual property. Failure to do so may void this Warranty with respect to such software and/or other intellectual property.
6.3.5 Disclaimer of all Other Warranties

The Warranty set forth in What Is Covered By This Warranty (page 113) are in lieu of all other warranties, express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. ProSoft Technology, Inc. July 7, 2009 Page 115 of 119
6.3.6 Limitation of Remedies **

In no event will ProSoft or its Dealer be liable for any special, incidental or consequential damages based on breach of warranty, breach of contract, negligence, strict tort or any other legal theory. Damages that ProSoft or its Dealer will not be responsible for included, but are not limited to: Loss of profits; loss of savings or revenue; loss of use of the product or any associated equipment; loss of data; cost of capital; cost of any substitute equipment, facilities, or services; downtime; the claims of third parties including, customers of the Purchaser; and, injury to property. ** Some areas do not allow time limitations on an implied warranty, or allow the exclusion or limitation of incidental or consequential damages. In such areas, the above limitations may not apply. This Warranty gives you specific legal rights, and you may also have other rights which vary from place to place.
6.3.7 Time Limit for Bringing Suit

Any action for breach of warranty must be commenced within 39 months following shipment of the Product.
6.3.8 No Other Warranties

Unless modified in writing and signed by both parties, this Warranty is understood to be the complete and exclusive agreement between the parties, suspending all oral or written prior agreements and all other communications between the parties relating to the subject matter of this Warranty, including statements made by salesperson. No employee of ProSoft or any other party is authorized to make any warranty in addition to those made in this Warranty. The Customer is warned, therefore, to check this Warranty carefully to see that it correctly reflects those terms that are important to the Customer.
6.3.9 Allocation of Risks

This Warranty allocates the risk of product failure between ProSoft and the Customer. This allocation is recognized by both parties and is reflected in the price of the goods. The Customer acknowledges that it has read this Warranty, understands it, and is bound by its Terms.
6.3.10 Controlling Law and Severability

This Warranty shall be governed by and construed in accordance with the laws of the United States and the domestic laws of the State of California, without reference to its conflicts of law provisions. If for any reason a court of competent jurisdiction finds any provisions of this Warranty, or a portion thereof, to be unenforceable, that provision shall be enforced to the maximum extent permissible and the remainder of this Warranty shall remain in full force and effect. Any cause of action with respect to the Product or Services must be instituted in a court of competent jurisdiction in the State of California. Page 116 of 119 ProSoft Technology, Inc. July 7, 2009
Index Driver Manual

COMMAND 47 - Write Transfer Function 78 COMMAND 48 - Read Additional Transmitter Status 79 COMMAND 49 - Write PV Sensor Serial Number 80 COMMAND 50 - Read Dynamic Variable Assignments 81 COMMAND 51 - Write Dynamic Variable Assignments 82 COMMAND 52 - Set Transmitter Variable Zero 83 COMMAND 53 - Write Transmitter Variable Units 84 COMMAND 54 - Read Transmitter Variable Information 85 COMMAND 55 - Write Transmitter Variable Damping Value 86 COMMAND 56 - Write Transmitter Variable Sensor Serial Number 87 COMMAND 57 - Read Unit Tag Descriptor Date 88 COMMAND 58 - Write Unit Tag Descriptor Date 89 COMMAND 59 - Write Number Of Response Preambles 90 Command Count 29 Command List Overview 31 Commands Supported by the Module 32, 34, 41 Configuration Error Word Table 43 Configure the Gateway 25 Connecting Power to the Unit 9 Connections for HART Devices (Types A, B, C and D) 94 Controlling Law and Severability 116
Index
[
[HART PORT x COMMANDS] 31 [HART PORT x] 28
A
All Product Returns: 112 All ProLinx Products 2 Allocation of Risks 116 Auto-Poll Code 30 Auto-Poll DB Address 30 Auto-Poll Disabled Mode 18 Auto-Poll Swap Float 30 Auto-Polling 15
B
Byte Count 38
C
COMMAND 00 - Read Unique Identifier 51 COMMAND 01 - Read Primary Variable 52 COMMAND 02 - Read Current And Percent Of Range 53 COMMAND 03 - Read Dynamic Variables 54 COMMAND 06 - Write Polling Address 55 COMMAND 108 - Write Burst Mode Command Number 91 COMMAND 109 - Burst Mode Control 92 COMMAND 110 - Read All Dynamic Variables 93 COMMAND 12 - Read Message 56 COMMAND 13 - Read Tag, Descriptor and Date 57 COMMAND 14 - Read PV Sensor Info 58 COMMAND 15 - Read Output Information 59 COMMAND 16 - Read Final Assembly Number 60 COMMAND 17 - Write Message 61 COMMAND 18 - Write Tag, Descriptor and Date 62 COMMAND 19 - Write Final Assembly Number 63 COMMAND 33 - Read Transmitter Variables 64 COMMAND 34 - Write Damping Value 65 COMMAND 35 - Write Range Values 66 COMMAND 36 - Set Upper Range Value 67 COMMAND 37 - Set Lower Range Value 68 COMMAND 38 - Reset Configuration Changed Flag 69 COMMAND 39 - EEPROM Control 70 COMMAND 40 - Enter Exit Fixed Current Mode 71 COMMAND 41 - Perform Transmitter Self Test 72 COMMAND 42 - Perform Master Reset 73 COMMAND 43 - Set PV Zero 74 COMMAND 44 - Write PV Units 75 COMMAND 45 - Trim DAC Zero 76 COMMAND 46 - Trim DAC Gain 77
D
Data Map 39, 102, 105, 107 DB Address Status 29 Delay Preset 41 Disclaimer of all Other Warranties 115 Disclaimer Regarding High Risk Activities 114 Done DB Address 37 Downloading a File from PC to the Gateway 42
E
Enable 32 Enable DB Address 37 Enabled 28 Error/Status Data 43 Error/Status Data Structure 45 Example Field Terminations 101
F
Fatal Crash Codes 105 Fixed Data 38 Float DB Address 33 FP Word Count 33 From Address 40 Function Code 34 Functional Overview 11
G
General Module Status Data 107
Page 117 of 119

General Status Data (Ports 2 through 7) 45 Global Out Update Status 106
Index Driver Manual

Port 0 General Status Data 44, 102 Port 1 Command Errors 103 Port 1 Command List Errors 47 Port 1 General Status Data 44, 103 Port 2 Data 103 Port 3 Data 104 Port 4 Data 104 Port 5 Data 104 Port 6 Data 104 Port 7 Data 104 Preambles 29 Primary Master 29 Printing a Configuration File 28 Procedures for Return of Units Out of Warranty: 112 Procedures for Return of Units Under Warranty: 112 ProLinx Gateways with Ethernet Ports 2 ProLinx HART Connection Diagram for Multiple Single and Loop-Powered Devices, Digital Signal Only (A, B, C, or D Types) 101 ProLinx HART Field Connections 93 ProSoft Technology Product Documentation 3 Protocol Error Codes 47
H
HART Channel Driver Access to Database 15 HART Channel Specifications 13 HART Channels 11 HART Command Entry Formats 32, 41 HART Command List 23 HART Command List Error Data 46 HART Common Practice Commands 32, 64 HART Common Practice Commands Set 35 HART Configuration Error Word 43, 102, 103 HART LED Indicators 43 HART Status Data Map 102 HART Universal Commands 32, 51 HART Universal Commands Set 34 How to Contact Us Technical Support 111, 112 HTTP Port 80 Status 107
I
Important Installation Instructions 2 Install ProSoft Configuration Builder Software 9 Int Word Count 36 Int. DB Address 36 Intellectual Property Indemnity 115 Interface Crash Codes 105 Internal Database Re-mapping 40
R
Reference 51 Register Count 40 Retry Count 29 Return Material Authorization (RMA) Policies and Conditions 112
L
Limitation of Remedies ** 116 LIMITED WARRANTY 113
S
Short Address 34 Slave List Status 47 SNTP Client Status 107 Start Here 7 Support, Service & Warranty 111 Swap Code 33, 37, 38, 40 System Requirements 7
M
Max Device Count 30 Module Entries 27 Module Error Codes 47 Module Internal Database 15 Module Status Data Map 107 Module Status Values 105 Mounting the Module on the DIN-rail 8 Multi-drop Mode 20
T
Time Limit for Bringing Suit 116 To Address 40 To Order a ProLinx Plus gateway with the -WEB option: 3 To upgrade a previously purchased Series C model: 2
N
Network Power Supply Requirements 94 No Other Warranties 116 Normal Operation 105 Notes 94
U
Use Long 37 Using the Help System 10
P
Package Contents 8 Peer Status Codes 106 Pinouts 2, 94 Point-to-Point Mode 18 Poll Interval 33 Port 0 Command Errors 102 Port 0 Command List Errors 46
V
Viewing Error and Status Data 43 Virtual Addresses Assigned to Status Data Areas 108
W
What Is Covered By This Warranty 113, 115 What Is Not Covered By This Warranty 114
Page 118 of 119
Index Driver Manual

Wireless SNTP Client Status 108 Write DB Address 37
Y
Your Feedback Please 3
Page 119 of 119

Hart Driver Manual

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Hart Driver Manual

Încărcat de

Drepturi de autor:

Formate disponibile

HART

ProLinx Gateway HART Master

July 07, 2009

Important Installation Instructions

All ProLinx Products

243333 CL I Div 2 GPs A, B, C, D Temp Code T5 II 3 G Ex nA nL IIC T5 X 0 C <= Ta <= 60 C

ProLinx Gateways with Ethernet Ports

To upgrade a previously purchased Series C model:

To Order a ProLinx Plus gateway with the -WEB option:

Your Feedback Please

ProSoft Technology Product Documentation

Contents Driver Manual

HART ProLinx Gateway HART Master

Configure the Gateway

ProSoft Technology, Inc. July 7, 2009

HART ProLinx Gateway HART Master 6

Contents Driver Manual 111

Support, Service & Warranty

ProSoft Technology, Inc. July 7, 2009

Start Here Driver Manual

HART ProLinx Gateway HART Master

ProSoft Technology, Inc. July 7, 2009

HART ProLinx Gateway HART Master

Start Here Driver Manual

Mounting the Module on the DIN-rail

ProLinx 5000/6000 Series Module

ProSoft Technology, Inc. July 7, 2009

Start Here Driver Manual

HART ProLinx Gateway HART Master

Connecting Power to the Unit

Install ProSoft Configuration Builder Software

ProSoft Technology, Inc. July 7, 2009

HART ProLinx Gateway HART Master 3 4

Start Here Driver Manual

1.5.1 Using the Help System

ProSoft Technology, Inc. July 7, 2009

Functional Overview Driver Manual

HART ProLinx Gateway HART Master

ProSoft Technology, Inc. July 7, 2009

HART ProLinx Gateway HART Master

Functional Overview Driver Manual

ProSoft Technology, Inc. July 7, 2009

Functional Overview Driver Manual

HART ProLinx Gateway HART Master

HART Channel Specifications

Common Practice Command Set

ProSoft Technology, Inc. July 7, 2009

HART ProLinx Gateway HART Master

Functional Overview Driver Manual

Polling of command list

The ProLinx HART module supports version 5 of the HART protocol.

ProSoft Technology, Inc. July 7, 2009

Functional Overview Driver Manual

HART ProLinx Gateway HART Master

Module Internal Database

2.3.1 HART Channel Driver Access to Database

Write for Read Command

HART Driver Slave Device

ProSoft Technology, Inc. July 7, 2009

HART ProLinx Gateway HART Master

Functional Overview Driver Manual

byte word byte byte byte byte byte byte byte

CMD 0 CMD 0 CMD 0 CMD 3 CMD 3 CMD 3 CMD 3 CMD 13 CMD 13

Info Info Info Cfg Cfg Cfg Cfg Info Info