1. Manuals
  2. Brands
  3. ProSoft Manuals
  4. Media Converter
  5. PLX51-HART-4I
  6. User manual

ProSoft PLX51-HART-4I User Manual

4-channel hart input multidrop field device
Hide thumbs Also See for PLX51-HART-4I:
Table of Contents

Advertisement

Quick Links

Download this manual
PLX51-HART-4I
4-Channel HART Input
Multidrop Field Device
November 27, 2018
USER MANUAL

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the PLX51-HART-4I and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for ProSoft PLX51-HART-4I

Summary of Contents for ProSoft PLX51-HART-4I

  • Page 1 PLX51-HART-4I 4-Channel HART Input Multidrop Field Device November 27, 2018 USER MANUAL...
  • Page 2 Page 2 of 88...

  • Page 3: Table Of Contents

    3.1. Install Configuration Software .................. 13 3.2. Network Parameters ....................14 3.3. Creating a New Project ....................18 3.4. PLX51-HART-4I Parameters ..................20 3.5. Module Download ..................... 29 3.6. Logix Integration......................31 3.6.1. Add Module to I/O Configuration ..............31 3.6.2.
  • Page 4 5.2.3. Modbus TCP/IP Status ..................58 5.3. Channel Status ......................60 5.3.1. General Tab ......................61 5.3.2. Device Info Tab ....................62 5.3.3. Device Status Tab ....................63 5.3.4. Device Configuration Tab ................... 65 5.3.5. Advanced Status Tab ..................66 5.3.6.

  • Page 5: Preface

    Preface 1. PREFACE 1.1. FEATURES The PLX51-HART-4I can convert up to four analog devices into either EtherNet/IP™, Modbus TCP/IP®, or DNP3 TCP/UDP protocols. This includes 4 to 20 mA input devices, with or without HART communications. The conversion to EtherNet/IP enables a HART device to be added directly into a Rockwell Automation Logix IO tree.

  • Page 6: References

    For additional support, please contact the following: Resource Link Contact Us web link https://www.prosoft-technology.com/ Support email support@prosoft-technology.com Table 1.3. – Support Details For professional users in the European Union If you wish to discard electrical and electronic equipment (EEE), please contact your dealer or supplier for further information.

  • Page 7: Installation

    Installation 2. INSTALLATION 2.1. MODULE LAYOUT The module has six ports at the bottom of the enclosure as shown in the figure below. The ports are used for Ethernet, the four analog HART channels, and power. The power port uses a three-way connector, which is used for the DC power supply and the earth connection.

  • Page 8: Led's

    Installation 2.2. LED’S The module provides six diagnostic LEDs as shown in the figure below. These LEDs are used to provide information regarding the module system operation, the Ethernet interface, and the status of each of the four analog HART channels. Figure 2.2.

  • Page 9: Module Mounting

    Installation 2.3. MODULE MOUNTING The module provides a DIN rail clip to mount onto a 35mm DIN rail. Figure 2.3 - DIN rail specification The DIN rail clip is mounted on the bottom of the module at the back as shown in the figure below.

  • Page 10: Power

    Installation 2.4. POWER A three-way power connector is used to connect Power+, Power- (ground), and earth. The module requires an input voltage of 12 to 28 Vdc. Refer to the Technical Specifications section in this document. Figure 2.5 - Power connector 2.5.

  • Page 11: Ethernet Port

    The equivalent Analog Input circuit is shown below: Figure 2.7 – Analog Input Equivalent Circuit 2.6. ETHERNET PORT The Ethernet connector should be wired according to industry standards. Refer to the Additional Information section in this document for further details. Page 11 of 88...
  • Page 12 Page 12 of 88...

  • Page 13: Setup

    3. SETUP 3.1. INSTALL CONFIGURATION SOFTWARE The network setup and configuration of the module is achieved by means of the PLX50 Configuration Utility. This software can be downloaded from https://www.prosoft- technology.com/. Figure 3.1. - PLX50 Configuration Utility Page 13 of 88...

  • Page 14: Network Parameters

    Setup 3.2. NETWORK PARAMETERS The module has DHCP (Dynamic Host Configuration Protocol) enabled as factory default. Thus, a DHCP server must be used to provide the module with the required network parameters (IP address, subnet mask, etc.). There are a number of DHCP utilities available, however it is recommended to use the DHCP server within the PLX50 Configuration Utility.
  • Page 15 Setup To assign an IP address, click on the corresponding “Assign” button. The IP Address Assignment window opens. Figure 3.4. - Assigning IP Address The required IP address can then be either entered, or a recently used IP address can be selected by clicking on an item in the Recent List.
  • Page 16 Setup It is possible to force the module back into DHCP mode by powering up the device with DIP switch 2 set to the On position. A new IP address can then be assigned by repeating the previous steps. NOTE: It is important to return DIP switch 2 back to Off position, to avoid the module returning to a DHCP mode after the power is cycled again.
  • Page 17 Setup Right-clicking on a device reveals the context menu, including the Port Configuration option. Figure 3.8. - Selecting Port Configuration The Ethernet port configuration parameters can be modified using the Port Configuration window. Figure 3.9. - Port Configuration Alternatively, these parameters can be modified using Rockwell Automation’s RSLinx software.

  • Page 18: Creating A New Project

    Setup 3.3. CREATING A NEW PROJECT Before you can configure the module, a new PLX50 Configuration Utility project must be created. Under the File menu, select New. Figure 3.10. - Creating a new project A PLX50 Configuration Utility project will be created, showing the Project Explorer tree view. To save the project, use the Save option under the File menu.
  • Page 19 Setup In the Add New Device window, select the PLX51-HART-4I module and click the Ok button. Figure 3.12 – Selecting a new PLX51-HART-4I The device will appear in the Project Explorer tree with its configuration window opened. The device configuration window can be reopened by either double-clicking the module in the Project Explorer tree or right-clicking the module and selecting Configuration.

  • Page 20: Plx51-Hart-4I Parameters

    Setup 3.4. PLX51-HART-4I PARAMETERS The PLX51-HART-4I parameters are configured using the PLX50 Configuration Utility. The configuration form is divided into multiple tabs to configure the general, DNP3, and channel- specific parameters. When downloading the configuration into the module, it will be saved in non-volatile memory that remains when the module is powered down.
  • Page 21 Setup The general configuration is shown in the figure below. The general configuration window is opened by either double-clicking on the module in the tree or right-clicking the module and selecting Configuration. Figure 3.14. - General Configuration Each of the channel configuration tabs consist of the following parameters: Parameter Description Enable Channel...
  • Page 22 Setup HART Communications Used to Enable or Disable the HART Communication. Enable HART This should be disabled when using standard (non-HART) analog field devices. Used to enable or disable pass through (Class 2) messages, either from Logix Enable Relay Messages (message blocks) or DTMs.
  • Page 23 Setup The Channel (0) configuration is shown in the figure below. This window is opened by either double-clicking on the module in the tree or right-clicking the module followed by selecting Configuration. Once in the configuration window, select the tab corresponding to the required channel.
  • Page 24 Setup The module supports the asynchronous reading of advanced diagnostic parameters, which are directly written to Logix tags. The Advanced Diagnostics configuration tab consists of the following parameters: Parameter Description Description A user description for the advanced diagnostic parameter. Command The command string used to collect the parameter.
  • Page 25 Setup To create a new Advanced Diagnostic item, select the Build button. The HART Advanced Diagnostic Builder will open. Figure 3.17. – Advanced Diagnostic Builder The builder is used to generate the command, and to define the Data Type. The following parameters need to be defined: Parameter Description...
  • Page 26 Setup Once accepted, the full command string will be built, and the current map item will be populated accordingly. A Logix tag can now be associated with the Advanced Diagnostic parameter. This can be done by either entering the tag name or by using the Tag Browser. NOTE: It is important to ensure that the selected Logix tag type matches the expected HART command parameter.
  • Page 27 Key Change Method This setting determines the method by which security keys are exchanged between two devices. Currently, the PLX51-HART-4I only supports the Pre-Shared Key method. This method requires both devices to have update keys entered by means outside the DNP3 protocol, (i.e. using PLX50 Configuration Utility).
  • Page 28 Configuration. Once in the configuration window, select the DNP3 tab at the top. NOTE: The actual pre-shared key cannot be included in the configuration. It can only be written to the PLX51-HART-4I when online via the Status window. Figure 3.19 – DNP3 security configuration Page 28 of 88...

  • Page 29: Module Download

    Setup 3.5. MODULE DOWNLOAD Once the PLX51-HART-4I configuration has been completed, it must be downloaded to the module. Before downloading, the Connection Path of the module must be set. This path will automatically default to the IP address of the module, as set in the module configuration. It can be modified if the PLX51-HART-4I is not on a local network.
  • Page 30 Setup To initiate the download, right-click on the module and select the Download option. Figure 3.22. - Selecting Download Once complete, you will be notified that the download was successful. Figure 3.23. - Successful download Within the PLX50 Configuration Utility, the module will be in the Online state that is indicated by the green circle around the module.

  • Page 31: Logix Integration

    ODULE TO ONFIGURATION The PLX51-HART-4I must be added to the RSLogix 5000 I/O tree as a generic Ethernet module. This is achieved by right clicking on the Ethernet Bridge in the RSLogix 5000 and selecting New Module. Then select ETHERNET-MODULE as shown in the figure below.
  • Page 32 Setup You must enter the IP address of the PLX51-HART-4I. The assembly instance and size must also be added for the input, output, and configuration in the connection parameters section. The required connection parameters for the PLX51-HART-4I are shown below:...
  • Page 33 Setup Add the connection requested packet interval (RPI). This is the rate at which the input and output assemblies are exchanged. The recommended value is 200ms. Refer to the Technical Specification section in this document for further details on the limits of the RPI. Figure 3.27 - Connection module properties in RSLogix 5000 Once the module has been added to the RSLogix 5000 I/O tree, you must assign the User Defined Types (UDTs) to the input and output assemblies.

  • Page 34: Importing Udts And Mapping Routines

    This file can be imported by right-clicking on the required Program and selecting the Import Routine option. Figure 3.29. – RSLogix 5000 Importing PLX51-HART-4I specific routine and UDTs Figure 3.30. - Selecting partial import file The import will create the following: ...
  • Page 35 Setup You may need to change the routine to map to the correct PLX51-HART-4I module instance name, and make sure that the mapping routine is called by the Program’s Main Routine. Figure 3.31. - Imported RSLogix 5000 objects Refer to the Additional Information section of this document for an example RSLogix 5000 project as well as the required UDTs.
  • Page 36 Page 36 of 88...

  • Page 37: Operation

    Operation 4. OPERATION Once the PLX51-HART-4I has been configured, it will exchange HART information between the HART field device and a Logix controller, Modbus TCP/IP Client, or DNP3 Master. 4.1. LOGIX 5000 When the module operates in a Logix “owned” mode, the Logix controller will establish a class 1 cyclic communication connection with the PLX51-HART-4I.
  • Page 38 Operation Chx_DeviceStatus.LoopOpen BOOL Loop open circuit detected. (Current < 3.6 mA) Chx_DeviceStatus.CurrentUnderrange BOOL Loop current under range. (Current < 3.8 mA) Chx_DeviceStatus.CurrentOverrange BOOL Loop current over range. (Current > 20.5 mA) Chx_DeviceStatus.LoopShorted BOOL Loop short circuit detected. (Current > 21.0 mA) Chx_DeviceStatus.CalibrationBusy BOOL Analog current calibration busy.
  • Page 39 Operation Chx_HARTStatus.Coldstart BOOL Field device power failure or device reset has occurred. Chx_HARTStatus.MoreStatusAvailable BOOL Additional status information is available. Chx_HARTStatus.LoopCurrentFixed BOOL The Loop Current is set at a fixed value and is not responding to process variations Chx_HARTStatus.LoopCurrentSaturated BOOL The Loop Current has reached its upper or lower limit.

  • Page 40: Hart Relay Message

    Operation 4.1.2. HART R ELAY ESSAGE The module supports the relaying of custom HART commands to the field device. This is achieved by building the HART command request and then sending it to the module using an explicit message instruction. An example of this is shown in the figure below: Figure 4.1.
  • Page 41 Operation The required Request and Response HART Command structures are defined as follows: HART Command Request Byte Data Offset Type Description Request Length SINT Start Character (0x82 for Long Address) SINT Long Address 0 (0x80 + Manufacturer ID) SINT Long Address 1 (Device Type Code) SINT Long Address 2 (Device ID Byte 0) SINT...
  • Page 42 Operation 4.1.2.1. HART COMMAND STATUS ENCODING The Status code returned in the HART relay command can be decoded as follows: To determine which table to use, first examine the value of the bit 7 in the first byte. If Byte 0 Bit 7 = 0 then: First Byte : Command Errors Value Description...
  • Page 43 Operation 4.1.2.2. HART COMMAND EXAMPLE In the example below, a Logix message instruction is used to read the Unique Identifier of the device. This makes use of the Universal Command #0. The field device is connected to channel 0, hence the Instance value is set to 1. Figure 4.3.
  • Page 44 Operation Figure 4.5. – Relay HART Command Example – Response NOTE: The HART Long Address is comprised of the Manufacturer ID, Device Type Code and Device ID. These values are displayed on the Channel Status screen in the PLX50 Configuration Utility when the device is Online. Page 44 of 88...

  • Page 45: Dnp3 Operation

    Operation 4.2. DNP3 OPERATION The DNP3 operation is enabled when the configuration protocol is set to either DNP3 TCP or DNP3 UDP. The PLX51-HART-4I will then operate as a DNP3 Outstation supporting the following DNP3 objects. Group: 10 - Counters...
  • Page 46 Operation Group: 102 - Unsigned 8 bit Integers Variation: Functions: Read Item Parameter Length General Channel 0 Channel 1 Channel 2 Channel 3 Module Status Bit 0 – Configuration Valid Bit 1 – Channel 0 Enabled Bit 2 – Channel 1 Enabled Bit 3 –...

  • Page 47: Dnp3 Security

    Key Changes. Thus, the Update Key needs to be entered into each device by means outside of the DNP3 protocol. In the PLX50 Configuration Utility, you can write the Update Key into the PLX51-HART-4I using the Key tab in the Online Status window. The key entered must match the Key Wrap Algorithm selected.
  • Page 48 Operation Figure 4.6 - DNP3 key update method. The module supports all DNP3 MAC algorithms and Key Wrap algorithms. The module also supports Aggressive Authentication mode which reduces the amount of traffic on the network (which could be required on busy networks or serial communication). Page 48 of 88...

  • Page 49: Modbus Tcp/Ip Operation

    Operation 4.3. MODBUS TCP/IP OPERATION The Modbus TCP/IP operation is enabled when the configuration protocol is set to either Modbus TCP/IP. The PLX51-HART-4I will then operate as a Modbus TCP/IP Server supporting the following Modbus registers. Register Type: Holding Registers 4xxxx (Function Code 3)
  • Page 50 Operation HART Statistics HART Tx Count DINT HART Rx Count DINT Communication Errors DINT Command Errors DINT Parity Errors DINT Register Type: Input Registers 3xxxx (Function Code 4) Register Byte Date Parameter Channel Channel Channel Channel Length Type General Device Process Variables Raw current REAL REAL...

  • Page 51: Diagnostics

    5.1. LEDS The module provides six LEDs for diagnostics purposes . A description of each LED is given in the table below. Figure 5.1 - PLX51-HART-4I front view Description Module The module LED will provide information regarding the system-level operation of the module.

  • Page 52: Module Status Monitoring In The Plx50 Configuration Utility

    5.2. MODULE STATUS MONITORING IN THE PLX50 CONFIGURATION UTILITY The PLX51-HART-4I can provide a range of statistics which can assist with module operation, maintenance, and fault finding. The statistics can be accessed in full by the PLX50 Configuration Utility or the web server in the module.
  • Page 53 Diagnostics The Status window contains multiple tabs to display the current status of the module. Figure 5.4. - Status monitoring – General The General tab displays the following general parameters and can also be used to set the module time to the PC time: Parameter Description Protocol...

  • Page 54: Ethernet/Ip Status

    Diagnostics 5.2.1. /IP S THER TATUS Figure 5.5 - EtherNet/IP Statistics Statistic Description Class 1 Timeout Count The number of Class 1 connections closed due to Timeouts. Class 3 Timeout Count The number of Class 3 connections closed due to Timeouts. Class 1 Forward Open Count The number of Class 1 Forward Open (connection establishment) messages sent.

  • Page 55: Dnp3

    The number of bytes with parity errors received by the module. DNP3 Request Data Too Large The request/response data is too big. The PLX51-HART-4I allows for a maximum of 1000 bytes per transaction. DNP3 Request Out of Range – Low The DNP3 request has a range that is outside of the implemented DNP3 bounds for the specific group and variation.
  • Page 56 DNP3 Request Too Many Objects The PLX51-HART-4I supports a maximum of 10 DNP3 objects in a single DNP3 request. This statistic indicates that more than 10 DNP3 objects were found in a single request.
  • Page 57 Diagnostics Figure 5.7 - DNP3 Security Statistics Statistic Description Authentication Successes Increases every time the device successfully authenticates a message. Session Key Changes When the session keys have been successfully updated. Session Key Change Failures When the session keys have failed to update. Update Key Changes The Update Key has changed.

  • Page 58: Modbus Tcp/Ip Status

    Diagnostics 5.2.3. TCP/IP S ODBUS TATUS The Modbus TCP/IP Statistics are displayed if the Modbus TCP/IP protocol has been configured. Figure 5.8. - Modbus Statistics Statistic Description Tx Packet Count The number of Modbus packets sent by the module. Rx Packet Count The number of Modbus packets received by the module.
  • Page 59 Diagnostics Address exception. Illegal Data Value The number of times the Modbus device responded with an Illegal Data Value exception. Slave Device Failure The number of times the Modbus device responded with a Device Failure exception. Acknowledge – Response Delay The number of times the Modbus device responded with an Acknowledge exception.

  • Page 60: Channel Status

    Diagnostics 5.3. CHANNEL STATUS The status of a specific channel can be monitored by double-clicking on the Channel x Status in the tree, or by right-clicking on the device and selecting the Channel x Status item. Figure 5.9 - Select Online Channel Status The channel status window contains multiple tabs to display the current status of that specific channel.

  • Page 61: General Tab

    Diagnostics 5.3.1. ENERAL The General tab displays a summary of the common HART parameters. Figure 5.10 - Channel Status – General Parameter Description The user tag name configured in the field device. (8 characters) Status The current status of the HART communication. Descriptor The user descriptor configured in the field device.

  • Page 62: Device Info Tab

    Diagnostics 5.3.2. EVICE The Device Info tab displays a more detailed information of the field device. Figure 5.11 - Channel Status – Device Info Parameter Description Manufacturer ID The field device manufacturer unique identification code. Device Type Code The device type code assigned by the manufacturer. Device ID The device identification code assigned by the manufacturer.

  • Page 63: Device Status Tab

    Diagnostics 5.3.3. EVICE TATUS The Device Status tab displays the status of the analog and HART interaction with the module. Figure 5.12 - Channel Status – Device Status Parameter Description Loop Open / Current Fault Flagged if the current loop is either below 3.6mA or above 21.0 mA. Current Under-range Flagged if the current is below 3.8 mA.
  • Page 64 Diagnostics Config Changed Flagged if an operation resulted in the configuration changing. Cold Start Flagged if the field device has experienced a power failure or reset. Flagged if the loop current is set at a fixed value and is not responding to Output Current Fixed process variations.

  • Page 65: Device Configuration Tab

    Diagnostics 5.3.4. EVICE ONFIGURATION The Device Configuration tab provides the facility to display and modify common HART parameters in the field device. Figure 5.13 - Channel Status – Device Configuration Parameter Description The user tag name configured in the field device. (8 characters). Note: The Tag, Descriptor and Date are updated together.

  • Page 66: Advanced Status Tab

    Diagnostics A parameter can be modified by entering the new value into the appropriate text box and clicking the adjacent Update button. When the parameter is pending, that is, edited but not yet committed, then the text box will be shaded yellow. Once the value has been written (updated) the value will be written to the field device and then re-read from the field device, after which the parameter background will return to normal.

  • Page 67: Hart Statistics Tab

    Diagnostics 5.3.6. HART S TATISTICS The HART Statistics tab displays the communication statistics. Figure 5.16 - Channel Status – HART Communication Statistics Parameter Description Tx Packet Count The number of HART packets sent. Rx Packet Count The number of HART packets received. Communication Errors The number of communication errors experienced.

  • Page 68: Pv Tracking Tab

    The Trend tab displays the status of the analog and HART interaction with the module. The PLX51-HART-4I is capable of storing up to 1000 trend points which are sampled at a user- configurable interval. You can choose between one of the following sources: ...
  • Page 69 Diagnostics Figure 5.18 - Channel Status – Trend Once the source or sample rate has been modified, the Apply button must be clicked for the changes to take effect. This will also result in the existing trend data being cleared. The Y-axis scale can be modified by adjusting the Min and Max value and clicking the Refresh button.

  • Page 70: Device List

    Diagnostics 5.4. DEVICE LIST The module can scan the channel to identify the short address the field device(s). You can select the start and end address to minimize the scan time. Once the scan is complete and a device is found, the device details are displayed as shown below. When you are using multiple devices on a single channel, more than one device will be displayed in this list.

  • Page 71: Calibration

    NPUT ALIBRATION To re-calibrate a PLX51-HART-4I module, 1. Using an external milliamp source, adjust the current to 4mA, or as close as possible to 4 mA. 2. Enter the exact milliamp value, read from an external meter, into the Low Value Actual numeric inputs.

  • Page 72: Module Event Log

    5.6. MODULE EVENT LOG The PLX51-HART-4I logs various diagnostic records to an internal event log. These logs are stored in non-volatile memory and can be displayed using the PLX50 Configuration Utility or via the web interface.

  • Page 73: Web Server

    Diagnostics 5.7. WEB SERVER The PLX51-HART-4I provides a web server allowing a user without the PLX50 Configuration Utility or RSLogix 5000 to view various diagnostics of the module. This includes Ethernet parameters, system event log, advanced diagnostics, and application diagnostics.
  • Page 74 Diagnostics Page 74 of 88...

  • Page 75: Asset Management Fdt/ Dtm Technology

    The PLX51-HART-4I supports FDT/DTM technology, allowing you to configure any field device using its DTM (Device Type Manager) in any standard FDT Frame (Field Device Tool). To use a field device DTM with the PLX51-HART-4I, the following Prosoft DTMs will need to first be installed: ...
  • Page 76 Asset Management FDT/ DTM Technology Page 76 of 88...

  • Page 77: What Is Hart

    What is HART? 7. WHAT IS HART? 7.1. INTRODUCTION TO HART HART is an acronym for Highway Addressable Remote Transducer. HART is able to transfer digital information across a standard 4-20 mA loop, by superimposing the digital data on the analog signal using Frequency Shift Keying (FSK).
  • Page 78 What is HART? Page 78 of 88...

  • Page 79: Technical Specifications

    Technical Specifications 8. TECHNICAL SPECIFICATIONS 8.1. DIMENSIONS Below are the enclosure dimensions as well as the required DIN rail dimensions. All dimensions are in millimetres. Figure 8.1 – PLX51-HART-4I enclosure dimensions Figure 8.2 - Required DIN dimensions Page 79 of 88...

  • Page 80: Electrical

    160mA @ 12 VDC - With 4 field devices at 22mA each. Power consumption 0.9 W – With no field devices attached. 3.1 W – With 4 field devices at 22mA each. PLX51-HART-4I ) 4.3 W – With input channels shorted. ( Connector (Power) 3-way terminal...

  • Page 81: Analog Input Channel

    247.5 Ω Accuracy (calibrated 25°C) < 0.15 % Accuracy (uncalibrated) < 0.30 % Range 0 – 22 mA Current limit 34 mA Table 8.3 - Analog Input channel specification 8.5. CERTIFICATIONS Please visit our website: www.prosoft-technology.com Page 81 of 88...
  • Page 82 Page 82 of 88...

  • Page 83: Support, Service & Warranty

    Details about the serial, Ethernet or Fieldbus devices interfaced to the module, if any. Note: For technical support calls within the United States, ProSoft’s 24/7 after-hours phone support is available for urgent plant-down issues. Detailed contact information for all our worldwide locations is available on the following page.
  • Page 84 Support, Service & Warranty Europe / Middle East / Africa Asia Pacific Regional Office Regional Office Phone: +33.(0)5.34.36.87.20 Phone: +603.7724.2080 europe@prosoft-technology.com asiapc@prosoft-technology.com Languages spoken: French, English Languages spoken: Bahasa, Chinese, English, Japanese, REGIONAL TECH SUPPORT Korean support.emea@prosoft-technology.com REGIONAL TECH SUPPORT support.ap@prosoft-technology.com...

  • Page 85: Warranty Information

    Phone: +54.911.4565.8119 scone@prosoft-technology.com Languages spoken: Spanish, English 9.2. WARRANTY INFORMATION For complete details regarding ProSoft Technology’s TERMS & CONDITIONS OF SALE, WARRANTY, SUPPORT, SERVICE AND RETURN MATERIAL AUTHORIZATION INSTRUCTIONS, please see the documents at: www.prosoft-technology.com/legal Documentation is subject to change without notice.
  • Page 86 Page 86 of 88...

  • Page 87: Index

    Index 10. INDEX HART relay message, 40 HART-4In, 32 Additional Information, 5 AES-128, 27, 47 AES-256, 27 input assembly, 37 Aggressive Mode, 27, 57 Input voltage, 10 Assembly instance, 32 Authentication, 47, 48, 57 Key Change Method, 27 Key Wrap Algorithm, 27, 47, 57 Calibration, 71 Certifications, 81 CIP Statistics, 54...
  • Page 88 Index Update Key, 47, 57 User Defined Types (UDTs), 33 Target Browser, 16 Trending, 69 Web server, 52, 73 UDT, 35 Page 88 of 88...

Table of Contents