Product image for PROSOFT 5228-DFNT-HART ETHERNET/IP TO ANALOG HART - 8 CHANNEL
Email

PROSOFT 5228-DFNT-HART ETHERNET/IP TO ANALOG HART - 8 CHANNEL

Manufacturer: Prosoft Technology, Inc. | Catalog # 5228-DFNT-HART | North Coast Part # 693827
$3,708.10 /ea
ea
Log in or register to view your price, purchase history, and more!
Next Day Delivery not avail / contact sales for lead times & return policy
The HART Analog Input Gateway provides a clean way to integrate HART Analog instruments with existing controller platforms on an EtherNet/IP network. The gateway works well for field applications where it can be installed closer to HART instrument, saving on copper cable and installation costs. The gateway also saves valuable rack space for other in-chassis options. The gateways provide extremely fast channel update times (all channels updating simultaneously in 67 ms) making the HART Analog Input Gateway ideal for applications where high speeds and point-to-point connectivity are required. These gateways are available in 4 and 8 Analog input channel options. The HART Analog 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.

Manufacturer Information

Brand
Prosoft Technology

General Product Info

12-Digit UPC
992231002369
EtherNet/IP Server Specifications
  • When in the Server mode, the module accepts commands from one or more clients to read/write data stored in the module's internal registers.
EtherNet/IP (Explicit Messaging) Compatible Devices
  • List of Rockwell Automation material that support EPIC:
  • PLC5/E rev C/N, D/E, E/D
  • SLC5/05 series A, OS503 frn4
  • 1785-ENET Series A, rev D
  • Interchange V6.2
  • MicroLogix 1100/1400/ANY via 1761-NET-ENI
  • CompactLogix 1768-L43/L45 via 1768-ENBT
  • CompactLogix 1769-L32E/L35E/ANY via 1761-NET-ENI
  • RSLinx Gateway V1.7+
  • ControlLogix 1756-ENET/ENBT/EN2T
Applications
  • The DFNT-MCM modules are the ideal solution for the many applications where EtherNet/IP connectivity can be used to integrate Modbus serial devices into a system. The EtherNet/IP gateway is a powerful module designed with both Client and Server support, enabling easy connection to Rockwell Automation PLCs (CLX, SLC, PLC, CPLX, and similar devices). In combination with the Modbus device support, the module provides a very powerful interface to the many Modbus devices which are in use in the industrial marketplace today. Applications for the module are found in most industries, especially the Manufacturing, Oil and Gas, Electrical Power and Food Processing. EtherNet/IP (Explicit Messaging) Compatible Devices Rockwell Automation equipment that supports EPIC:
  • PLC5/E rev C/N, D/E, E/D
  • SLC5/05 series A, OS503 frn4
  • 1785-ENET Series A, rev D
  • Interchange V6.2
  • MicroLogix 1100/1400/ANY via 1761-NET-ENI
  • CompactLogix 1768-L43/L45 via 1768-ENBT
  • CompactLogix 1769-L32E/L35E/ANY
  • CompactLogix L23E
  • RSLinx Gateway V1.7+
  • ControlLogix 1756-ENET/ENBT/EN2T/EN2TR
EtherNet/IP Protocol Specifications
  • The EtherNet/IP protocol is one of the primary connectivity tools to the different Rockwell Automation platforms. The Explicit Messaging aspect of the protocol (only) has been implemented in the ProLinx units to provide the data transfer link between the ProLinx units and the Rockwell Automation hardware. (Implicit Messaging (I/O communications) is not supported)
Internal Database
  • The ProLinx module contains an internal database that consists of areas for application data, status information, and configuration information.
  • The internal database is shared between all ports on the module and is used as a conduit to pass information from a device on one network to one or more devices on another network.
Application Data Area
  • The data area is used to store and retrieve data by the protocol drivers and for data exchange between protocols. The database is used as a source for write commands to remote devices and holds data collected from the remote devices. Commands defined in the configuration file (stored in the configuration data area) control how the data is to be handled in the database.
Configuration File
  • This file contains module configuration information such as port configuration, network information, and command configuration. This configuration file is downloaded to, or uploaded from, the module.
Status Data Area
  • This area is used to store error codes, counters, and port status information for each port.
Compare