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 DNP 3.0 Master to Modbus Master/Slave 5102-DNPM-MCM3

Type:  Network Gateway
Description:  The ProLinx family DNP 3.0 Master to Modbus Master/Slave communications module (5102-DNPM-MCM3) creates a powerful connection between devices on a DNP network and Modbus devices. The module is a stand-alone DIN rail-mounted protocol gateway that provides up to four serial ports. The DNP 3.0 Master protocol driver supports Master implementations of the protocol on one port. This port is fully configurable, providing a great deal of flexibility. 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.
Connectivity:  Modbus
Features:  Designed with Server support; Easy connection to Rockwell Automation PLCs (CLX, SLC, PLC, CPLX, and similar devices); Provides a powerful interface to many Modbus devices; Applications for the module are found in most industries especially the manufacturing, oil and gas, electrical power and food processing.
Specifications:  Contains an internal database with areas for application data, status information, and configuration information; 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 stores and retrieves data from the protocol drivers and for data exchange between protocols; 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.