Product image for PROSOFT 5207-MNET-HART MODBUS TCP/IP TO HART MULTIDROP - 4 CHANNEL
Image thumbnail 0
Image thumbnail 1

Email

PROSOFT 5207-MNET-HART MODBUS TCP/IP TO HART MULTIDROP - 4 CHANNEL

Manufacturer: Prosoft Technology, Inc. | Catalog # 5207-MNET-HART | North Coast Part # 486675

$3,049.54 /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 ProLinx Modbus TCP/IP to HART Multi-drop Gateway creates a powerful connection between devices on an EtherNet/IP network and HART Multi-drop devices. This stand-alone DIN-rail mounted protocol gateway provides one Ethernet port and four configurable HART channels. The Modbus TCP/IP protocol driver can interface many different protocols into Schneider Electric Quantum processors as well other solutions supporting the protocol. The MNET driver supports Client and Server connections, and when coupled with the Web option provides a web/ftp interface as well. The HART protocol driver works as a Master on four (HART) or eight channels (HART2 . not available on certain configurations) per interface card, depending on implementation. Each channel is individually configurable.

Manufacturer Information

Brand
Prosoft Technology
Applications
  • The MNET-HART modules are the ideal solution for the many applications where Modbus TCP/IP connectivity can be used to integrate HART Multi-drop devices into a system. The Modbus TCP/IP gateway is a powerful module designed with both Client and Server support, enabling easy connection to other Modbus devices (Modicon processors and many others). In combination with the HART Multi-drop device support, the module provides a very powerful interface to the mor than two million HART 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 .
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.
Configuration Data Area
  • This area contains module configuration information such as port configuration, network information, and command configuration. This configuration file is downloaded to, or uploaded from, this area.
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.
Status Data Area
  • This area is used to store error codes, counters, and port status information for each port.

Compare