Image thumbnail 0
Image thumbnail 1
Image thumbnail 2



Manufacturer: Prosoft Technology, Inc. | Catalog # 5201-MNET-DNPS | North Coast Part # 439678

Log in or register to view your price, purchase history, and more!
Usually ships within 16 to 26 days
The ProLinx Modbus TCP/IP to DNP 3.0 Slave Gateway creates a powerful connection between devices on a Modbus network and DNP master devices. This standalone DIN-rail mounted protocol gateway provides one Ethernet port and one serial port. 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 DNP 3.0 Slave protocol driver supports Slave implementations of the protocol on one port. This port is fully configurable.

Technical Information

500 mA Maximum at 32 VDC Maximum
For Industries, Especially Manufacturing, Oil and Gas, Electrical Power and Food Processing
Blade Dimensions
5.2 in H x 2.07 in W x 4.52 in D Standard, 5.2 in H x 2.73 in W x 4.52 in D Extended
Connection Type
Temperature Rating
-4 to 122 F Operating, -40 to 185 F Storage
DIN Rail Mount
24 VDC Nominal, 18-32 VDC Allowed

Manufacturer Information

Family Brand Name
Prosoft Technology
Sub Brand

General Product Info

Environmental Conditions
5 - 95% Relative Humidity Non-Condensing
Modbus TCP/IP to DNP 3.0 Slave
  • The MNET-DNPS modules are the ideal solution for the many applications where Modbus TCP/IP connectivity can be used to integrate DNP Slave devices into a system. The Modbus TCP/IP gateway is a powerful module designed with both Client and Server support, enabling easy connection to Modbus Processors (Modicon and many others). In combination with the DNP 3.0 Slave device support, the module provides a very powerful interface to the many DNP 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.
Status Data Area
  • This area is used to store error codes, counters, and port status information for each port.
Internal Database
  • 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.
  • The ProLinx module contains an internal database that consists of areas for application data, status information, and configuration information.
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.