DNP 3.0 Master/Slave

MVI69-DNP

The MVI69 DNP 3.0 module is a single slot, backplane compatible DNP 3.0 interface solution for the Rockwell Automation CompactLogix platform. This module provides highly configurable support of both DNP 3.0 Master and Slave implementations (level 2 minimum), allowing the many SCADA and field devices supporting the DNP protocol to be integrated into the powerful CompactLogix platform.

Features and Benefits

The module supports DNP Subset Level 2 features and some of the Level 3 features allowing the many SCADA and field devices supporting the DNP protocol to be integrated into the CompactLogix platform. The module acts as an input/output module between the DNP network and the CompactLogix backplane. The data transfer from the CompactLogix processor is asynchronous from the actions on the DNP network. Databases are user defined and stored in the module to hold the data required by the protocol.

Applications

The MVI69-DNP module is an ideal solution where DNP 3.0 Master/Slave protocol connectivity must be added to the CompactLogix platform.

The DNP solution addresses the expanding interest in the DNP 3.0 protocol. The protocol was originally developed for the power utility industry and is recommended by the IEEE for RTU-IED communication applications. Additional applications include Water/Wastewater and Oil and Gas industries.

Functional Specifications

The MVI69-DNP module supports the DNP 3.0 protocol with a minimum of Level 2 functionality. DNP protocol Subset Definitions for the Master and the Slave drivers are available in the module's User Manual.

The module has two DNP protocol ports that can be user configured to operate in a Master/Slave or in a Slave/Slave redundant port configuration.

User defined internal register space is accessible to the protocol driver and to the CompactLogix processor memory.

Redundant Slave Port Operation

When configured in the Slave/Slave port configuration, the module's slave ports operate in a primary and secondary fashion. In this mode, a single host polls the module via redundant physical layer connections. Several methods are supported to automatically switch between the primary and secondary slave ports.

DNP 3.0 Slave Protocol Specifications

The DNP Slave port(s) accepts DNP commands to control and monitor data stored in the module's DNP Slave databases. If a DNP Master port is also configured, a portion of these slave databases can be derived from or can control IED devices connected to the DNP master port.

• Report-by-Exception data is logged to the module's database
• Supports unsolicited messaging
• Each DNP point type is user configurable by point
• Total point counts must be configured so that Class 0 responses do not exceed 2048 bytes in size
• Class assignments are completely user-definable on a Type and point basis (BI, AI, FI, DI point types)
• The analog inputs are class and deadband configurable on a point basis for all formats (integer, float, double float)
• Supports clock synchronization from a master or from the processor
• Support for four octet-strings are supported (object type 110) in the slave driver to return version and other module information
• Up to 400 events are stored for Floats, Binary In, Analog In and Double Inputs
• In addition to the module generated events, AI and BI events can be generated in the processor and transferred to the module (useful with external timestamping hardware)
• Configurable event buffer transmission threshold based on count and/or time since last event transmission
• Collision avoidance algorithm per DNP organization for redundant port switching (redundant slave mode)
• Special modem AT command string and timing support for dialing out on redundant port (redundant slave mode)

DNP 3.0 Master Protocol Specifications

The DNP 3.0 Master port can be configured as a virtual DNP Master device that actively issues user-defined DNP commands to nodes on the network.

• The Master port supports 300 user defined commands, each one containing its own set of data link and application layer characteristics
• Master port logically supports up to 40 slave devices
• Individual command configuration includes conditional or continuous polling and Poll Delay Time
• Slave status and Command status available for transfer to the processor
• Event data received from the slave devices updates the module database (Date and Time stamping is not stored or used by module)
• Special command handling for Digital Output CROB under processor control for pulse output control
• Supports Report-by-Exception and Unsolicited Responses on a Time Interval basis or on a user determined Event Count basis. Analog and Binary input points are supported.

Debug/Configuration port (CFG)

• Communication parameters
  • Baud: 57600 (fixed)
  • Parity: none (fixed)
  • Stop: 1 (fixed)
• Configuration of module
• Communication and backplane transfer stats
• Protocol data monitor
• Internal database viewer

DNP 3.0 ports (PRT1 & PRT2)

• Memory usage is user definable
• Full radio, modem and multidrop support
• Support for the storage and transfer of all DNP data types across the backplane
• Communication parameters
  • Address: 0 to 65534 (slave mode)
  • Baud rate: 110 to 115K
  • Parity: none, data bits: 8, Stop bit: 1
  • RTS on delay: 0 to 65535 ms
  • RTS off delay: 0 to 65535 ms

Hardware Specifications

Ordering Information

Distributors:
Place your order by email to orders@prosoft-technology.com:, fax to +1 661-716-5101.

Sales and Support: