Note: You are seeing this text-only version of our site because you are using an older browser that is not standards-compliant.
How to upgrade to a FREE standards-compliant browser.
Some Netscape 7 and Mozilla users may see this warning in error. Click here to fix the problem.

Modbus Organization

Advantages of Joining | Join Form | Toolkit | Subscribe to Newsletter

Text Size: smallmediumlarge
 Back to Company

 

ProSoft Technology Inc

ProLinx Modbus Master/Slave to HART Multi-drop 5107-MCM-HART/5127-MCM-HART2

Type:  Network Gateway
Description:  The ProLinx family Modbus Master/Slave to HART Multi-Drop communications module (5107-MCM-HART/5127-MCM-HART2) creates a powerful connection between devices on a Modbus network and HART devices. The module is a stand-alone DIN rail-mounted protocol gateway that provides one serial port and up to eight configurable HART channels. The Modbus (MCM) protocol driver supports Master and Slave implementations of the protocol. All Modbus serial ports are individually configurable, providing a very powerful and flexible host or device interface solution. 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.
Connectivity:  Modbus
Features:  This Modbus gateway is designed with both Master and Slave support; Easy connection to other Modbus devices (Modicon processors and many others); In combination with the HART device support, the module provides a powerful interface to the over 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.
Specifications:  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 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 is used to store error codes, counters, and port status information for each port; Configuration Data 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.