5102-DNPS-DFCM3

5102-DNPS-DFCM3

The ProLinx DNP 3.0 Slave to DF1 Master/Slave Gateway creates a powerful connection between devices on a DNP network and DF1 devices. This stand-alone DIN-rail mounted protocol gateway provides one DNP Slave serial port and three DF1 serial ports individually configurable as either Master or Slave.

The DNP 3.0 Slave protocol driver supports Slave implementations of the protocol on one port. This port is fully configurable.

The DF1 protocol driver supports Master or Slave implementations of the protocol on each DF1 port. All DF1 ports are individually configurable.

  • Description

Description

DNP 3.0 Slave to DF1 Master/Slave Gateway

5102-DNPS-DFCM3

DNP 3.0 Slave to DF1 Master Slave
DNP3 Slave to DF1 Master Slave

The ProLinx DNP 3.0 Slave to DF1 Master/Slave Gateway creates a powerful connection between devices on a DNP network and DF1 devices. This stand-alone DIN-rail mounted protocol gateway provides one DNP Slave serial port and three DF1 serial ports individually configurable as either Master or Slave.

The DNP 3.0 Slave protocol driver supports Slave implementations of the protocol on one port. This port is fully configurable.

The DF1 protocol driver supports Master or Slave implementations of the protocol on each DF1 port. All DF1 ports are individually configurable.

 

Features and Benefits

Applications

The DNPS-DFCM modules are the ideal solution for the many applications where DNP connectivity can be used to integrate DF1 Master or Slave devices into a system. The DNP 3.0 Slave gateway is a powerful module designed with level 2 Slave support, enabling easy connection between DNP masters and devices on a dissimilar network. In combination with the DF1 device support, the module provides a very powerful interface to the many DF1 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