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 (3 ports) to DNP 3.0 Slave 5102-DNPS-MCM3

Type:  Network Gateway
Description:  The ProLinx family DNP 3.0 Slave to Modbus Master/Slave communication module (5102-DNPS-MCM3) creates a powerful connection between devices on a Modbus network and a DNP master device. The module is a stand-alone DIN rail-mounted protocol gateway that provides one DNP 3.0 Slave configurable serial port, and three Modbus Master or Slave configurable serial ports. The DNP 3.0 Slave protocol driver supports Slave implementations of the protocol on one port. This port is fully configurable, providing a great deal of flexibility.
Connectivity:  Modbus
Features:  Modbus connectivity can be used to integrate a DNP 3.0 Master device into a system; Designed with both Master and Slave support; Easy connection to other Modbus devices; In combination with the DNP 3.0 Slave device support, the module provides a powerful interface to the many DNP devices 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:  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.