1. Manuals
  2. Brands
  3. ProSoft Manuals
  4. I/O Systems
  5. PLX51-HART-4I
  6. User manual

ProSoft PLX51-HART-4I User Manual

Hart input/output multi-drop field devices
Hide thumbs Also See for PLX51-HART-4I:
Table of Contents

Advertisement

Quick Links

Download this manual
PLX51-HART-4I
PLX51-HART-4O
HART Input/Output
Multi-drop Field Devices
February 24, 2020
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

Related Manuals for ProSoft PLX51-HART-4I

Summary of Contents for ProSoft PLX51-HART-4I

  • Page 1 PLX51-HART-4I PLX51-HART-4O HART Input/Output Multi-drop Field Devices February 24, 2020 USER MANUAL...

  • Page 2: Table Of Contents

    Preface CONTENTS Preface ..........................5 1.1. Introduction to the PLX51-HART-4x ................5 1.2. Features ........................6 1.3. Architecture ......................... 7 1.4. Additional Information ....................9 1.5. References ......................... 10 1.6. Support ........................10 Installation ........................11 2.1. Module Layout ......................11 2.2.
  • Page 3 What is HART?........................ 114 7.1. Introduction to HART ....................114 7.2. HART Response Status .................... 115 Technical Specifications ....................116 8.1. Dimensions ......................116 8.2. Electrical ........................117 8.3. Ethernet ........................117 8.4. Analog Input ChanneL (PLX51-HART-4I) ..............118 Page 3 of 120...
  • Page 4 Preface 8.5. Analog Output ChanneL (PLX51-HART-4O) ............. 118 8.6. Certifications ......................118 Index ..........................119 Page 4 of 120...

  • Page 5: Preface

    1. PREFACE 1.1. INTRODUCTION TO THE PLX51-HART-4X The PLX51-HART-4I and PLX51-HART-4O allows the user to interface up to four analog HART channels with either EtherNet/IP, Modbus TCP/IP, DNP3 TCP/UDP, or PCCC (AB-ETH) protocols. This includes 4 to 20 mA input and output devices with or without HART communications, as well as 0 to 20 mA devices without HART.

  • Page 6: Features

    The PLX51-HART-4I or PLX51-HART-4O module is configured using the PLX50 Configuration Utility. This software can be downloaded from https://www.prosoft-technology.com free of charge. Hereafter the PLX51-HART-4I or PLX51-HART-4O module will be referred to as the module. Page 6 of 120...

  • Page 7: Architecture

    Preface 1.3. ARCHITECTURE The figure below provides an example of the typical architecture for a PLX51-HART-4I interfacing to an EtherNet/IP device (e.g. Allen-Bradley Logix Controller). Figure 1.2 – PLX51-HART-4I EtherNet/IP typical architecture The figure below provides an example of the typical architecture for a PLX51-HART-4x interfacing to a Modbus TCP/IP Client.
  • Page 8 Preface The figure below provides an example of the typical architecture for a PLX51-HART-4I interfacing to a DNP3 Master SCADA. Figure 1.4 – PLX51-HART-4I DNP3 typical architecture The figure below provides an example of the typical architecture for a PLX51-HART-4I interfacing to a SLC using PCCC.

  • Page 9: Additional Information

    Preface The figure below provides an example of the typical architecture for a PLX51-HART-4I with multidrop HART devices. Figure 1.6 – PLX51-HART-4I multidrop architecture 1.4. ADDITIONAL INFORMATION The following documents contain additional information that can assist the user with the module installation and operation.

  • Page 10: References

    Technical support is provided via the Web (in the form of user manuals, FAQ, datasheets etc.) to assist with installation, operation, and diagnostics. For additional support the user can use either of the following: Resource Link Contact Us link https://www.prosoft-technology.com/ Support email support@prosoft-technology.com Table 1.3 – Support Details Page 10 of 120...

  • Page 11: Installation

    The module provides six diagnostic LEDs as shown in the front view figure below. These LEDs are used to provide status of the module system operation, the Ethernet interface, and the status of each of the four analog HART channels. Figure 2.2 – PLX51-HART-4I front and top view Page 11 of 120...

  • Page 12: Module Mounting

    Installation The module provides four DIP switches at the top of the enclosure as shown in the top view figure above. DIP Switch Description DIP Switch 1 Used to force the module into “Safe Mode”. When in “Safe Mode” the module will not load the application firmware and will wait for new firmware to be downloaded.

  • Page 13: Power

    Installation The DIN rail clip is mounted on the bottom of the module at the back as shown in the figure below. Use a flat screwdriver to pull the clip downward. This will enable the user to mount the module onto the DIN rail. Once the module is mounted onto the DIN rail the clip must be pushed upwards to lock the module onto the DIN rail.

  • Page 14: Analog (Hart) - Single Device

    2.4. ANALOG (HART) – SINGLE DEVICE The Analog HART channels are connected using a two-way connector. The input channels (PLX51-HART-4I) are internally loop powered and therefore can be connected directly to the field device signal terminals. Figure 2.6 – PLX51-HART-4I Connection to Field Device (2-wire) The output channels (PLX51-HART-4O) source the current directly and therefore can also be connected directly to the field device signal terminals.
  • Page 15 The equivalent Analog Input and Output circuits are shown below. Figure 2.8 – Analog Input Equivalent Circuit Figure 2.9 – Analog Output Equivalent Circuit The PLX51-HART-4I module supports 2-wire (loop-powered) and 4-wire devices in various configurations as illustrated below. Figure 2.10 – Channel Connection - 2-wire – Module Powered...
  • Page 16 Installation Figure 2.11 – Channel Connection - 4-wire – Device Powered Figure 2.12 – Channel Connection - 2-wire – Externally Powered Figure 2.13 – Channel Connection - 2-wire – Externally Powered with External Resistor Page 16 of 120...

  • Page 17: Analog (Hart) - Multidrop

    2. (Assuming a typical minimum of 10V, and a supply of 24V). This would apply to each channel of both the PLX51-HART-4O and the PLX51-HART-4I. As indicated in the diagrams below, the PLX51-HART-4I can support multi-drop devices in series with either module-powered or externally-powered configurations.

  • Page 18: Parallel Configuration

    In the case where output field devices attempt to draw more than 4 mA in this mode, the number of allowable multidrop devices reduces. As indicated in the diagrams below, the PLX51-HART-4I can support multi-drop devices in parallel with either module-powered or externally-powered configurations.

  • Page 19: Ethernet Port

    Installation Figure 2.17 – PLX51-HART-4I - Multidrop Wiring – Parallel – Module Powered Figure 2.18 – PLX51-HART-4I - Multidrop Wiring – Parallel – Externally Powered Figure 2.19 – PLX51-HART-4O - Multidrop Wiring – Parallel *NOTE: It is not recommended to multidrop 4-wire devices unless all devices make use of isolated power supplies.

  • Page 20: 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 20 of 120...

  • Page 21: Network Parameters

    Setup 3.2. NETWORK PARAMETERS The module will have 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 that the DHCP server in the PLX50 Configuration Utility be used.
  • Page 22 Setup NOTE: If the DHCP requests are not displayed in the DHCP Server, it may be due to the local PC’s firewall. During installation, the necessary firewall rules are automatically created for the Windows firewall. Another possibility is that another DHCP Server is operational on the network and it has assigned the IP address.
  • Page 23 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 24 Setup Right-clicking on a device, reveals the context menu, including the Port Configuration option. Figure 3.8 - Selecting Port Configuration All the relevant 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 25: Creating A New Project

    Add under the Device menu. Figure 3.11 - Adding a new device In the Add New Device window select the PLX51-HART-4I or PLX51-HART-4O and click the Ok button. The configuration of the PLX51-HART-4I or PLX51-HART-4O are almost identical.
  • Page 26 Setup Figure 3.12 – Selecting a new module The device will appear in the Project Explorer tree as shown below, and 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 27: Module Parameters

    Setup 3.4. MODULE PARAMETERS The configuration form is divided into multiple tabs to configure the general, communication and channel specific parameters. When downloading this configuration into the module it will be saved in non-volatile memory that persists when the module is powered down. NOTE: When a firmware upgrade is performed the module will clear all configuration.
  • Page 28 Setup The general configuration consists of the following parameters: Parameter Description Instance Name This parameter is a user defined name to identify between various modules. Description This parameter is used to provide a more detail description of the application for the module.
  • Page 29 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. Figure 3.15 - Channel configuration (PLX51-HART-4I) Page 29 of 120...
  • Page 30 Setup Figure 3.16 - Channel configuration (PLX51-HART-4O) Each of the channel configuration tabs consist of the following parameters: Parameter Description Enable Channel Used to Enable or Disable the entire analog channel. Signal Select either 4-20 mA or 0-20 mA. Range Note that HART communication will be disabled if the 0-20 mA range has been selected.
  • Page 31 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 32 Setup This configuration is used to determine the behaviour of the output analog signal when communication from the source (EtherNet/IP, DNP3 or Modbus TCP/IP) is lost. Comm Fail Freeze Enabling this option freezes the output value to its last state, when communication is lost.

  • Page 33: Advanced Mapping

    Setup 3.5. ADVANCED MAPPING The module supports multidrop functionality on each channel (having multiple HART devices per channel) as well as the asynchronous reading of advanced diagnostic parameters, which are then written directly to Logix tags. NOTE: Advanced Mapping is NOT supported for the DNP3 interface protocol. NOTE: Diagnostics is supported ONLY for the EtherNet/IP interface protocol.
  • Page 34 Setup The Advanced Mapping configuration tab consists of the following parameters: Parameter Description Action Diagnostics When the Diagnostics option is selected, the user will be able to configure a specific HART command that must be sent to the “main” device (usually at the specified fixed address). The result will then be written to a configured Logix tag thus allowing the user to extract device specific diagnostics from a field device.
  • Page 35 Setup When using the Diagnostics Action; to create a new Advanced Diagnostic item, select the Build button. The HART Advanced Diagnostic Builder will open. Figure 3.19 – Advanced Diagnostic Builder The builder is used to generate the command, and to define the Data Type. The following parameters need to be configured: Parameter Description...
  • Page 36 Setup Once accepted, the full command string will be built, and the current map item will be updated 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 to browse for a tag. NOTE: It is important to ensure that the selected Logix tag type matches that of the expected HART command parameter.

  • Page 37: Dnp3 Security

    Setup 3.6. DNP3 SECURITY If one of the DNP3 protocols (DNP3 TCP or DNP3 UDP) have been selected, then the DNP3 Security tab will be enabled. This DNP3 Security configuration consists of the following parameters: Parameter Description Enable Security DNP3 Secure Authentication can be enabled or disabled. When enabled there will be no unsecured exchange of data (for critical functions).
  • Page 38 Setup The security configuration is shown in the figure below. The DNP3 Security configuration window is opened by either double-clicking on the module in the tree or right clicking the module and selecting Configuration. Once in the configuration window select the DNP3 tab at the top.

  • Page 39: Multidrop

    Setup 3.7. MULTIDROP When using Multidrop and requiring a HART device at a specific address to be the “main” HART device (e.g. which will be populated in the Logix Input Assembly), then the Fixed HART Address parameter must be used (see below). This will ensure that the specified address is used as the main.
  • Page 40 Setup The user will need to ensure that each field device on the drop has a unique node address. This can be verified by initiating a Device Scan and checking that each field device on the network has a unique address (as shown below): Figure 3.23 –...
  • Page 41 Setup Figure 3.25 – Set Field Device Node Address The user will also need to ensure that each field device on the drop has its loop current mode set to Multidrop and NOT Current Signalling Mode. This can be achieved by using the Write Address option (as shown above) and unchecking the loop current mode in the PLX50 Configuration Utility as shown below: Figure 3.26 –...

  • Page 42: Module Download

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

  • Page 44: Logix Integration

    The required connection parameters for the PLX51-HART-4I module are shown below: Connection Parameter Assembly Instance Size Input 119 (32-bit) Output 1 (32-bit) Configuration 0 (8-bit) Table 3.5 - RSLogix class 1 connection parameters for the PLX51-HART-4I module Page 44 of 120...
  • Page 45 Setup Figure 3.33 - RSLogix 5000 General module properties for PLX51-HART-4I module The required connection parameters for the PLX51-HART-4O module are shown below: Connection Parameter Assembly Instance Size Input 119 (32-bit) Output 4 (32-bit) Configuration 0 (8-bit) Table 3.6 - RSLogix class 1 connection parameters for the PLX51-HART-4O module Figure 3.34 - RSLogix 5000 General module properties for PLX51-HART-4O module...
  • Page 46 Setup NOTE: The user will need to enter the exact connection parameters before the module will establish a class 1 connection with the Logix controller. Next the user needs to add the connection requested packet interval (RPI). This is the rate at which the input and output assemblies are exchanged.

  • Page 47: Importing Udts And Mapping Routines

    The import will create the following:  The required UDTs (user defined data types)  Controller tags representing the Input and Output assemblies.  A routine mapping the PLX51-HART-4I and PLX51-HART-4O modules to the aforementioned tags. Page 47 of 120...
  • Page 48 Setup The user may need to change the routine to map to the correct module instance name, and make sure that the mapping routine is called by the Program’s Main Routine. Figure 3.39 - 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 49: Operation

    1 cyclic communication connection with the module. An input and output assembly is exchanged at the configured (RPI) interval. 4.1.1. NPUT SSEMBLY The following parameters are used in the input assembly of the PLX51-HART-4I and PLX51- HART-4O modules. Parameter Datatype Description...
  • Page 50 Operation Chx_DeviceID DINT The device identification code specified by the manufacturer. Chx_Tag STRING8 Tag name of the field device. Chx_Descriptor STRING16 Descriptor of the field device. Chx_DeviceStatus SINT Device Status comprising the following bits: Chx_DeviceStatus.LoopOpen BOOL Loop open circuit detected. (Current < 3.6 mA) Chx_DeviceStatus.CurrentUnderrange BOOL Loop current under range.
  • Page 51 Operation Chx_HARTStatus.DeviceBusy BOOL Device Busy. Chx_HARTStatus.CommandNotImplemented BOOL Command not supported. Chx_HARTStatus.DeviceMalfunction BOOL Device Malfunction. Chx_HARTStatus.ConfigurationChanged BOOL Configuration changed. Chx_HARTStatus.Coldstart BOOL Field device power failure or device reset. Chx_HARTStatus.MoreStatusAvailable BOOL Additional status information is available. Chx_HARTStatus.LoopCurrentFixed BOOL Loop Current is set at a fixed value and is not responding to process variations Chx_HARTStatus.LoopCurrentSaturated BOOL...

  • Page 52: Output Assembly

    Operation 4.1.2. UTPUT SSEMBLY The following parameters are used in the output assembly of the PLX51-HART-4O module. Parameter Datatype Description Ch0_Data REAL Analog output value (in engineering units) for Channel 0. Ch1_Data REAL Analog output value (in engineering units) for Channel 1. Ch2_Data REAL Analog output value (in engineering units) for Channel 2.
  • Page 53 Operation The required attributes for the message instruction are as follows: Figure 4.2 – Relay HART Message Configuration Parameter Value / Description Message Type CIP Generic Service Type Custom Service Code 79 Hex (Relay HART Message service) Class 40F Hex Instance Channel value + 1 1 for Channel 0...
  • Page 54 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 55 Operation 4.1.3.1. HART COMMAND STATUS ENCODING The Status code returned in the HART relay command are as follows: Examine the value of the bit 7 in the first byte. If Byte 0 Bit 7 = 0 then: First Byte : Command Errors Value Description No error...
  • Page 56 Operation 4.1.3.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 set to 1. Figure 4.3 –...

  • Page 57: Multidrop

    Operation Figure 4.5 – Relay HART Command Example – Response NOTE: The HART Long Address for a device 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 58 Operation Once the Logix tags for each multidrop HART device have been selected, the PLX51-HART-4x will automatically update the Logix tags with the data from each multidrop HART device on each HART channel. 4.1.4.1. MULTIDROP UDT STRUCTURE Figure 4.7 – Multidrop – UDT Page 58 of 120...
  • Page 59 Operation Parameter Datatype Description PollStatus SINT Bit 0 – When set this bit will indicate that the device is online LastStatusByte SINT The first byte of the field device HART response status. See the HART section at the end of this document for details regarding the HART status.
  • Page 60 Operation PVURLLRV_Units SINT PV Upper and Lower Range Values Units Code WriteProtectionCode SINT Write Protection Code PrivateLabelCode SINT Private Label Distributor Code PVAnalogChFlag SINT PV Analog Channel Flags REAL Primary Variable in engineering units. REAL Secondary Variable in engineering units. REAL Third Variable in engineering units.
  • Page 61 Operation 4.1.4.2. MULTIDROP LEGACY (MVI56) UDT STRUCTURE Figure 4.8 – Multidrop – Legacy UDT Parameter Datatype Description Auto_Poll_CMD_Status SINT Bit 0 – When set this bit will indicate that the device is online Last_Status_Byte SINT The first byte of the field device HART response status.
  • Page 62 Operation Universal_CMD_Major SINT Universal Command Major Revision Number. Device Revision Number. Device_Rev_Level SINT Software_Rev_Level SINT Software Revision Number. Hardware_Rev_Level SINT Hardware Revision Number. Device_Flags SINT Device Function Flags. Bit 0 – Multi Sensor device Bit 1 – EEPROM control required Bit 2 –...
  • Page 63 Operation Min_span REAL Minimum Span PV_URV REAL PV Upper Rage Value PV_LRV REAL PV Lower Range Value PV_damp REAL PV Damping Value (s) Table 4.9 – Multidrop UDT structure Page 63 of 120...

  • Page 64: 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 module will then operate as a DNP3 Outstation supporting the following DNP3 objects. Group: 10 - Counters Variation: Functions: Read...
  • Page 65 Operation Group: 41 - Analog Outputs Variation: 1,2,3,4 Functions: Select, Operate, Direct Operate, Direct Operate w/o Ack. Item Parameter Length General Channel 0 Channel 1 Channel 2 Channel 3 Output Value Group: 102 - Unsigned 8-bit Integers Variation: Functions: Read Item Parameter Length...

  • Page 66: Dnp3 Security

    Operation NOTE: When using the Select, Operate, Direct Operate and Direct Operate without Acknowledge functions, only one item can be addressed at a time. 4.2.1. DNP3 S ECURITY DNP3 offers Secure Authentication for links at risk of being attacked. There are various Key Change methods, Message Authentication Code (MAC) algorithms, and Authentication methods provided in the DNP3 protocol specification.
  • Page 67 Operation Figure 4.9 - HART 4 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 67 of 120...

  • Page 68: 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 Modbus TCP/IP. The module will then operate as a Modbus TCP/IP Server supporting the following Modbus registers for the main device. Register Type: Holding Registers Register Byte...
  • Page 69 Operation Descriptor BYTE[16] Date BYTE[3] HART Statistics HART Tx Count DINT HART Rx Count DINT Communication Errors DINT Command Errors DINT Parity Errors DINT Output Data Output Process Variable REAL Register Type: Input Registers Register Byte Date Parameter Channel Channel Channel Channel Length...

  • Page 70: Multidrop

    Operation 4.3.1. ULTIDROP When multidrop is being used for HART devices the data from each device will automatically be updated to the specific Multidrop Device Index (MD). The table below indicates the Modbus location for the associated data. Figure 4.10 - Setting Multidrop Device Index Register Type: Holding Registers Register...
  • Page 71 Operation Multidrop Device Index (MD) - 1 Poll Status 1100 2100 3100 4100 Manufacturer ID 1101 2101 3101 4101 BYTE Mfg Device Type Code BYTE Number of Preambles Required BYTE 1102 2102 3102 4102 Universal Command Rev BYTE Device Specific Command Rev 1103 2103 3103...
  • Page 72 Operation Sensor Minimum Span 1216 2216 3216 4216 REAL 1218 2218 3218 4218 BYTE[8] Descriptor 1222 2222 3222 4222 BYTE[16] Date 1230 2230 3230 4230 BYTE[3] Multidrop Device Index (MD) – 3 Poll Status 1300 2300 3300 4300 Manufacturer ID 1301 2301 3301...
  • Page 73 Operation Sensor Serial Number 1410 2410 3410 4410 BYTE[3] Units Code for Sensor BYTE Sensor Upper Limit 1412 2412 3412 4412 REAL Sensor Lower Limit 1414 2414 3414 4414 REAL Sensor Minimum Span REAL 1416 2416 3416 4416 1418 2418 3418 4418 BYTE[8]...
  • Page 74 Operation Max Number of Device Vars BYTE Config Change Count 1608 2608 3608 4608 Extended Device Status 1609 2609 3609 4609 BYTE Pad Byte BYTE Sensor Serial Number BYTE[3] 1610 2610 3610 4610 Units Code for Sensor BYTE Sensor Upper Limit 1612 2612 3612...
  • Page 75 Operation REAL 1302 2302 3302 4302 REAL 1304 2304 3304 4304 REAL 1306 2306 3306 4306 SINT 1308 2308 3308 4308 PV units code SV units code SINT SINT 1309 2309 3309 4309 TV units code SINT FV units code Multidrop Device Index (MD) - 4 REAL 1400...

  • Page 76: Pccc Operation

    Operation 4.4. PCCC OPERATION The PCCC operation is enabled when the configuration protocol is set to SLC 500 / MicroLogix / PLC5. The module will then operate as a PCCC (AB-ETH) Slave allowing SLC500, MicroLogix, and PLC5 controllers to read and write data to the HART devices. NOTE: Only SLC Typed Read and SLC Typed Write commands are supported by the PLX51-HART-4x when operating in PCCC mode.

  • Page 77: Multidrop

    Operation TV Unit N10:7 N11:7 N12:7 N13:7 FV Unit N10:8 N11:8 N12:8 N13:8 Floats PV Value F20:0 F21:0 F22:0 F23:0 SV Value F20:1 F21:1 F22:1 F23:1 TV Value F20:2 F21:2 F22:2 F23:2 FV Value F20:3 F21:3 F22:3 F23:3 Analog Value F20:4 F21:4 F22:4...
  • Page 78 Operation Files Parameter Channel 0 Channel 1 Channel 2 Channel 3 Integers Multidrop Device Index (MD) - 0 Poll Status N10:10 N11:10 N12:10 N13:10 Bit 0 – When set this bit will indicate that the device is online Manufacturer ID N10:11 N11:11 N12:11...
  • Page 79 Operation SV Unit N10:35 N11:35 N12:35 N13:35 TV Unit N10:36 N11:36 N12:36 N13:36 FV Unit N10:37 N11:37 N12:37 N13:37 Multidrop Device Index (MD) - 4 Poll Status N10:38 N11:38 N12:38 N13:38 Bit 0 – When set this bit will indicate that the device is online Manufacturer ID N10:39...
  • Page 80 Operation SV Value F20:15 F21:15 F22:15 F23:15 TV Value F20:16 F21:16 F22:16 F23:16 FV Value F20:17 F21:17 F22:17 F23:17 Multidrop Device Index (MD) - 2 PV Value F20:18 F21:18 F22:18 F23:18 SV Value F20:19 F21:19 F22:19 F23:19 TV Value F20:20 F21:20 F22:20 F23:20...

  • Page 81: Ftview Operation

    Operation 4.5. FTVIEW OPERATION The module supports direct EDS parameter access allowing FTView to read main and multidrop process variables directly. 4.5.1. EDS F EGISTER Before FTView can access the HART data from the module, the module’s EDS file must be registered on that system.

  • Page 82: Configure Ftview Communication

    Operation 4.5.2. ONFIGURE OMMUNICATION Within the FTView environment, (either SE or ME,) using either a new or existing project ensure that the RSLinx Enterprise server has been added. To add the RSLinx Enterprise communication server, right-click on the project server in the project tree and select the Add New Server option, and then the Rockwell Automation Device Server (RSLinx Enterprise).
  • Page 83 Operation The RSLinx Enterprise item will then appear in the FTView project tree. Right-click on the Communication Setup option under this item. Figure 4.16 – Open Communication Setup The Communication Setup window, allows the user to associate a Device Shortcut to the physical module.

  • Page 84: Displaying Process Variable

    Operation A warning, similar to the one below, will be shown. Select the Yes option to continue and accept the changes. Figure 4.18 – Confirm RSLinx Enterprise shortcut 4.5.3. ISPLAYING ROCESS ARIABLE A Numeric Display can now be added to a FTView display to show a HART module parameter. Open a new or existing display, and using the menu or toolbar, add a Numeric Display object.
  • Page 85 Operation Figure 4.20 – Tag Browser – Refreshing All Folders Once refreshed, all the HART module parameters will appear under the Offline section. Figure 4.21 – Tag Browser – Select Tag Select the required parameter (process variable or status) tag, and press Ok. The selected tag will appear in the Numeric Display’s Expression textbox.
  • Page 86 Operation Figure 4.22 – Configure Numeric Display The Numeric Display can be tested by using FTView’s Test Display option. If the module is online and configured correctly, the selected parameter will be displayed. Figure 4.23 – Testing Display Page 86 of 120...

  • Page 87: Diagnostics

    Diagnostics 5. DIAGNOSTICS 5.1. LEDS The module provides six LEDs for diagnostics purposes as shown in the front view figure below. A description of each LED is given in the table below. Figure 5.1 - Module front view Description Module The module LED will provide information regarding the system-level operation of the module.

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

    Diagnostics 5.2. MODULE STATUS MONITORING IN THE PLX50 CONFIGURATION UTILITY The module 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 using the web server in the module. To view the module’s status in the PLX50 Configuration Utility environment, the module must be online.
  • Page 89 Diagnostics Figure 5.3 - Selecting online Status The Status monitoring window can be opened by either double-clicking on the Status item in the Project Explorer tree, or by right-clicking on the module and selecting Status. The status window contains multiple tabs to display the current status of the module. Most of these parameters in the status windows are self-explanatory or have been discussed in previous sections.
  • Page 90 Diagnostics 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 Indicates the current configured protocol: EtherNet/IP DNP3 TCP DNP3 UDP Modbus TCP/IP SLC500 / MicroLogix / PLC5 (PCCC) Owned Indicates whether or not the module is currently owned (Class 1) by a Logix controller.

  • Page 91: 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 92: Dnp3

    Diagnostics 5.2.2. DNP3 The DNP3 Statistics and DNP3 Security Statistics will be displayed if either of the two DNP3 protocols have been configured. Figure 5.6 - DNP3 Statistics Statistic Description Application Messages Tx The number of application DNP3 packets sent by the module. Application Messages Rx The number of application DNP3 packets received by the module.
  • Page 93 Diagnostics DNP3 bounds for the specific group and variation. This error is specific to the range being lower than the implemented range. DNP3 Request Out of Range – High The DNP3 request has a range that is outside of the implemented DNP3 bounds for the specific group and variation.
  • Page 94 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 95: Modbus

    Diagnostics 5.2.3. ODBUS The Modbus Statistics will be 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. Checksum errors The number of corrupted Modbus packets received by the module.
  • Page 96 Diagnostics 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 97: Pccc

    Diagnostics 5.2.4. PCCC The PCCC Statistics will be displayed if the PCCC protocol has been configured. Figure 5.9 - PCCC Statistics Statistic Description Connection Requests The number of PCCC connection establishment requests received. Read Requests The number of Read requests received. Write Requests The number of Write requests received.

  • Page 98: 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.10 - Select Online Channel Status The channel status window contains multiple tabs to display the current status of that specific channel.
  • Page 99 Diagnostics 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. (16 characters) Manufacturer The field device manufacturer. Device Type The device type code assigned by the manufacturer.
  • Page 100 Diagnostics The Device Info tab displays a more detailed information of the field device. Figure 5.12 - 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 101 Diagnostics The Device Status tab displays the status of the analog and HART interaction with the module. Figure 5.13 - 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.8mA.
  • Page 102 Diagnostics 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 Analog Output Saturated Flagged if the Loop Current has reached its upper or lower limit Variable Out of Limits Flagged if a variable other than the PV is beyond its operating limits.
  • Page 103 Diagnostics signal. Note: The LRV, URV and Range Units are updated together. The engineering units in which the LRV and URV values are specified. Range Units Note: The LRV, URV and Range Units are updated together. The damping value specified in seconds. Damping refers to the digital filtering of process variables to remove transient and potentially erroneous deviations from Damping the actual measure variable.
  • Page 104 Diagnostics The Advanced Status tab displays the advanced and device specific status information of the field device. Due to the manufacturer specific encoding of these parameters, consult the field device manufacturer’s documentation for more information. Figure 5.16 - Channel Status – Advanced Status The HART Statistics tab displays the communication statistics.
  • Page 105 Diagnostics 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. Command Errors The number of command errors experienced. Time-Out Errors The number of HART time-out errors experienced. Relay Message Tx Count The number of HART packets sent via relay (Class 2) messages (DTMs etc.) Relay Message Rx Count...
  • Page 106 Diagnostics The Trend tab displays the status of the analog and HART interaction with the module. The module is capable of storing up to 1000 trend points which are sampled at a user- configurable interval. The user can choose between one of the following sources: ...

  • Page 107: Device List

    Diagnostics 5.4. DEVICE LIST The module supports scanning a channel to determine at which short address the field device(s) are. The user can select the start and end address to minimize the scan time. Once the scan is completed and a device is found the devices details will be displayed in the list as shown below.

  • Page 108: Multidrop

    Diagnostics 5.5. MULTIDROP The MultiDrop tab will have all the configured multidrop devices, their Status, as well as the four process variables for each multidrop HART device. Figure 5.22 – Channel Status – MultiDrop 5.6. CALIBRATION The Calibration tab in the Channel status monitoring form, can be used to display and modify the calibration parameters.

  • Page 109: Plx51-Hart-4I Calibration

    5.6.1. PLX51-HART-4I C ALIBRATION To re-calibrate a PLX51-HART-4I module, 1. Using an external milliamp source, adjust the current to 4 mA, 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 110: Plx51-Hart-4O Calibration

    Diagnostics 5.6.2. PLX51-HART-4O C ALIBRATION To re-calibrate a PLX51-HART-4O module: 1. Ensure the channel configuration has both the Prog/Fault Freeze and Comm Fail Freeze options checked, and that the module is disconnected from the EtherNet/IP (Logix), DNP3 or Modbus source. 2.

  • Page 111: Module Event Log

    Diagnostics 5.7. MODULE EVENT LOG The module 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. To view them in the PLX50 Configuration Utility, select the Event Viewer option in the Project Explorer tree.

  • Page 112: Web Server

    Diagnostics 5.8. WEB SERVER The module 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. NOTE: The web server is view only and thus no parameters or configuration can be altered from the web interface.

  • Page 113: Asset Management Fdt - Dtm Technology

    The module supports FDT / DTM technology, allowing the user 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 module, the following Prosoft DTMs will need to first be installed: ...

  • Page 114: 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 115: Hart Response Status

    What is HART? 7.2. HART RESPONSE STATUS If Byte 0 Bit 7 = 0 then: First Byte : Command Errors Value Description No error (Undefined) Invalid selection Passed parameter too large Passed parameter too small Too few data bytes received Transmitter specific error In write-protect mode 8-15...

  • Page 116: 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 – module enclosure dimensions Figure 8.2 - Required DIN dimensions Page 116 of 120...

  • Page 117: 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. 4.3 W – With input channels shorted. (PLX51-HART-4I) Connector (Power) 3-way terminal Connector (Analog)

  • Page 118: Analog Input Channel (Plx51-Hart-4I)

    Technical Specifications 8.4. ANALOG INPUT CHANNEL (PLX51-HART-4I) Specification Rating Number of channels ADC resolution 12 bit Input impedance 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...
  • Page 119 Index 9. INDEX HART-4In, 44 HART-4Out, 45 Additional Information, 9 AES-128, 37, 66 AES-256, 37 input assembly, 49 Aggressive Mode, 37, 94 Input voltage, 13 Assembly instance, 44 Authentication, 66, 67, 94 Key Change Method, 37 Key Wrap Algorithm, 37, 66, 94 Calibration, 108 Certifications, 118 CIP Statistics, 91...
  • Page 120 Index User Defined Types (UDTs), 46 Target Browser, 23 Trending, 106 Web server, 88, 112 Update Key, 66, 94 Page 120 of 120...

This manual is also suitable for:

Plx51-hart-4o

Table of Contents