Functional overview, Dnp 3.0 slave port – ProSoft Technology 5201-DFNT-DNPS User Manual
Page 50
ProLinx DNPS ♦ ProLinx Gateway
Reference
DNP 3.0 Slave
User Manual
Page 50 of 86
ProSoft Technology, Inc.
December 1, 2009
3.3 Functional
Overview
The DNP 3.0 Slave protocol driver exists in a single port (DNPS) implementation
only. The DNPS port operates in a slave mode only, supporting the DNP 3.0
protocol in a Level 2 implementation.
The DNP slave driver is implemented in ProLinx modules to interface DNP
master units with a variety of communication protocols and interfaces. This driver
supports DNP version 3.0, subset level 2. The Reference chapter of this
documentation contains the Device Profile for the driver. The Reference chapter
contains the subset definition for the driver. This document serves as the base
for understanding the DNP slave driver functionality and configuration. The
discussion is general in nature deferring specifics to the individual product
documents.
Before attempting to use this or any other DNP protocol device, verify that you
have a copy of the DNP Basic 4 document and other information available
through the DNP User Group. It is very important that these documents be
understood for successful application of the protocol in a user’s solution. If you
are a member of the user group, you can download these documents from the
http://www.dnp.org (
The DNP slave driver will respond to requests from a remote DNP master device.
All data in the module’s database configured as DNP data points is available to
the remote master device for read and write requests.
3.3.1 DNP 3.0 Slave Port
ACT
ERR
Port 1
ACT
ERR
Port 2
ACT
ERR
Port 3
ACTIVE
ERR
Port 0
ACTIVE
ERR
Debug
ACT
ERR
ACT
ERR
Port 1
ACT
ERR
ACT
ERR
Port 2
ACT
ERR
ACT
ERR
Port 3
ACTIVE
ERR
Port 0
ACTIVE
ERR
Debug
The ProLinx module supports the DNP 3.0 protocol as a Slave on one port. This
port is fully configurable.