5102-DNPM-MCM3

5102-DNPM-MCM3

The ProLinx DNP 3.0 Master to Modbus Master/Slave Gateway creates a powerful connection between devices on a DNP network and Modbus devices. This stand-alone DIN-rail mounted protocol gateway 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.

The Modbus 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.

  • Description

Description

DNP 3.0 Master to Modbus Master/Slave Gateway

5102-DNPM-MCM3

The ProLinx DNP 3.0 Master to Modbus Master/Slave Gateway creates a powerful connection between devices on a DNP network and Modbus devices. This stand-alone DIN-rail mounted protocol gateway 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.

The Modbus 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.

 

Features and Benefits

Applications

The DNPM-MCM modules are the ideal solution for the many applications where DNP Master connectivity can be used to integrate Modbus devices into a system. The DNP gateway is a powerful module designed with both Server support, enabling easy connection to Rockwell Automation PLCs (CLX, SLC, PLC, CPLX, and similar devices). In combination with the Modbus device support, the module provides a very powerful interface to the many Modbus 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

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.

 

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.

 

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.

 

 

NOTE:  All products are pre-order items

Specifications, downloads & certifications