MVI56-DNPSNET
ControlLogix Platform
DNP 3.0 Server over Ethernet
Communication Module
February 11, 2011
USER MANUAL
Your Feedback Please
We always want you to feel that you made the right decision to use our products. If you have suggestions, comments,
compliments or complaints about our products, documentation, or support, please write or call us.
How to Contact Us
ProSoft Technology
5201 Truxtun Ave., 3rd Floor
Bakersfield, CA 93309
+1 (661) 716-5100
+1 (661) 716-5101 (Fax)
www.prosoft-technology.com
support@prosoft-technology.com
Copyright © 2011 ProSoft Technology, Inc., all rights reserved.
MVI56-DNPSNET User Manual
February 11, 2011
ProSoft Technology ®, ProLinx ®, inRAx ®, ProTalk ®, and RadioLinx ® are Registered Trademarks of ProSoft
Technology, Inc. All other brand or product names are or may be trademarks of, and are used to identify products
and services of, their respective owners.
ProSoft Technology® Product Documentation
In an effort to conserve paper, ProSoft Technology no longer includes printed manuals with our product shipments.
User Manuals, Datasheets, Sample Ladder Files, and Configuration Files are provided on the enclosed CD-ROM,
and are available at no charge from our web site: www.prosoft-technology.com
Printed documentation is available for purchase. Contact ProSoft Technology for pricing and availability.
North America: +1.661.716.5100
Asia Pacific: +603.7724.2080
Europe, Middle East, Africa: +33 (0) 5.3436.87.20
Latin America: +1.281.298.9109
Important Installation Instructions
Power, Input, and Output (I/O) wiring must be in accordance with Class I, Division 2 wiring methods, Article 501-4 (b)
of the National Electrical Code, NFPA 70 for installation in the U.S., or as specified in Section 18-1J2 of the Canadian
Electrical Code for installations in Canada, and in accordance with the authority having jurisdiction. The following
warnings must be heeded:
WARNING - EXPLOSION HAZARD - SUBSTITUTION OF COMPONENTS MAY IMPAIR SUITABILITY FOR CLASS
I, DIV. 2;
WARNING - EXPLOSION HAZARD - WHEN IN HAZARDOUS LOCATIONS, TURN OFF POWER BEFORE
REPLACING OR WIRING MODULES
WARNING - EXPLOSION HAZARD - DO NOT DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN
SWITCHED OFF OR THE AREA IS KNOWN TO BE NON-HAZARDOUS.
THIS DEVICE SHALL BE POWERED BY CLASS 2 OUTPUTS ONLY.
MVI (Multi Vendor Interface) Modules
WARNING - EXPLOSION HAZARD - DO NOT DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN
SWITCHED OFF OR THE AREA IS KNOWN TO BE NON-HAZARDOUS.
AVERTISSEMENT - RISQUE D'EXPLOSION - AVANT DE DÉCONNECTER L'ÉQUIPEMENT, COUPER LE
COURANT OU S'ASSURER QUE L'EMPLACEMENT EST DÉSIGNÉ NON DANGEREUX.
Warnings
North America Warnings
Power, Input, and Output (I/O) wiring must be in accordance with Class I, Division 2 wiring methods, Article 501-4 (b)
of the National Electrical Code, NFPA 70 for installation in the U.S., or as specified in Section 18-1J2 of the Canadian
Electrical Code for installations in Canada, and in accordance with the authority having jurisdiction. The following
warnings must be heeded:
A Warning - Explosion Hazard - Substitution of components may impair suitability for Class I, Division 2.
B Warning - Explosion Hazard - When in hazardous locations, turn off power before replacing or rewiring modules.
C Warning - Explosion Hazard - Do not disconnect equipment unless power has been switched off or the area is
known to be non-hazardous.
Avertissement - Risque d'explosion - Avant de déconnecter l'équipement, couper le courant
ou s'assurer que l'emplacement est désigné non dangereux.
D Suitable for use in Class I, Division 2 Groups A, B, C and D Hazardous Locations or Non-Hazardous Locations.
ATEX Warnings and Conditions of Safe Usage
Power, Input, and Output (I/O) wiring must be in accordance with the authority having jurisdiction.
A Warning - Explosion Hazard - When in hazardous locations, turn off power before replacing or wiring modules.
B Warning - Explosion Hazard - Do not disconnect equipment unless power has been switched off or the area is
known to be non-hazardous.
C These products are intended to be mounted in an IP54 enclosure. The devices shall provide external means to
prevent the rated voltage being exceeded by transient disturbances of more than 40%. This device must be used
only with ATEX certified backplanes.
D DO NOT OPEN WHEN ENERGIZED.
Battery Life Advisory
The MVI46, MVI56, MVI56E, MVI69, and MVI71 modules use a rechargeable Lithium Vanadium Pentoxide battery to
backup the real-time clock and CMOS. The battery should last for the life of the module. The module must be
powered for approximately twenty hours before the battery becomes fully charged. After it is fully charged, the battery
provides backup power for the CMOS setup and the real-time clock for approximately 21 days. When the battery is
fully discharged, the module will revert to the default BIOS and clock settings.
Note: The battery is not user replaceable.
Markings
Electrical Ratings
Backplane Current Load: 800 mA @ 5.1 Vdc; 3 mA @ 24 Vdc
Operating Temperature: 0°C to 60°C (32°F to 140°F)
Storage Temperature: -40°C to 85°C (-40°F to 185°F)
Shock: 30 g, operational; 50 g, non-operational; Vibration: 5 g from 10 Hz to 150 Hz
Relative Humidity: 5% to 95% with no condensation
All phase conductor sizes must be at least 1.3 mm(squared) and all earth ground conductors must be at least
4mm(squared).
Label Markings
ATEX
II 3 G
EEx nA IIC T6
0°C <= Ta <= 60°C
cULus
E183151
Class I Div 2 Groups A,B,C,D
T6
-30°C <= Ta <= 60°C
Agency Approvals and Certifications
Agency Applicable Standard
RoHS
CE EMC-EN61326-1:2006; EN61000-6-4:2007
ATEX EN60079-15:2003
cULus UL508; UL1604; CSA 22.2 No. 142 & 213
CB Safety CA/10533/CSA
IEC 61010-1 Ed.2; CB 243333-2056722 (2090408)
GOST-R EN 61010
CSA EN 61010
243333
ME06
E183151
MVI56-DNPSNET ♦ ControlLogix Platform Contents
DNP 3.0 Server over Ethernet Communication Module User Manual
Contents
Your Feedback Please ........................................................................................................................ 2
How to Contact Us .............................................................................................................................. 2
ProSoft Technology® Product Documentation .................................................................................... 2
Important Installation Instructions ....................................................................................................... 3
MVI (Multi Vendor Interface) Modules ................................................................................................ 3
Warnings ............................................................................................................................................. 3
Battery Life Advisory ........................................................................................................................... 4
Markings .............................................................................................................................................. 4
Guide to the MVI56-DNPSNET User Manual 9
1 Start Here 11
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9
1.7.1
1.7.2
1.7.3
System Requirements ............................................................................................. 12
Package Contents ................................................................................................... 13
Installing ProSoft Configuration Builder Software ................................................... 14
Setting Jumpers ...................................................................................................... 15
Installing the Module in the Rack ............................................................................ 16
Connecting Your PC to the ControlLogix Processor ............................................... 17
Opening the Sample Ladder Logic .......................................................................... 18
Determining the Firmware Version of Your Processor ............................................ 18
Selecting the Slot Number for the Module .............................................................. 19
Configuring the RSLinx Driver for the PC COM Port .............................................. 21
Downloading the Sample Program to the Processor .............................................. 23
Connecting your PC to the Module ......................................................................... 24
2 Configuring the MVI56-DNPSNET Module 25
2.1
2.1.1
2.1.2
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
2.2.7
2.2.8
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
Using ProSoft Configuration Builder ....................................................................... 26
Setting Up the Project ............................................................................................. 26
Renaming PCB Objects .......................................................................................... 28
[Backplane Configuration] ....................................................................................... 30
Module Name .......................................................................................................... 30
Read Register Start ................................................................................................. 30
Read Register Count ............................................................................................... 30
Write Register Start ................................................................................................. 30
Write Register Count ............................................................................................... 30
Failure Flag Count ................................................................................................... 30
Error Offset .............................................................................................................. 31
Initializing Output Data ............................................................................................ 31
[DNP ENET Slave] .................................................................................................. 32
Internal Slave ID ...................................................................................................... 32
Use IP List ............................................................................................................... 32
Use Trip/Close Single Point .................................................................................... 33
Binary Inputs ........................................................................................................... 34
Analog Inputs .......................................................................................................... 34
Float Inputs .............................................................................................................. 34
Counters .................................................................................................................. 35
ProSoft Technology, Inc. Page 5 of 139
February 11, 2011
Contents MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
2.3.8
2.4
2.5
2.6
2.7
2.8
2.9
2.3.9
2.3.10
2.3.11
2.3.12
2.3.13
2.3.14
2.3.15
2.3.16
2.3.17
2.3.18
2.3.19
2.3.20
2.3.21
2.3.22
2.3.23
2.3.24
2.3.25
2.3.26
2.3.27
2.3.28
2.3.29
2.3.30
2.3.31
2.3.32
2.4.1
2.4.2
2.5.1
2.5.2
2.5.3
2.6.1
2.6.2
2.6.3
Binary Outputs ........................................................................................................ 35
Analog Outputs ....................................................................................................... 35
Float Outputs .......................................................................................................... 35
BI Class ................................................................................................................... 35
AI Class ................................................................................................................... 35
Float Class .............................................................................................................. 35
AI Deadband ........................................................................................................... 36
Float Deadband ...................................................................................................... 36
Select/Operate Arm Time ....................................................................................... 36
Write Time Interval .................................................................................................. 36
App Layer Confirm Tout .......................................................................................... 36
Unsolicited Response ............................................................................................. 36
Class 1 Unsol Resp Min ......................................................................................... 37
Class 2 Unsol Resp Min ......................................................................................... 37
Class 3 Unsol Resp Min ......................................................................................... 37
Unsol Resp Delay ................................................................................................... 37
Uresp Master Address ............................................................................................ 37
AI Events with Time ................................................................................................ 37
AI with Flag ............................................................................................................. 37
BI with Flag ............................................................................................................. 38
BI Events Without Time .......................................................................................... 38
BO Without Flag...................................................................................................... 38
Counter with Flag .................................................................................................... 38
Frozen Counter with Flag ....................................................................................... 38
Time Sync Before Events ....................................................................................... 39
[DNP Slave Binary Inputs] ...................................................................................... 40
Point # ..................................................................................................................... 40
Class ....................................................................................................................... 40
[DNP Slave Analog Inputs] ..................................................................................... 41
Point # ..................................................................................................................... 41
Class ....................................................................................................................... 41
Deadband ............................................................................................................... 41
[DNP Slave Float Inputs] ........................................................................................ 42
Point # ..................................................................................................................... 42
Class ....................................................................................................................... 42
Deadband ............................................................................................................... 42
[DNP ENET IP ADDRESSES] ................................................................................ 43
Ethernet Configuration ............................................................................................ 44
Downloading the Project to the Module Using a Serial COM Port ......................... 45
3 Ladder Logic 47
3.1
3.2
3.1.1
3.1.2
Module Data Objects .............................................................................................. 48
DNPModuleDef Object ........................................................................................... 48
Special Objects ....................................................................................................... 51
Adding the Module to an Existing Project ............................................................... 53
4 Diagnostics and Troubleshooting 57
4.1
4.1.1
4.1.2
4.1.3
LED Status Indicators ............................................................................................. 58
Ethernet LED Indicators .......................................................................................... 59
Clearing a Fault Condition ...................................................................................... 59
Troubleshooting ...................................................................................................... 59
Page 6 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Contents
DNP 3.0 Server over Ethernet Communication Module User Manual
4.1.4
4.2
4.3
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
Error Status Table ................................................................................................... 60
Using ProSoft Configuration Builder (PCB) for Diagnostics.................................... 62
Using the Diagnostic Window in ProSoft Configuration Builder .............................. 62
Navigation ............................................................................................................... 64
Main Menu ............................................................................................................... 65
DNP Menu ............................................................................................................... 67
Database View Menu .............................................................................................. 69
Network Menu ......................................................................................................... 71
Reading Status Data from the Module .................................................................... 73
5 Reference 75
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.1.1
5.1.2
5.1.3
5.2.1
5.3.1
5.3.2
5.3.3
5.3.4
5.3.5
5.4.1
5.4.2
5.4.3
5.7.1
5.7.2
Product Specifications ............................................................................................. 76
General Specifications ............................................................................................ 76
Hardware Specifications.......................................................................................... 77
Functional Specifications......................................................................................... 78
Functional Overview ................................................................................................ 79
General Concepts ................................................................................................... 79
MVI56-DNPSNET Application Design ..................................................................... 93
Designing the system .............................................................................................. 93
Communication Parameters .................................................................................. 105
Functionality .......................................................................................................... 105
Data Transfer at Startup ........................................................................................ 105
Module Operation .................................................................................................. 106
Cable Connections ................................................................................................ 107
Ethernet Connection .............................................................................................. 107
RS-232 Configuration/Debug Port ........................................................................ 108
DB9 to RJ45 Adaptor (Cable 14) .......................................................................... 111
Configuration Data ................................................................................................ 112
MVI56-DNPSNET Status Data .............................................................................. 116
Internal Indication Bits (IIN Bits) for DNP Server .................................................. 119
First Byte ............................................................................................................... 119
Second Byte .......................................................................................................... 119
DNP Subset Definition ........................................................................................... 120
Device Profile ........................................................................................................ 126
Event Size Computation ........................................................................................ 128
6 Support, Service & Warranty 129
Contacting Technical Support ......................................................................................................... 129
6.1
6.1.1
6.1.2
6.1.3
6.2
6.2.1
6.2.2
6.2.3
6.2.4
6.2.5
6.2.6
6.2.7
6.2.8
Return Material Authorization (RMA) Policies and Conditions.............................. 131
Returning Any Product .......................................................................................... 131
Returning Units Under Warranty ........................................................................... 132
Returning Units Out of Warranty ........................................................................... 132
LIMITED WARRANTY ........................................................................................... 133
What Is Covered By This Warranty ....................................................................... 133
What Is Not Covered By This Warranty ................................................................ 134
Disclaimer Regarding High Risk Activities ............................................................ 134
Intellectual Property Indemnity .............................................................................. 135
Disclaimer of all Other Warranties ........................................................................ 135
Limitation of Remedies ** ...................................................................................... 136
Time Limit for Bringing Suit ................................................................................... 136
No Other Warranties ............................................................................................. 136
ProSoft Technology, Inc. Page 7 of 139
February 11, 2011
Contents MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
6.2.9
6.2.10
Allocation of Risks ................................................................................................ 136
Controlling Law and Severability .......................................................................... 136
Index 137
Page 8 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Guide to the MVI56-DNPSNET User Manual
DNP 3.0 Server over Ethernet Communication Module User Manual
Guide to the MVI56-DNPSNET User Manual
Function
Introduction
(Must Do)
Diagnostic and
Troubleshooting
Reference
Product Specifications
Support, Service, and
Warranty
Index
Section to Read Details
Start Here (page 11) This section introduces the customer to the
→
Diagnostics and
→
Troubleshooting
(page 57)
Reference (page 75)
→
Product
Specifications (page
76)
Support, Service
→
and Warranty (page
129)
Index
module. Included are: package contents,
system requirements, hardware installation, and
basic configuration.
This section describes Diagnostic and
Troubleshooting procedures.
These sections contain general references
associated with this product and its
Specifications..
This section contains Support, Service and
Warranty information.
Index of chapters.
ProSoft Technology, Inc. Page 9 of 139
February 11, 2011
Guide to the MVI56-DNPSNET User Manual MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Page 10 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Start Here
DNP 3.0 Server over Ethernet Communication Module User Manual
1 Start Here
In This Chapter
System Requirements ........................................................................... 12
Package Contents ................................................................................. 13
Installing ProSoft Configuration Builder Software .................................. 14
Setting Jumpers .................................................................................... 15
Installing the Module in the Rack ........................................................... 16
Connecting Your PC to the ControlLogix Processor .............................. 17
Opening the Sample Ladder Logic ........................................................ 18
Downloading the Sample Program to the Processor ............................. 23
Connecting your PC to the Module ........................................................ 24
To get the most benefit from this User Manual, you should have the following
skills:
Rockwell Automation® RSLogix™ software: launch the program, configure
ladder logic, and transfer the ladder logic to the processor
Microsoft Windows: install and launch programs, execute menu commands,
navigate dialog boxes, and enter data
Hardware installation and wiring: install the module, and safely connect
Distributed Network Protocol and ControlLogix devices to a power source and
to the MVI56-DNPSNET module’s application port(s)
ProSoft Technology, Inc. Page 11 of 139
February 11, 2011
Start Here MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
1.1 System Requirements
The MVI56-DNPSNET module requires the following minimum hardware and
software components:
Rockwell Automation ControlLogix™ processor, with compatible power
supply and one free slot in the rack, for the MVI56-DNPSNET module. The
module requires 800 mA of available power.
Rockwell Automation RSLogix 5000 programming software version 2.51 or
higher
Rockwell Automation RSLinx communication software
Pentium® II 450 MHz minimum. Pentium III 733 MHz (or better)
recommended
Supported operating systems:
o
Microsoft Windows XP Professional with Service Pack 1 or 2
o
Microsoft Windows 2000 Professional with Service Pack 1, 2, or 3
o
Microsoft Windows Server 2003
128 Mbytes of RAM minimum, 256 Mbytes of RAM recommended
100 Mbytes of free hard disk space (or more based on application
requirements)
256-color VGA graphics adapter, 800 x 600 minimum resolution (True Color
1024 × 768 recommended)
CD-ROM drive
ProSoft Configuration Builder, HyperTerminal or other terminal emulator
program.
Note: You can install the module in a local or remote rack. For remote rack installation, the module
requires EtherNet/IP or ControlNet communication with the processor.
Page 12 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Start Here
DNP 3.0 Server over Ethernet Communication Module User Manual
1.2 Package Contents
The following components are included with your MVI56-DNPSNET module, and
are all required for installation and configuration.
Important: Before beginning the installation, please verify that all of the following items are
present.
Qty. Part Name Part Number Part Description
1 MVI56-DNPSNET
Module
1 Cable Cable #15 - RS232
1 Cable Cable #14 - RJ45
1 inRAx Solutions CD Contains sample programs, utilities and
If any of these components are missing, please contact ProSoft Technology
Support for replacement parts.
MVI56-DNPSNET DNP 3.0 Server over Ethernet
Communication Module
For RS232 between a Personal Computer
Null Modem
to DB9 Male
Adapter
(PC) and the CFG port of the module
For connecting the module’s port to Cable
#15 for RS-232 connections
documentation for the MVI56-DNPSNET
module.
ProSoft Technology, Inc. Page 13 of 139
February 11, 2011
Start Here MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
1.3 Installing ProSoft Configuration Builder Software
You must install the ProSoft Configuration Builder (PCB) software to configure
the module. You can always get the newest version of ProSoft Configuration
Builder from the ProSoft Technology website.
To install ProSoft Configuration Builder from the ProSoft Technology website
1 Open your web browser and navigate to http://www.prosoft-
technology.com/pcb
2 Click the D
Configuration Builder.
3 Choose S
4 Save the file to your Windows Desktop, so that you can find it easily when
you have finished downloading.
5 When the download is complete, locate and open the file, and then follow the
instructions on your screen to install the program.
If you do not have access to the Internet, you can install ProSoft Configuration
Builder from the ProSoft Solutions Product CD-ROM, included in the package
with your module.
To install ProSoft Configuration Builder from the Product CD-ROM
1 Insert the ProSoft Solutions Product CD-ROM into the CD-ROM drive of your
PC. Wait for the startup screen to appear.
2 On the startup screen, click P
Windows Explorer file tree window.
3 Click to open the U
and files you will need to set up and configure your module.
4 Double-click the S
PCB_*.
software on your PC. The information represented by the "*" character in the
file name is the PCB version number and, therefore, subject to change as
new versions of PCB are released.
OWNLOAD HERE
AVE
or S
AVE FILE
TILITIES
ETUP CONFIGURATION TOOL
EXE
file and follow the instructions on your screen to install the
link to download the latest version of ProSoft
when prompted.
RODUCT DOCUMENTATION
folder. This folder contains all of the applications
folder, double-click the
. This action opens a
Note: Many of the configuration and maintenance procedures use files and other utilities on the
CD-ROM. You may wish to copy the files from the Utilities folder on the CD-ROM to a convenient
location on your hard drive.
Page 14 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Start Here
DNP 3.0 Server over Ethernet Communication Module User Manual
1.4 Setting Jumpers
The Setup Jumper acts as "write protection" for the module’s flash memory. In
"write protected" mode, the Setup pins are not connected, and the module’s
firmware cannot be overwritten. Do not jumper the Setup pins together unless
you are directed to do so by ProSoft Technical Support.
The following illustration shows the MVI56-DNPSNET jumper configuration.
Note: If you are installing the module in a remote rack, you may prefer to leave the Setup pins
jumpered. That way, you can update the module’s firmware without requiring physical access to
the module.
ProSoft Technology, Inc. Page 15 of 139
February 11, 2011
Start Here MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
1.5 Installing the Module in the Rack
If you have not already installed and configured your ControlLogix processor and
power supply, please do so before installing the MVI56-DNPSNET module. Refer
to your Rockwell Automation product documentation for installation instructions.
Warning: You must follow all safety instructions when installing this or any other electronic
devices. Failure to follow safety procedures could result in damage to hardware or data, or even
serious injury or death to personnel. Refer to the documentation for each device you plan to
connect to verify that suitable safety procedures are in place before installing or servicing the
device.
After you have checked the placement of the jumpers, insert MVI56-DNPSNET
into the ControlLogix chassis. Use the same technique recommended by
Rockwell Automation to remove and install ControlLogix modules.
Warning: When you insert or remove the module while backplane power is on, an electrical arc
can occur. This could cause an explosion in hazardous location installations. Verify that power is
removed or the area is non-hazardous before proceeding. Repeated electrical arcing causes
excessive wear to contacts on both the module and its mating connector. Worn contacts may
create electrical resistance that can affect module operation.
1 Turn power OFF.
2 Align the module with the top and bottom guides, and slide it into the rack
until the module is firmly against the backplane connector.
3 With a firm but steady push, snap the module into place.
4 Check that the holding clips on the top and bottom of the module are securely
in the locking holes of the rack.
5 Make a note of the slot location. You must identify the slot in which the
module is installed in order for the sample program to work correctly. Slot
numbers are identified on the green circuit board (backplane) of the
ControlLogix rack.
6 Turn power ON.
Note: If you insert the module improperly, the system may stop working, or may behave
unpredictably.
Page 16 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Start Here
DNP 3.0 Server over Ethernet Communication Module User Manual
1.6 Connecting Your PC to the ControlLogix Processor
There are several ways to establish communication between your PC and the
ControlLogix processor. The following steps show how to establish
communication through the serial interface. It is not mandatory that you use the
processor's serial interface. You may access the processor through whatever
network interface is available on your system. Refer to your Rockwell Automation
documentation for information on other connection methods.
1 Connect the right-angle connector end of the cable to your controller at the
communications port.
2 Connect the straight connector end of the cable to the serial port on your
computer.
ProSoft Technology, Inc. Page 17 of 139
February 11, 2011
Start Here MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
1.7 Opening the Sample Ladder Logic
The sample program for your MVI56-DNPSNET module includes custom tags,
data types and ladder logic for data I/O and status monitoring. For most
applications, you can run the sample ladder program without modification, or, for
advanced applications, you can incorporate the sample program into your
existing application.
The inRAx Solutions CD provides one or more versions of the sample ladder
logic. The version number appended to the file name corresponds with the
firmware version number of your ControlLogix processor. The firmware version
and sample program version must match.
1.7.1 Determining the Firmware Version of Your Processor
Important: The RSLinx service must be installed and running on your computer in order for
RSLogix to communicate with the processor. Refer to your RSLinx and RSLogix documentation for
help configuring and troubleshooting these applications.
1 Connect an RS-232 serial cable from the COM (serial) port on your PC to the
communication port on the front of the processor.
2 Start RSLogix 5000 and close any existing project that may be loaded.
3 Open the C
establish communication with the processor. This may take a few moments.
4 When RSLogix has established communication with the processor, the
Connected To Go Online dialog box will open.
OMMUNICATIONS
menu and choose GO O
NLINE
. RSLogix will
Page 18 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Start Here
DNP 3.0 Server over Ethernet Communication Module User Manual
5 In the Connected To Go Online dialog box, click the G
ENERAL
tab. This tab
shows information about the processor, including the Revision (firmware)
version. In the following illustration, the firmware version is 17.2.
1.7.2 Selecting the Slot Number for the Module
This sample application is for a module installed in Slot 1 in a ControlLogix rack.
The ladder logic uses the slot number to identify the module. If you are installing
the module in a different slot, you must update the ladder logic so that program
tags and variables are correct, and do not conflict with other modules in the rack.
ProSoft Technology, Inc. Page 19 of 139
February 11, 2011
Start Here MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
To change the slot number
1 In the Controller Organization list, select the module and then click the right
mouse button to open a shortcut menu.
2 On the shortcut menu, choose P
ROPERTIES
. This action opens the Module
Properties dialog box.
3 In the Slot field, use the spinners on the right side of the field to select the slot
number where the module will reside in the rack, and then click OK.
RSLogix will automatically apply the slot number change to all tags, variables
and ladder logic rungs that use the MVI56-DNPSNET slot number for
computation.
Page 20 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Start Here
DNP 3.0 Server over Ethernet Communication Module User Manual
1.7.3 Configuring the RSLinx Driver for the PC COM Port
If RSLogix is unable to establish communication with the processor, follow these
steps.
1 Open RSLinx.
2 Open the C
This action opens the Configure Drivers dialog box.
OMMUNICATIONS
menu, and choose C
ONFIGURE DRIVERS
.
Note: If the list of configured drivers is blank, you must first choose and configure a driver from the
Available Driver Types list. The recommended driver type to choose for serial communication with
the processor is RS-232 DF1 Devices.
ProSoft Technology, Inc. Page 21 of 139
February 11, 2011
Start Here MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
3 Click to select the driver, and then click C
ONFIGURE
. This action opens the
Configure RS-232 DF1 Devices dialog box.
4 Click the A
UTO-CONFIGURE
button. RSLinx will attempt to configure your
serial port to work with the selected driver.
5 When you see the message Auto Configuration Successful, click the OK
button to dismiss the dialog box.
Note: If the auto-configuration procedure fails, verify that the cables are connected correctly
between the processor and the serial port on your computer, and then try again. If you are still
unable to auto-configure the port, refer to your RSLinx documentation for further troubleshooting
steps.
Page 22 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Start Here
DNP 3.0 Server over Ethernet Communication Module User Manual
1.8 Downloading the Sample Program to the Processor
Note: The key switch on the front of the ControlLogix processor must be in the REM or PROG
position.
1 If you are not already online with the processor, open the Communications
menu, and then choose D
communication with the processor. You do not have to download through the
processor's serial port, as shown here. You may download through any
available network connection.
2 When communication is established, RSLogix 5000 will open a confirmation
dialog box. Click the D
processor.
OWNLOAD.
OWNLOAD
RSLogix 5000 will establish
button to transfer the sample program to the
3 RSLogix 5000 will compile the program and transfer it to the processor. This
process may take a few minutes.
4 When the download is complete, RSLogix 5000 will open another
confirmation dialog box. If the key switch is in the REM position, click OK to
switch the processor from PROGRAM mode to RUN mode.
Note: If you receive an error message during these steps, refer to your RSLogix documentation to
interpret and correct the error.
ProSoft Technology, Inc. Page 23 of 139
February 11, 2011
Start Here MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
1.9 Connecting your PC to the Module
With the module securely mounted, connect your PC to the Configuration/Debug
port using an RJ45-DB-9 Serial Adapter Cable and a Null Modem Cable.
1 Attach both cables as shown.
2 Insert the RJ45 cable connector into the Configuration/Debug port of the
module.
3 Attach the other end to the serial port on your PC.
Page 24 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Configuring the MVI56-DNPSNET Module
DNP 3.0 Server over Ethernet Communication Module User Manual
2 Configuring the MVI56-DNPSNET Module
In This Chapter
Using ProSoft Configuration Builder ...................................................... 26
[Backplane Configuration] ..................................................................... 30
[DNP ENET Slave] ................................................................................ 32
[DNP Slave Binary Inputs] ..................................................................... 40
[DNP Slave Analog Inputs] .................................................................... 41
[DNP Slave Float Inputs] ....................................................................... 42
[DNP ENET IP ADDRESSES] ............................................................... 43
Ethernet Configuration .......................................................................... 44
Downloading the Project to the Module Using a Serial COM Port ......... 45
ProSoft Technology, Inc. Page 25 of 139
February 11, 2011
Configuring the MVI56-DNPSNET Module MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
2.1 Using ProSoft Configuration Builder
ProSoft Configuration Builder (PCB) provides a quick and easy way to manage
module configuration files customized to meet your application needs. PCB is not
only a powerful solution for new configuration files, but also allows you to import
information from previously installed (known working) configurations to new
projects.
2.1.1 Setting Up the Project
To begin, start PROS
OFT CONFIGURATION BUILDER
(PCB).
If you have used other Windows configuration tools before, you will find the
screen layout familiar. PCB’s window consists of a tree view on the left, and an
information pane and a configuration pane on the right side of the window. When
you first start PCB, the tree view consists of folders for Default Project and
Default Location, with a Default Module in the Default Location folder. The
following illustration shows the PCB window with a new project.
Page 26 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Configuring the MVI56-DNPSNET Module
DNP 3.0 Server over Ethernet Communication Module User Manual
Adding the MVI56-DNPSNET module to the project
1 Use the mouse to select D
EFAULT MODULE
in the tree view, and then click the
right mouse button to open a shortcut menu.
2 On the shortcut menu, choose C
HOOSE MODULE TYPE
. This action opens the
Choose Module Type dialog box.
3 In the Product Line Filter area of the dialog box, select MVI56. In the Select
Module Type dropdown list, select MVI56-DNPSNET, and then click OK to
save your settings and return to the ProSoft Configuration Builder window.
ProSoft Technology, Inc. Page 27 of 139
February 11, 2011
Configuring the MVI56-DNPSNET Module MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
2.1.2 Renaming PCB Objects
Notice that the contents of the information pane and the configuration pane
changed when you added the module to the project.
At this time, you may wish to rename the Default Project and Default Location
folders in the tree view.
1 Select the object, and then click the right mouse button to open a shortcut
menu. From the shortcut menu, choose R
ENAME
.
2 Type the name to assign to the object.
3 Click away from the object to save the new name.
Configuring Module Parameters
1 Click the [+] sign next to the module icon to expand module information.
2 Click the [+] sign next to any icon to view module information and
configuration options.
3 Double-click any icon to open an Edit dialog box.
4 To edit a parameter, select the parameter in the left pane and make your
changes in the right pane.
5 Click OK to save your changes.
Page 28 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Configuring the MVI56-DNPSNET Module
DNP 3.0 Server over Ethernet Communication Module User Manual
Creating Optional Comment Entries
1 Click the [+] to the left of the icon to expand the module
comments.
2 Double-click the icon. The Edit - Module Comment dialog box
appears.
3 Enter your comment and click OK to save your changes.
Printing a Configuration File
1 Select the module icon, and then click the right mouse button to open a
shortcut menu.
2 On the shortcut menu, choose V
IEW CONFIGURATION
. This action opens the
View Configuration window.
3 In the View Configuration window, open the F
ILE
menu, and choose P
RINT.
This action opens the Print dialog box.
4 In the Print dialog box, choose the printer to use from the drop-down list,
select printing options, and then click OK.
ProSoft Technology, Inc. Page 29 of 139
February 11, 2011
Configuring the MVI56-DNPSNET Module MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
2.2 [Backplane Configuration]
This section of the file describes the database setup and module level
parameters.
2.2.1 Module Name
0 to 80 characters
This parameter assigns a name to the module that can be viewed using the
configuration/debug port. Use this parameter to identify the module and the
configuration file.
2.2.2 Read Register Start
0 to 8899
This parameter specifies the starting register in the module where data will be
transferred from the module to the processor. Valid range for this parameter is 0
to 8899.
2.2.3 Read Register Count
0 to 9000
This parameter specifies the number of registers to be transferred from the
module to the processor. Valid entry for this parameter is 0 to 9000.
2.2.4 Write Register Start
0 to 8899
This parameter specifies the starting register in the module where the data will be
transferred from the processor to the module. Valid range for this parameter is 0
to 8899.
2.2.5 Write Register Count
0 to 9000
This parameter specifies the number of registers to transfer from the processor to
the module. Valid entry for this parameter is 0 to 9000.
2.2.6 Failure Flag Count
0 through 65535
This parameter specifies the number of successive transfer errors that must
occur before halting communication on the application port(s). If the parameter is
set to 0, the application port(s) will continue to operate under all conditions. If the
value is set larger than 0 (1 to 65535), communications will cease if the specified
number of failures occur.
Page 30 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Configuring the MVI56-DNPSNET Module
DNP 3.0 Server over Ethernet Communication Module User Manual
2.2.7 Error Offset
0 to 8964
This parameter specifies the register location in the module’s database where
module status data will be stored. If a value less than 0 is entered, the data will
not be stored in the database. If the value specified is in the range of 0 to 8964,
the data will be placed in the modules database.
2.2.8 Initializing Output Data
YES or NO
This parameter determines if the output data for the module should be initialized
with values from the processor. If the value is set to NO (0), the output data will
be initialized to 0. If the value is set to YES (1), the data will be initialized with
data from the processor. Use of this option requires associated ladder logic to
pass the data from the processor to the module.
ProSoft Technology, Inc. Page 31 of 139
February 11, 2011
Configuring the MVI56-DNPSNET Module MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
2.3 [DNP ENET Slave]
This section provides information required to configure a slave application with
the module. Most entries contained within this section are self explanatory with
the possible exception of the Use IP List directive. This directive instructs the
module to verify the address of the received message and ignore the message if
it is not on our list of acceptable clients.
2.3.1 Internal Slave ID
0 to 65534
This is the DNP address for the module. All messages with this address received
from the master will be processed by the module.
2.3.2 Use IP List
YES or NO
This parameter specifies if the IP address of the host connected to the system
will be validated. If the parameter is set to NO, any host may connect to the unit.
If the parameter is set to YES, only hosts in the IP list will be permitted to connect
to the module. All other IP addresses will be ignored by the module and the
module will issue a RST to the TCP/IP connection.
DNP Database Definition Note: The databases are in the memory of the module in this sequence
and are placed directly adjacent to each other. In other words when you change the size of a
database you must adjust the transfer commands to accommodate the new location.
Page 32 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Configuring the MVI56-DNPSNET Module
DNP 3.0 Server over Ethernet Communication Module User Manual
2.3.3 Use Trip/Close Single Point
Yes or No
If you set this parameter to Yes, Trip/Close events will function like Pulse On
operations. Only one bit will be reserved in the DNP BO database.
If you set this parameter to No, the dual-point relay control database (Trip/Close)
is overlaid on the DNP Binary Output database of the module. Each DNP point
index sent will have an offset of point index times 2 into the database. The first bit
of the dual-point relay control database will correspond to the close relay and the
second will correspond to the trip relay.
The bit definitions from control byte of CROB are as follows:
00 - Null (single bit control or select of Trip/Close
01 - Close relay
10 - Trip relay
11 - Invalid
If the operate command is used with the Null relay (00), the module will operate
on the point as single point control. The following table describes the module’s
behavior:
Point Index in Command Point in Database Controlled
0 Bit 0 in BO database
10 Bit 10 in BO database
15 Bit 15 in BO database
If the operate command is used with the close relay selected, the module will
operate on the first bit of the two database bits associated with the point. The
following table describes the module’s behavior when the close relay is selected:
Point Index in Command Point in Database Controlled
0 Bit 0 in BO database
1 Bit 2 in BO database
10 Bit 20 in BO database
15 Bit 30 in BO database
ProSoft Technology, Inc. Page 33 of 139
February 11, 2011
Configuring the MVI56-DNPSNET Module MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
If the operate command is used with the trip relay selected, the module will
operate on the second bit of the two database bits associated with the point. The
following table describes the module’s behavior when the trip relay is selected:
Point Index in Command Point in Database Controlled
0 Bit 1 in BO database
1 Bit 3 in BO database
10 Bit 21 in BO database
15 Bit 31 in BO database
It is important to note that the trip and close relays are linked in the module. If a
latch-on command is sent to the close relay its bit will be set and the associated
trip relay bit will be cleared.
Because the single-point and dual-point control database share the same
memory area, caution should be exercised to prevent control of one area by
another. This can be accomplished by careful design of the system. The dualpoint database could be isolated from the single-point database. For example,
DNP point index 0 to 9 could be used for the dual-point database and correspond
to bits 0 to 19. The single-point control points would then start at DNP point index
20 which corresponds to bit 20 of the database.
Using this technique, the MVI56-DNPSNET module will not require any
configuration for the new dual-point control, and the module will be backward
compatible for current customer applications.
2.3.4 Binary Inputs
0 to 500 words
This parameter specifies the number of digital input points to configure in the
DNP slave device based on a word count. The valid range is 0 to 500 words.
2.3.5 Analog Inputs
0 to 500 points
This parameter sets the number of analog input points to configure in the DNP
slave device. Each point will occupy a one-word area in the module memory.
2.3.6 Float Inputs
0 to 150
Number of floating-point input points to configure in the DNP slave device. Each
point will occupy a two-word area in the module memory.
Page 34 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Configuring the MVI56-DNPSNET Module
DNP 3.0 Server over Ethernet Communication Module User Manual
2.3.7 Counters
0 to 250 points
This parameter sets the number of counter points to configure in the DNP slave
device. Each point will occupy a two-word area in the module memory. This
number corresponds to the number of frozen counters. The application maps the
counters to the frozen counters directly. Valid values are 0 to 250 points.
2.3.8 Binary Outputs
0 to 500 words
Number of digital output points to configure in the DNP slave device based on a
word count. Each word stores 16 points. Therefore, if the parameter is set to 2,
32 binary outputs will be defined for the application.
2.3.9 Analog Outputs
0 to 500 points
Number of analog output points to configure in the DNP slave device. Each point
will occupy a one word area in the module memory.
2.3.10 Float Outputs
0 to 150 points
Number of floating-point output points to configure in the DNP slave device. Each
point will occupy a two- word area in the module memory.
2.3.11 BI Class
0=disable, else 1 to 3
This parameter specifies the default class to be utilized for all the binary input
points in the DNP database that are not defined in the override list section.
2.3.12 AI Class
0=disable, else 1 to 3
This parameter specifies the default class to be utilized for all the analog input
points in the DNP database that are not defined in the override list section.
2.3.13 Float Class
0=disable, else 1 to 3
This parameter specifies the default class to be utilized for all the floating-point
input points in the DNP database that are not defined in the override list section.
ProSoft Technology, Inc. Page 35 of 139
February 11, 2011
Configuring the MVI56-DNPSNET Module MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
2.3.14 AI Deadband
0 to 32767 data units
This value sets the global deadband for all analog input points. When the current
value for an analog input point is not within the deadband limit set based on the
last event for the point, an event will be generated.
2.3.15 Float Deadband
0 to 10000 data units
This parameter specifies the default single float deadband value assigned to all
points not defined in the override list for the floating-point input point type in the
DNP database.
2.3.16 Select/Operate Arm Time
1 to 65535 milliseconds
This parameter sets the time period after select command received in which
operate command will be performed. After the select command is received, the
operate command will only be honored if it arrives within this period of time. Valid
arm timeout values are 1 to 65535 milliseconds. This example shows the value
set to 2000 milliseconds.
2.3.17 Write Time Interval
0 to 1440 minutes
This parameter sets the time interval to set the need time IIN bit (0=never), which
will cause the master to write the time. Stored in milliseconds in the module
memory.
2.3.18 App Layer Confirm Tout
1 to 65535 milliseconds
Event data contained in the last response may be sent again if not confirmed
within the millisecond time period set. If application layer confirms are used with
data link confirms, ensure that the application layer confirm timeout is set long
enough.
2.3.19 Unsolicited Response
YES or NO
This parameter is set if the slave unit will send unsolicited response messages. If
set to No, the slave will not send unsolicited responses. If set to Yes, the slave
will send unsolicited responses.
Page 36 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Configuring the MVI56-DNPSNET Module
DNP 3.0 Server over Ethernet Communication Module User Manual
2.3.20 Class 1 Unsol Resp Min
1 to 255 events
Minimum number of events in Class 1 required before an unsolicited response
will be generated.
2.3.21 Class 2 Unsol Resp Min
1 to 255 events
Minimum number of events in Class 2 required before an unsolicited response
will be generated.
2.3.22 Class 3 Unsol Resp Min
1 to 255 events
Minimum number of events in Class 3 required before an unsolicited response
will be generated.
2.3.23 Unsol Resp Delay
0 to 65535 milliseconds
Maximum number of 1 millisecond intervals to wait after an event occurs before
sending an unsolicited response message. If set to 0, only use minimum number
of events.
2.3.24 Uresp Master Address
0 to 65535
DNP destination address where unsolicited response messages are sent.
2.3.25 AI Events with Time
YES or NO
This parameter determines if the analog input events generated by the module
will include the date and time of the event. If the parameter is set to NO, the
default is set to no time data. If the parameter is set to YES, the default object will
include the time of the event.
2.3.26 AI with Flag
YES or NO
This parameter determines which variation will be returned for object 30 when
the master requests variation 0. If the parameter is set to NO, variation 4 will be
returned. If the parameter is set to YES, variation 2 will be returned.
Note: Flag will always be set for Online and cannot be changed through by the PLC or user
program. Only the default variation returned by the module will be affected by changing this
parameter.
ProSoft Technology, Inc. Page 37 of 139
February 11, 2011
Configuring the MVI56-DNPSNET Module MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
2.3.27 BI with Flag
YES or NO
This parameter determines which variation will be returned for object 1 when the
master requests variation 0. If the parameter is set to NO, variation 1 will be
returned. If the parameter is set to YES, variation 2 will be returned.
Note: Flag will always be set for Online and cannot be changed through by the PLC or user
program. Only the default variation returned by the module will be affected by changing this
parameter.
2.3.28 BI Events Without Time
YES or NO
This parameter determines if the binary input events generated by the module
will include the date and time of the event. If the parameter is set to YES, the
default is set to no time data. If the parameter is set to NO, the default object will
include the time of the event.
2.3.29 BO Without Flag
YES or NO
This parameter determines which variation will be returned for object 10 when
the master requests variation 0. If the parameter is set to NO, variation 2 will be
returned. If the parameter is set to YES, variation 1 will be returned.
2.3.30 Counter with Flag
YES or NO
This parameter determines which variation will be returned for object 20 when
the master requests variation 0. If the parameter is set to NO, variation 5 will be
returned. If the parameter is set to YES, variation 1 will be returned.
Note: Flag will always be set for Online and cannot be changed through by the PLC or user
program. Only the default variation returned by the module will be affected by changing this
parameter.
2.3.31 Frozen Counter with Flag
YES or NO
This parameter determines which variation will be returned for object 21 when
the master requests variation 0. If the parameter is set to NO, variation 9 will be
returned. If the parameter is set to YES, variation 1 will be returned.
Note: Flag will always be set for Online and cannot be changed through by the PLC or user
program. Only the default variation returned by the module will be affected by changing this
parameter.
Page 38 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Configuring the MVI56-DNPSNET Module
DNP 3.0 Server over Ethernet Communication Module User Manual
2.3.32 Time Sync Before Events
YES or NO
This parameter determines if events are to be generated by the module before
the time synchronization from the master unit. If the parameter is set to NO,
events will be generated irrespective of the module’s time sync status. If the
parameter is set to YES, events will be generated only if the module’s time is
synchronized.
ProSoft Technology, Inc. Page 39 of 139
February 11, 2011
Configuring the MVI56-DNPSNET Module MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
2.4 [DNP Slave Binary Inputs]
This section of the configuration file overrides the Class 2 binary database points.
2.4.1 Point #
This is the information object address of the point.
2.4.2 Class
C
LASS 1
C
LASS 2
C
LASS 3
0 - Disable.
- Highest priority
- Middle priority
- Lowest priority
Page 40 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Configuring the MVI56-DNPSNET Module
DNP 3.0 Server over Ethernet Communication Module User Manual
2.5 [DNP Slave Analog Inputs]
This area is to override the class (3) and deadband for the integer analog input
database. The point # is the offset from the start of the analog input database.
2.5.1 Point #
This is the information object address of the point.
2.5.2 Class
C
LASS 1
C
LASS 2
C
LASS 3
0 - Disable.
- Highest priority
- Middle priority
- Lowest priority
2.5.3 Deadband
The module will generate events only if the data value changes by an amount
greater than or equal to the configured deadband value.
ProSoft Technology, Inc. Page 41 of 139
February 11, 2011
Configuring the MVI56-DNPSNET Module MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
2.6 [DNP Slave Float Inputs]
This area is to override the class (3) and deadband for the single float database.
The point # is not the address in the analog database, but is the offset from the
start of the single floating-point database.
2.6.1 Point #
This is the information object address of the point.
2.6.2 Class
C
LASS 1
C
LASS 2
C
LASS 3
0 - Disable.
- Highest priority
- Middle priority
- Lowest priority
2.6.3 Deadband
The module will generate events only if the data value changes by an amount
greater than or equal to the configured deadband value.
Page 42 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Configuring the MVI56-DNPSNET Module
DNP 3.0 Server over Ethernet Communication Module User Manual
2.7 [DNP ENET IP ADDRESSES]
This section of the configuration file only applies if the directive labeled Use IP
List is set to Yes or Y. If Use IP List is enabled, the module will refuse to answer
a request unless the IP address of the client is listed in this section. This section
may contain no more than 10 addresses.
ProSoft Technology, Inc. Page 43 of 139
February 11, 2011
Configuring the MVI56-DNPSNET Module MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
2.8 Ethernet Configuration
Use this procedure to configure the Ethernet settings for your module. You must
assign an IP address, subnet mask and gateway address. After you complete
this step, you can connect to the module with an Ethernet cable.
1 Determine the network settings for your module, with the help of your network
administrator if necessary. You will need the following information:
o
IP address (fixed IP required) _____ . _____ . _____ . _____
o
Subnet mask _____ . _____ . _____ . _____
o
Gateway address _____ . _____ . _____ . _____
Note: The gateway address is optional, and is not required for networks that do not use a default
gateway.
2 Double-click the E
dialog box.
THERNET CONFIGURATION
icon. This action opens the Edit
3 Edit the values for my_ip, netmask (subnet mask) and gateway (default
gateway).
4 When you are finished editing, click OK to save your changes and return to
the ProSoft Configuration Builder window.
Page 44 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Configuring the MVI56-DNPSNET Module
DNP 3.0 Server over Ethernet Communication Module User Manual
2.9 Downloading the Project to the Module Using a Serial COM Port
For the module to use the settings you configured, you must download (copy) the
updated Project file from your PC to the module.
To download the project file
1 In the tree view in ProSoft Configuration Builder, click once to select the
module.
2 Right-click the module icon to open a shortcut menu. From the shortcut
menu, choose D
PC for a valid com port (this may take a few seconds). When PCB has found
a valid COM port, the Download dialog box will open.
OWNLOAD FROM PC TO DEVICE
. The program will scan your
3 Choose the COM port to use from the dropdown list, and then click the
D
OWNLOAD
button.
The module will perform a platform check to read and load its new settings.
When the platform check is complete, the status bar in the Download dialog
box will display the message Module Running.
ProSoft Technology, Inc. Page 45 of 139
February 11, 2011
Configuring the MVI56-DNPSNET Module MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Page 46 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Ladder Logic
DNP 3.0 Server over Ethernet Communication Module User Manual
3 Ladder Logic
In This Chapter
Module Data Objects ............................................................................. 48
Adding the Module to an Existing Project .............................................. 53
Ladder logic is required for application of the MVI56-DNPSNET module. Tasks
that must be handled by the ladder logic are module data transfer, special block
handling, and status data receipt. Additionally, a power-up handler may be
needed to handle the initialization of the module’s data and to clear any
processor fault conditions.
The sample ladder logic, on the ProSoft Solutions CD-ROM, is extensively
commented, to provide information on the purpose and function of each rung. For
most applications, the sample ladder will work without modification.
ProSoft Technology, Inc. Page 47 of 139
February 11, 2011
Ladder Logic MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
3.1 Module Data Objects
All data related to the MVI56-DNPSNET is stored in one user defined data type,
containing data transfer and status data, and the DNP datasets. Any time an
array’s size is altered in the RSLogix 5000 software, all the data in the object can
be set to zero. Because the array sizes may need to be adjusted for the data
types in an application, the user defined data should be adjusted prior to the
module being placed in service (if the default configuration does not contain
enough data points for the application).
An instance of each data type is required before the module can be used. This is
accomplished by declaring variables of the data types in the Controller Tags Edit
Tags dialog box. Each object is discussed in the following topics.
3.1.1 DNPModuleDef Object
The DNPModuleDef object contains all the MVI56-DNPSNET module status data
and data transfer variables. The following table describes the structure of this
object.
Name Data Type Description
Status DNPSlvStat
Data DNPData
CMDcontrolbits DNPCMDBits
ReadClock DNPClock
WriteClock DNPClock
BI_Events DNPBIEvntBlk
AI_Events DNPAIEvntBLK
BP
DNPBackplane
Each of these object types are discussed in the following topics:
Page 48 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Ladder Logic
Name
Data Type
Description
DNP 3.0 Server over Ethernet Communication Module User Manual
Status
This object holds the module status information transferred with each read data
block transferred from the module. The following table describes the structure of
this object.
Scan_Cnt INT Program Scan Counter
Product_Name SINT[4] Product Code
Rev_Level SINT[4] Revision
Op_Sys SINT[4] Operating system revision
Run_Number SINT[4] Run number
Blk_Rd_Count INT Number of block read transfers
Blk_Wr_Count INT Number of block write transfers
Blk_Parse_Cnt INT Number of blocks parsed by module
Blk_Err INT Number of block errors
Rx_Frames INT Number of frames received for this unit
Tx_Frames INT Number of frames transmitted for this unit
Rx_Total INT Number of frames received
Sync_err INT Sync error count
Overrun_err INT Overrun error count
len_err INT Length error count
CRC_err INT CRC error count
Overflow_err INT Overflow error count
Seq_err INT Sequence error count
Addrs_err INT Address error count
BI_Events INT Number of binary events generated
BI_Queue INT Number of binary events in queue
AI_Events INT Number of analog input events
AI_Queue INT Number of analog input events in queue
FL_Events INT Number of float input events
Reserved INT Reserved
Bad_func_err INT Number of bad function code error count
Ukn_Obj_err INT Unknown Object error count
Range_err INT Range error count
App_Overflow INT Number of application level overflow errors
Multi_Frame_err INT Multi-frame error count
UDP_Rx_Count INT UDP Recieve Count
UDP_Tx_Count INT UDP transmit Count
Unsol_error INT Unsolicited Error Count
State_Value INT State Value
TCP_ST_value INT TCP Socket State Value
UDP_ST_Value INT UDP Socket State Value
Busywithmsg INT DNP Busy with Message State
App_Fragm INT Application fragment
Tx_frame_ST INT Transmit frame State
TCP_msg_len INT TCP message length
UDP_msg_len INT UDP message length
Port_Tx_St INT Port Transmit state
Free_Mem DINT Free Memory
ProSoft Technology, Inc. Page 49 of 139
February 11, 2011
Ladder Logic MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
This information is important as it can be used to view the "health" of the module.
If the module is not communicating, examine the object to help find the problem.
Additionally, you should use the configuration/debug port on the module to
confirm that the desired configuration of the module is implemented.
Data
The DNPData object stores all the data for an MVI56-DNPSNET module.
Contained within the object is an array for each data type. The array sizes are set
to match the configuration set for the module. If multiple MVI56-DNPSNET
modules are used within a rack, a copy of this structure may have to be made to
permit each module to have its own database sizes. Ladder logic is required to
transfer the data in this structure between the module and the processor. The
following table describes the structure of this object.
Name Data Type Description
DNP_BI INT[20] Number of DNP BI data words
DNP_AI INT[40] Number of DNP AI data points
DNP_FLTI REAL[20] Number of DNP FLTI data points
DNP_Cntr DINT[10] Number of DNP counter double-words
DNP_BO INT[40] Number of DNP BO data words
DNP_AO INT[40] Number of DNP AO data words
DNP_FLTO REAL[20] Number of DNP FLTO data points
CMDcontrolbits
Name Data Type Description
Warmboot BOOL WarmBoot module
ColdBoot BOOL ColdBoot module
GetDateNTime BOOL Get Date and Time from module
SetDateNTime BOOL Set Date and Time for module
SetBIEvents BOOL Send BI Event to Binary Input event buffer
SetAIEvents BOOL Send AI Event to Analog Input event buffer
GetFullStatus BOOL Request 9250 block for full status information
Clock
Name Data Type Description
Year DINT Year returned from GSV to processor
Month DINT Month returned from GSV to processor
Day DINT Day returned from GSV to processor
Hours DINT Hours returned from GSV to processor
Minutes DINT Minutes returned from GSV to processor
Seconds DINT Seconds returned from GSV to processor
MicroSeconds DINT MicroSeconds returned from GSV to processor
Synchronized INT If 1, time has been set by DNP master. 0 = waiting
for time to be set.
Page 50 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Ladder Logic
DNP 3.0 Server over Ethernet Communication Module User Manual
BP (Backplane)
The DNPBackplane Object stores the variables required for backplane data
transfer between the module and the processor. The following table describes
the structure of the object.
Name Data Type Description
LastRead INT Index of last read block
LastWrite INT Index of last write block
BlockIndex INT Computed block offset for data table
ReadData INT[600] Buffer File for data Read from Module
WriteData INT[600] Buffer File for data Written to Module
3.1.2 Special Objects
These objects utilize some of the advanced features the module provides. If your
application does not require the object, then you need not declare an instance of
the object. Each of the objects and associated function are discussed in the
following topics.
BI_Events
The DNPAIEvntBLKt object stores the information for a single binary input event
to be sent from the processor to the module in a command block 9958. The
structure shown in the following example contains all the parameters required for
a binary input event.
Name Data Type Description
EventCount INT Event Count
SeqCounter INT Sequence Counter
EventData DNPAIEvntData[10] Event Data Points
AIDataPoint INT DNP Analog Input Data Point
AIvalue INT DNP Analog Input Value
Day SINT Day
Month SINT Month
Minutes SINT Minutes
Hour SINT Hour
SecMsec INT Formatted, bits 0 to 9 = Milliseconds, bits 10-15 =
seconds
Year INT Year
ProSoft Technology, Inc. Page 51 of 139
February 11, 2011
Ladder Logic MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
AI_Events
The DNPBIEvntBlk object stores the information for a single analog input event
to be sent from the processor to the module in a command block 9959. The
structure shown in the following example contains all the parameters required for
an analog input event.
Name Data Type Description
EventCount INT Event Count
SeqCounter INT Sequence Counter
EventData DNPBIEvntData[12]
DataPoint INT DNP Binary Input Data Point
Day SINT Day
MonthState SINT Month and State Bit (state is MSB)
Minutes SINT Minutes
Hour SINT Hours
SecMsecond INT Formatted: Bits 0-9 = Milliseconds, bits 10 to 15 =
Seconds
Year INT Year
Page 52 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Ladder Logic
DNP 3.0 Server over Ethernet Communication Module User Manual
3.2 Adding the Module to an Existing Project
1 Select the I/O Configuration folder in the Controller Organization window of
RSLogix 5000, and then click the right mouse button to open a shortcut
menu. On the shortcut menu, choose N
EW MODULE
.
This action opens the Select Module dialog box:
2 Select the 1756-M
ODULE (GENERIC
1756 M
ODULE
) from the list and click OK.
This action opens the New Module dialog box.
3 Enter the Name, Description and Slot options for your application. You must
select the Comm Format as D
ATA -
INT in the dialog box, otherwise the
module will not communicate. Click OK to continue.
ProSoft Technology, Inc. Page 53 of 139
February 11, 2011
Ladder Logic MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Parameter Value
Name Enter a module identification string. Example:
DNPSNET_2
Description
Comm Format
Slot Enter the slot number in the rack where the MVI56-
Input Assembly Instance
Input Size
Output Assembly Instance
Output Size
Configuration Assembly Instance
Configuration Size
Enter a description for the module. Example: DNP 3.0
S
ERVER OVER ETHERNET COMMUNICATION MODULE
Select D
DNPSNET module is located.
1
250
2
248
4
0
ATA
-INT.
4 Select the Requested Packet Interval value for scanning the I/O on the
module. This value represents the minimum frequency that the module will
handle scheduled events. This value should not be set to less than 1
millisecond. The default value is 5 milliseconds. Values between 1 and 10
milliseconds should work with most applications.
Page 54 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Ladder Logic
DNP 3.0 Server over Ethernet Communication Module User Manual
5 Save the module. Click OK to dismiss the dialog box. The Controller
Organization window now displays the module's presence.
6 Copy the User-Defined Data Types from the sample program into your
existing RSLogix 5000 project.
7 Copy the Controller Tags from the sample program into your project.
8 Copy the Ladder Rungs from the sample program into your project.
ProSoft Technology, Inc. Page 55 of 139
February 11, 2011
Ladder Logic MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Page 56 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Diagnostics and Troubleshooting
DNP 3.0 Server over Ethernet Communication Module User Manual
4 Diagnostics and Troubleshooting
In This Chapter
LED Status Indicators ............................................................................ 58
Using ProSoft Configuration Builder (PCB) for Diagnostics................... 62
Reading Status Data from the Module .................................................. 73
The module provides information on diagnostics and troubleshooting in the
following forms:
LED status indicators on the front of the module provide general information
on the module's status.
Status data contained in the module can be viewed through the
Configuration/Debug port, using the troubleshooting and diagnostic
capabilities of ProSoft Configuration Builder (PCB).
Status data values can be transferred from the module to processor memory
and can be monitored there manually or by customer-created logic.
ProSoft Technology, Inc. Page 57 of 139
February 11, 2011
Diagnostics and Troubleshooting MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
4.1 LED Status Indicators
The LEDs indicate the module’s operating status as follows:
LED Color Status Indication
CFG Green On Data is being transferred between the module and a remote
Off No data is being transferred on the Configuration/Debug port.
P1 Green On Port not used in application
Off Port not used in application
P2 Green On Port not used in application
Off Port not used in application
APP Amber Off The MVI56-DNPSNET is working normally.
On The MVI56-DNPSNET module program has recognized a
BP ACT Amber On The LED is on when the module is performing a write
Off The LED is off when the module is performing a read
OK Red/
Green
BAT Red Off The battery voltage is OK and functioning.
Off The card is not receiving any power and is not securely
Green The module is operating normally.
Red
On The battery voltage is low or battery is not present. Allow
terminal using the Configuration/Debug port.
communication error on one of its DNP ports.
operation on the backplane.
operation on the backplane. Under normal operation, the LED
should blink rapidly on and off.
plugged into the rack.
The program has detected an error or is being configured. If
the LED remains red for over 10 seconds, the program has
probably halted. Remove the card from the rack and re-insert
the card to restart the module’s program.
battery to charge by keeping module plugged into rack for 24
hours. If BAT LED still does not go off, contact ProSoft
Technology, as this is not a user serviceable item.
If the APP, BP ACT and OK LEDs blink at a rate of every one-second, this
indicates a serious problem with the module. Call ProSoft Technology support to
arrange for repairs.
Page 58 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Diagnostics and Troubleshooting
DNP 3.0 Server over Ethernet Communication Module User Manual
4.1.1 Ethernet LED Indicators
LED State Description
Data OFF No activity on the Ethernet port.
GREEN Flash The Ethernet port is actively transmitting or receiving data.
Link OFF No physical network connection is detected. No Ethernet
communication is possible. Check wiring and cables.
GREEN Solid Physical network connection detected. This LED must be ON
solid for Ethernet communication to be possible.
4.1.2 Clearing a Fault Condition
Typically, if the OK LED on the front of the module turns RED for more than ten
seconds, a hardware problem has been detected in the module or the program
has exited.
To clear the condition, follow these steps:
1 Turn off power to the rack.
2 Remove the card from the rack.
3 Verify that all jumpers are set correctly.
4 If the module requires a Compact Flash card, verify that the card is installed
correctly.
5 Re-insert the card in the rack and turn the power back on.
6 Verify correct configuration data is being transferred to the module from the
ControlLogix controller.
If the module's OK LED does not turn GREEN, verify that the module is inserted
completely into the rack. If this does not cure the problem, contact ProSoft
Technology Technical Support.
4.1.3 Troubleshooting
Use the following troubleshooting steps if you encounter problems when the
module is powered up. If these steps do not resolve your problem, please contact
ProSoft Technology Technical Support.
Processor Errors
Problem description Steps to take
Processor fault Verify that the module is plugged into the slot that has been configured
for the module in the I/O Configuration of RSLogix.
Verify that the slot location in the rack has been configured correctly in
the ladder logic.
Processor I/O LED
flashes
ProSoft Technology, Inc. Page 59 of 139
February 11, 2011
This indicates a problem with backplane communications. A problem
could exist between the processor and any installed I/O module, not just
the MVI56-DNPSNET. Verify that all modules in the rack are correctly
configured in the ladder logic.
Diagnostics and Troubleshooting MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Module Errors
Problem description Steps to take
BP ACT LED (not
present on MVI56E
modules) remains OFF
or blinks slowly
MVI56E modules with
scrolling LED display:
<Backplane Status>
condition reads ERR
OK LED remains RED The program has halted or a critical error has occurred. Connect to the
This indicates that backplane transfer operations are failing. Connect to
the module’s Configuration/Debug port to check this.
To establish backplane communications, verify the following items:
The processor is in RUN or REM RUN mode.
The backplane driver is loaded in the module.
The module is configured for read and write data block transfer.
The ladder logic handles all read and write block situations.
The module is properly configured in the processor I/O configuration
and ladder logic.
Configuration/Debug port to see if the module is running. If the program
has halted, turn off power to the rack, remove the card from the rack and
re-insert it, and then restore power to the rack.
4.1.4 Error Status Table
The program maintains an error/status table that is transferred to the processor
in each read block. Ladder logic should be programmed to accept this block of
data and place it in the module’s controller tag. You can use the error/status data
to determine the "health" of the module.
The data in the block is structured as shown in the following table.
Word Variable Name Description
0 Scan Counter Program scan counter incremented each time the
program loop is executed.
1 to 2 Product Name (ASCII) These two words contain the product name of the
module in ASCII format.
3 to 4 Revision (ASCII) These two words contain the product revision level of the
firmware in ASCII format.
5 to 6 Operating System Revision
(ASCII)
7 to 8 Production Run Number
(ASCII)
9 Read Block Count Total number of blocks transferred from the module to
10 Write Block Count Total number of blocks transferred from the processor to
11 Parse Block Count Total number of blocks parsed by the module that were
12 Block number error Number of BTW requests that resulted in an incorrect
13 DNP Slave Port total
number of message frames
received by slave
14 DNP Slave Port total
number of response
message frames sent from
slave
These two words contain the module’s internal operating
system revision level in ASCII format.
These two words contain the production "batch" number
for the particular chip in the module in ASCII format.
the processor.
the module.
received from the processor.
BTW identification code.
This value represents the total number of message
frames that have matched this slaves address on this
port. This count includes message frames which the
slave may or may not be able to parse and respond.
This value represents the number of good (non-error)
responses that the slave has sent to the master on this
port. The presumption is that if the slave is responding,
the message was good. Note: This is a frame count.
Page 60 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Diagnostics and Troubleshooting
DNP 3.0 Server over Ethernet Communication Module User Manual
Word Variable Name Description
15 DNP Slave Port total
number of message frames
seen by slave
16 DNP Slave synchronization
error count (Physical Layer
Error)
17 DNP Slave overrun error
count (Physical Layer
Error)
18 DNP Slave length error
count (Physical Layer
Error)
19 DNP Slave bad CRC error
(Data Link Layer Error)
20 DNP Slave user data
overflow error (Transport
Layer Error)
21 DNP Slave sequence error
(Transport Layer Error)
22 DNP Slave address error
(Layer Error) (Transport
23 DNP Slave Binary Input
Event count
24 DNP Slave Binary Input
Event count in buffer
25 DNP Slave Analog Input
Event count
26 DNP Slave Analog Input
Event count in buffer
27 DNP Slave bad function
code error (Application
Layer Error)
28 DNP Slave object unknown
error (Application Layer
Error)
29 DNP Slave out of range
error (Application Layer
Error)
30 DNP Slave message
overflow error (Application
Layer Error)
31 DNP Slave multi-frame
message from DNP Master
error (Application Layer
Error)
32 Free Memory LSB Free memory in module
Free Memory MSB
This value represents the total number of message
frames received by the slave, regardless of the slave
address.
This value counts the number of times a sync error
occurs. The error occurs when extra bytes are received
before the start bytes (0x05 and 0x64) are received.
This value counts the number of times the overrun error
occurs. This error occurs when the mainline Data Link
Layer routine cannot read the data received on the
communication port before it is overwritten.
This value counts the number of times an invalid length
byte is received. If the length of the message does not
match the length value in the message, this error occurs.
This value counts the number of times a bad CRC value
is received in a message.
This value counts the number of times the application
layer receives a message fragment buffer which is too
small.
This value counts the number of times the sequence
numbers of multi-frame request fragments do not
increment correctly.
This value counts the number of times the source
addresses contained in a multi-frame request fragments
do not match.
This value contains the total number of binary input
events which have occurred.
This value represents the number of binary input events
which are waiting to be sent to the master.
This value contains the total number of analog input
events which have occurred.
This value represents the number of analog input events
which are waiting to be sent to the master.
This value counts the number of times a bad function
code for a selected object/variation is received by the
slave device.
This value counts the number of times a request for an
unsupported object is received by the slave device.
This value counts the number of times a parameter in the
qualifier, range or data field is not valid or out of range.
This value counts the number of times an application
response message from the slave is too long to transmit.
This value counts the number of times the slave receives
a multi-frame message from the master. The application
does not support multi-frame master messages.
ProSoft Technology, Inc. Page 61 of 139
February 11, 2011
Diagnostics and Troubleshooting MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
4.2 Using ProSoft Configuration Builder (PCB) for Diagnostics
The Configuration and Debug menu for this module is arranged as a tree
structure, with the Main menu at the top of the tree, and one or more submenus
for each menu command. The first menu you see when you connect to the
module is the Main menu.
Because this is a text-based menu system, you enter commands by typing the
[command letter] from your computer keyboard in the Diagnostic window in
ProSoft Configuration Builder (PCB). The module does not respond to mouse
movements or clicks. The command executes as soon as you press the
[
COMMAND LETTER
[
COMMAND LETTER
] — you do not need to press [E
NTER].
When you type a
], a new screen will be displayed in your terminal application.
4.2.1 Using the Diagnostic Window in ProSoft Configuration Builder
Tip: You can have a ProSoft Configuration Builder Diagnostics window open for more than one
module at a time.
To connect to the module’s Configuration/Debug serial port
1 Start PCB, and then select the module to test. Click the right mouse button to
open a shortcut menu.
2 On the shortcut menu, choose D
IAGNOSTICS
.
Page 62 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Diagnostics and Troubleshooting
DNP 3.0 Server over Ethernet Communication Module User Manual
This action opens the Diagnostics dialog box.
3 Press [?] to open the Main menu.
If there is no response from the module, follow these steps:
1 Click to configure the connection. On the Connection Setup dialog box, select
a valid com port or other connection type supported by the module.
2 Verify that the null modem cable is connected properly between your
computer’s serial port and the module. A regular serial cable will not work.
3 On computers with more than one serial port, verify that your communication
program is connected to the same port that is connected to the module.
If you are still not able to establish a connection, contact ProSoft Technology for
assistance.
ProSoft Technology, Inc. Page 63 of 139
February 11, 2011
Diagnostics and Troubleshooting MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
4.2.2 Navigation
All of the submenus for this module contain commands to redisplay the menu or
return to the previous menu. You can always return from a submenu to the next
higher menu by pressing [M] on your keyboard.
The organization of the menu structure is represented in simplified form in the
following illustration:
The remainder of this section shows the menus available for this module, and
briefly discusses the commands available to you.
Keystrokes
The keyboard commands on these menus are usually not case sensitive. You
can enter most commands in lowercase or uppercase letters.
The menus use a few special characters (?, -, +, @) that must be entered exactly
as shown. Some of these characters will require you to use the SHIFT, CTRL, or
ALT keys to enter them correctly. For example, on US English keyboards, enter
the ? command as SHIFT and /.
Also, take care to distinguish the different uses for uppercase letter "eye" (I),
lowercase letter "el" (L), and the number one (1). Likewise, uppercase letter "oh"
(O) and the number zero (0) are not interchangeable. Although these characters
look alike on the screen, they perform different actions on the module and may
not be used interchangeably.
Page 64 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Diagnostics and Troubleshooting
DNP 3.0 Server over Ethernet Communication Module User Manual
4.2.3 Main Menu
When you first connect to the module from your computer, your terminal screen
will be blank. To activate the main menu, press the [?] key on your computer’s
keyboard. If the module is connected properly, the following menu will appear.
Caution: Some of the commands available to you from this menu are designed for advanced
debugging and system testing only, and can cause the module to stop communicating with the
processor or with other devices, resulting in potential data loss or other failures. Only use these
commands if you are specifically directed to do so by ProSoft Technology Technical Support staff.
Some of these command keys are not listed on the menu, but are active nevertheless. Please be
careful when pressing keys so that you do not accidentally execute an unwanted command.
Viewing Block Transfer Statistics
Press [B] from the Main menu to view the Block Transfer Statistics screen.
Use this command to display the configuration and statistics of the backplane
data transfer operations between the module and the processor. The information
on this screen can help determine if there are communication problems between
the processor and the module.
Tip: To determine the number of blocks transferred each second, mark the numbers displayed at a
specific time. Then some seconds later activate the command again. Subtract the previous
numbers from the current numbers and divide by the quantity of seconds passed between the two
readings.
Viewing Module Configuration
Press [C] to view the Module Configuration screen.
Use this command to display the current configuration and statistics for the
module.
Opening the Database View Menu
Press [D] to open the Database View menu.
Use this menu command to view the current contents of the module’s database.
For more information about this submenu, see Database View Menu (page 69).
ProSoft Technology, Inc. Page 65 of 139
February 11, 2011
Diagnostics and Troubleshooting MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Opening the DNP Menu
Press [I] from the Main Menu to open the DNP Menu. This menu allows you to
view all data associated with the DNP Server driver. For more information about
the commands on this menu, refer to DNP Menu (page 67).
Receiving the Configuration File
Press [R] to download (receive) the current configuration file from the module.
Sending the Configuration File
Press [S] to upload (send) a configuration file from the module to your PC.
Viewing Version Information
Press [V] to view version information for the module.
Use this command to view the current version of the software for the module, as
well as other important values. You may be asked to provide this information
when calling for technical support on the product.
Values at the bottom of the display are important in determining module
operation. The Program Scan Counter value is incremented each time a
module’s program cycle is complete.
Tip: Repeat this command at one-second intervals to determine the frequency of program
execution.
Warm Booting the Module
Press [W] from the Main menu to warm boot (restart) the module.
This command will cause the program to exit and reload, refreshing configuration
parameters that must be set on program initialization. Only use this command if
you must force the module to reboot.
Opening the Network Menu
Press [@] to open the Network menu.
The Network menu allows you to send, receive and view the WATTCP.CFG file
that contains the IP, gateway and other network specification information. For
more information about this submenu, see Network Menu (page 71).
Exiting the Program
Press [ESC] to restart the module and force all drivers to be loaded. The module
will use the configuration stored in the module's flash memory to configure the
module.
Page 66 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Diagnostics and Troubleshooting
DNP 3.0 Server over Ethernet Communication Module User Manual
4.2.4 DNP Menu
When you press the [I] key, this opens the DNP Ethernet Protocol Menu. After
the option is selected, press the [?] key to display the menu and the following is
displayed:
Each option on the menu is discussed in the following topics.
Viewing DNP Set Up & Pointers
Press [B] to display the memory allocation and the database setup parameters.
Viewing DNP Configuration
Press [C] to display the configuration information for the server. Use this
command to confirm that the module is configured as desired. If any parameter is
not set correctly, adjust the configuration file and download the altered file to the
unit.
Opening the DNP Database View Menu
Press [D] to open the DNP Database View menu. Use this command to display
the database associated with each data type.
Viewing a List of Valid Hosts
Press [I] to view the list of IP addresses from which the module will accept
connections This list is only used if the module configuration parameter, Use IP
List, is set to a value other than 0.
Returning to the Main Menu
Press [M] to return to the Main menu.
Viewing DNP Communication Status
Press [1] to view DNP Communication Status. Use this command to view the
communication status data for the DNP driver.
ProSoft Technology, Inc. Page 67 of 139
February 11, 2011
Diagnostics and Troubleshooting MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Viewing TCP Socket Status
Press [2] to view the status of the TCP socket in the module. After selecting the
option, the following is displayed:
The parameters displayed have the following definitions:
Rx Count - Number of messages received on TCP socket
Tx Count - Number of messages transmitted on TCP socket
Tx State - 0=not transmitting, 1=transmitting
TCP State - Value used for TCP/IP socket state machine
Busy Flag - 0=not busy, 1=TCP has control of DNP server, 2=UDP has control
of DNP server, 3=Unsolicited message being sent
App Frame - 0=no application data frame data, 1=application data available
Tx Frame - 0=Data link level frame ready to send, 1=Data link level message not
ready to send
Packet Length - Length of message left to process
Viewing UDP Socket Status
Press [3] to view the status of the UDP socket in the module. After selecting the
option, the following is displayed:
The parameters displayed have the following definitions:
Rx Count - Number of messages received on UDP socket
Tx Count - Number of messages transmitted on UDP socket
Tx State - 0=not transmitting, 1=transmitting
TCP State - Value used for UDP/IP socket state machine
Busy Flag - 0=not busy, 1=TCP has control of DNP server, 2=UDP has control
of DNP server, 3=Unsolicited message being sent
App Frame - 0=no application data frame data, 1=application data available
Tx Frame - 0=Data link level frame ready to send, 1=Data link level message not
ready to send
Packet Length - Length of message left to process
Page 68 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Diagnostics and Troubleshooting
DNP 3.0 Server over Ethernet Communication Module User Manual
4.2.5 Database View Menu
Press [D] from the Main menu to open the Database View menu. Use this menu
command to view the current contents of the module database. Press [?] to view
a list of commands available on this menu.
Viewing Register Pages
To view sets of register pages, use the keys described below:
Command Description
[0]
[1]
[2]
Display registers 0 to 99
Display registers 1000 to 1099
Display registers 2000 to 2099
And so on. The total number of register pages available to view depends on your
module’s configuration.
Displaying the Current Page of Registers Again
Press [S] from the Database View menu to show the current page of registers
again.
This screen displays the current page of 100 registers in the database.
ProSoft Technology, Inc. Page 69 of 139
February 11, 2011
Diagnostics and Troubleshooting MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Moving Back Through 5 Pages of Registers
Press [-] from the Database View menu to skip five pages back in the database
to see the 100 registers of data starting 500 registers before the currently
displayed page.
Moving Forward (Skipping) Through 5 Pages of Registers
Press [+] from the Database View menu to skip five pages ahead in the database
to see the 100 registers of data starting 500 registers after the currently displayed
page.
Viewing the Previous Page of Registers
Press [P] from the Database View menu to display the previous page of data.
Viewing the Next Page of Registers
Press [N] from the Database View menu to display the next page of data.
Viewing Data in Decimal Format
Press [D] from the Database View menu to display the data on the current page
in decimal format.
Viewing Data in Hexadecimal Format
Press [H] from the Database View menu to display the data on the current page
in hexadecimal format.
Viewing Data in Floating-Point Format
Press [F] from the Database View menu to display the data on the current page
in floating-point format. The program assumes that the values are aligned on
even register boundaries. If floating-point values are not aligned as such, they
are not displayed properly.
Viewing Data in ASCII (Text) Format
Press [A] from the Database View menu to display the data on the current page
in ASCII format. This is useful for regions of the database that contain ASCII
data.
Returning to the Main Menu
Press [M] to return to the Main menu.
Page 70 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Diagnostics and Troubleshooting
DNP 3.0 Server over Ethernet Communication Module User Manual
4.2.6 Network Menu
From the IEC-870-5-104 Server menu press [@] to display the IEC-870-5-104
Network menu screen. The Network menu allows you to send, receive, and view
the WATTCP.CFG file that contains the IP and module addresses, and other
network information.
Transferring WATTCP.CFG to the Module
Press [R] to transfer a new WATTCP.CFG file from the PC to the module. Use
this command to change the network configuration for the module (for example,
the module’s IP address).
Press [Y] to confirm the file transfer, and then follow the instructions on the
terminal screen to complete the file transfer process.
Transferring WATTCP.CFG to the PC
Press [S] to transfer the WATTCP.CFG file from the module to your PC.
Press [Y] to confirm the file transfer, and then follow the instructions on the
terminal screen to complete the file transfer process.
After the file has been successfully transferred, you can open and edit the file to
change the module’s network configuration.
ProSoft Technology, Inc. Page 71 of 139
February 11, 2011
Diagnostics and Troubleshooting MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Viewing the WATTCP.CFG File on the module
Press [V] to view the module’s WATTCP.CFG file. Use this command to confirm
the module’s current network settings.
Returning to the Main Menu
Press [M] to return to the Main menu.
Page 72 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Diagnostics and Troubleshooting
DNP 3.0 Server over Ethernet Communication Module User Manual
4.3 Reading Status Data from the Module
The MVI56-DNPSNET module provides the status data in each read block. This
data can also be located in the module’s database. For a complete listing of the
status data object, refer to the Module Set Up section.
ProSoft Technology, Inc. Page 73 of 139
February 11, 2011
Diagnostics and Troubleshooting MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Page 74 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Reference
DNP 3.0 Server over Ethernet Communication Module User Manual
5 Reference
In This Chapter
Product Specifications ........................................................................... 76
Functional Overview .............................................................................. 79
MVI56-DNPSNET Application Design ................................................... 93
Cable Connections .............................................................................. 107
Configuration Data .............................................................................. 112
MVI56-DNPSNET Status Data ............................................................ 116
Internal Indication Bits (IIN Bits) for DNP Server ................................. 119
DNP Subset Definition ......................................................................... 120
Device Profile ...................................................................................... 126
Event Size Computation ...................................................................... 128
ProSoft Technology, Inc. Page 75 of 139
February 11, 2011
Reference MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
5.1 Product Specifications
The MVI56 DNP 3.0 Server over Ethernet Communications Module supports the
implementation of the DNP 3.0 (Distributed Network Protocol) over Ethernet,
allowing ControlLogix processors to easily communicate with host systems
supporting the protocol. The module supports DNP Subset Level 2 features and
some Level 3 features.
5.1.1 General Specifications
Single Slot - 1756 backplane compatible
The module is recognized as an Input/Output module and has access to
processor memory for data transfer between processor and module.
Ladder Logic is used for data transfer between module and processor.
Sample ladder file included.
Configuration data obtained from configuration text file downloaded to
module. Sample configuration file included
Local or remote rack
Page 76 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Reference
DNP 3.0 Server over Ethernet Communication Module User Manual
5.1.2 Hardware Specifications
Specification Description
Backplane Current Load 800 mA @ 5 Vdc
3 mA @ 24 Vdc
Operating Temperature 32°F to 140°F (0° C to 60°C)
Storage Temperature
Shock 30 g operational
Relative Humidity 5% to 95% (with no condensation)
LED Indicators Module Status
Application port (Ethernet)
Ethernet Port (Ethernet modules) 10/100 Base-T
Shipped with Unit RJ45 to DB-9M cables for each port
Debug/Configuration port (CFG)
CFG Port (CFG) RJ45 (DB-9M with supplied cable)
-40°F to 185°F (-40° C to 85°C)
50 g non-operational
Vibration: 5 g from 10 Hz to 150 Hz
Backplane Transfer Status
Application Status
Serial Activity
RJ45 Connector
Link and activity LED indicators
Electrical Isolation 1500 V rms at 50 Hz to 60 Hz
for 60 s, applied as specified in section 5.3.2 of
IEC 60950: 1991
Ethernet Broadcast Storm Resiliency = less than
or equal to 5000 [ARP] frames-per-second and
less than or equal to 5 minutes duration
6-foot RS-232 configuration cable
No hardware handshaking
ProSoft Technology, Inc. Page 77 of 139
February 11, 2011
Reference MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
5.1.3 Functional Specifications
The MVI56-DNPSNET module accepts DNP commands to control and monitor
the data stored in the DNP databases. This data is passed between the module
and the ControlLogix processor over the backplane for use in user applications.
DNP databases to house data for the slave port supporting the following
maximum input counts
Binary input 8000 points (500 words)
Binary output 8000 points (500 words)
Counter 250 (500 words)
Analog input 500
Analog output 500
Float Input 150
Float Output 150
User-definable module memory usage up to maximum point counts
Data movement between module using input/output image
Ethernet port supports both TCP and UDP over Ethernet
Supports DNP 3.0 in a level 2 implementation
Supports sending of input event data from the ladder to the module
Supports time synchronization from/to processor
Configurable via text file
Status and error information
All data in the DNP slave is contained in user-defined files
Page 78 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Reference
DNP 3.0 Server over Ethernet Communication Module User Manual
5.2 Functional Overview
The DNPSNET protocol driver exists as a single service port (DNPSNET port
20000) implementation that supports a single TCP port connection and multiple
UDP ports on a TCP/IP Ethernet network. The DNPSNET port operates as a
server, supporting the DNP 3.0 protocol in a Level 2 implementation using the
DNP User Group recommended extension for use on LAN/WAN. This is
published in "Transporting DNP V3.00 over Local and Wide Area Networks",
December 15, 1998 by the DNP Users Group and is available on the Internet at
http://www.dnp.org.
5.2.1 General Concepts
The following discussion explains several concepts that are important for
understanding module operation.
Backplane Data Transfer
The MVI56-DNPSNET module communicates directly over the ControlLogix
backplane. Data is paged between the module and the ControlLogix processor
across the backplane using the module's input and output images. The update
frequency of the images is determined by the scheduled scan rate defined by the
user for the module and the communication load on the module. Typical updates
are in the range of 1 to 10 milliseconds.
This bi-directional transference of data is accomplished by the module filling in
data in the module's input image to send to the processor. Data in the input
image is placed in the Controller Tags in the processor by the ladder logic. The
input image for the module is set to 250 words. This large data area permits fast
throughput of data between the module and the processor.
The processor inserts data to the module's output image to transfer to the
module. The module's program extracts the data and places it in the module's
internal database. The output image for the module is set to 248 words. This
large data area permits fast throughput of data from the processor to the module.
The following illustration shows the data transfer method used to move data
between the ControlLogix processor, the MVI56-DNPSNET module and the DNP
Network.
ProSoft Technology, Inc. Page 79 of 139
February 11, 2011
Reference MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
All data transferred between the module and the processor over the backplane is
through the input and output images. Ladder logic must be written in the
ControlLogix processor to interface the input and output image data with data
defined in the Controller Tags. All data used by the module is stored in its internal
databases. These databases are defined as a virtual DNP data tables with
addresses from 0 to the maximum number of points for each data type. The
following illustration shows the layout of the databases:
DATA AREA
DNP DATA BINARY INPUTS
ANALOG INPUTS
COUNTER DATA
BINARY OUTPUTS
ANALOG OUTPUTS
FROZEN DATA FROZEN COUNTER DATA
LAST VALUE DATA BINARY INPUTS
ANALOG INPUTS
EVENT DATA BINARY INPUT EVENTS
ANALOG INPUT EVENTS
Data contained in this database is paged through the input and output images by
coordination of the ControlLogix ladder logic and the MVI56-DNPSNET module's
program. Up to 248 words of data can be transferred from the module to the
processor at a time. Up to 247 words of data can be transferred from the
processor to the module.
Each block transferred from the module to the processor or from the processor to
the module contains a block identification code that describes the content of the
block.
The following table defines the blocks used by this module:
Block Number Function/Description
0 or -1 Dummy Blocks: Used by module when no data is to be transferred
1 to 45 DNP Data blocks
1000 to 1044 Output initialization blocks
9958 PLC Binary Input Event data
9959 PLC Analog Input Event Data
9970 Set PLC time using module's DNP time
9971 Set module's time using PLC time
9998 Warm Boot Request from PLC (Block contains no data)
9999 Cold Boot Request from PLC (Block contains no data)
Blocks 1 to 45 transfer data between the module and the processor. Blocks
1000 to 1044 are utilized to transfer the initial output databases (binary and
analog output data) from the processor to the module at startup. Blocks 9958 to
9999 are used for command control of the module. Each group of blocks are
discussed in the following topics.
Page 80 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Reference
DNP 3.0 Server over Ethernet Communication Module User Manual
Normal Data Transfer
Normal data transfer includes the paging of the user data found in the module’s
internal databases between the module and the controller. These data are
transferred through read (input image) and write (output image) blocks. Refer to
the Module Set Up section for a description of the data objects used with the
blocks and the ladder logic required. Each data block transferred between the
module and the processor has a specific block identification code that defines the
data set contained in the block. The following illustration shows the direction of
movement of the DNP data types between the module and the processor:
The structure and function of each block is described in the following topics:
Read Block
These blocks of data transfer information from the module to the ControlLogix
processor. The following table describes the structure of the input image.
Block Offset Content
0 Reserved
1 Write block ID
2 to 201 Read data
202 to 248 Status Data
249 Read block ID
The Read Block ID is an index value used to determine the location of where the
data will be placed in the ControlLogix processor controller tag array of module
read data. Each transfer can move up to 200 words (block offsets 2 to 201) of
data.
The Write Block ID associated with the block requests data from the ControlLogix
processor. Under normal program operation, the module sequentially sends read
blocks and requests write blocks. For example, if two blocks of read data and
three blocks of write data are to be moved between the module and the
processor, the sequence will be as follows:
R1W1→R2W2→R1W3→R2W1→R1W2→R2W3→R1W1→
This sequence will continue until interrupted by other write block numbers sent by
the controller or by a command request from a node on the DNP network or
operator control through the module’s Configuration/Debug port.
ProSoft Technology, Inc. Page 81 of 139
February 11, 2011
Reference MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Write Block
These blocks of data transfer information from the ControlLogix processor to the
module. The following table describes the structure of the output image.
Block Offset Content
0 Write Block ID
1 to 200 Write Data
201 to 247 Spare (Not used)
The Write Block ID is an index value used to determine the location in the
module’s database where the data will be placed. Each transfer can move up to
200words (block offsets 1 to 200) of data.
Trip/Close
The MVI56-DNPSNET module supports Trip/Close functionality for Binary Output
points.
This allows Trip/Close commands to be sent to the MVI56-DNPSNET module, for
dual point control. Each DNP Trip/Close command will occupy 2 bits within the
module memory.
This does overlap the regular pulse on/off and latch on/off Binary Output
database, therefore special consideration must be used to make sure that points
are not used twice.
The following table describes the address mapping for the module using Latch
and Pulse commands, and Trip/Close functionality.
DNP BO Database Point BO Latch/Pulse Point BO Trip/Close Point
0 BO 0 Close BO 0
1 BO 1 Trip BO 0
2 BO 2 Close BO 1
3 BO 3 Trip BO 1
4 BO 4 Close BO 2
5 BO 5 Trip BO 2
100 BO 100 Close BO 50
101 BO 101 Trip BO 50
1000 BO 1000 Close BO 500
1001 BO 1001 Trip BO 500
2046 BO 2046 Close BO 1023
2047 BO 2047 Trip BO 1023
As you can see from the above chart, trip/close requires 2 points within the
module’s DNP database. A trip is represented by the value of 2#10 for those 2
points, and a close is represented by the value of 2#01 for those same 2 points.
The module can only process 4000 trip/close points, as the database for the DNP
BO is limited to 8000 bits total.
Page 82 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Reference
DNP 3.0 Server over Ethernet Communication Module User Manual
Special Function Blocks
Special Function blocks are blocks used to control the module or request special
data from the module. The current version of the software supports several
special function blocks each of which is discussed in the following topics:
Binary Input Event Block (9958)
If the PLC sends a block 9958, the module will place the binary input event data
in the block into the event buffer and alter the data values for the points in the
DNP binary input database. The format for the event message is shown in the
following table.
Word Offset in Block Data Field(s) Description
0 Block ID This field contains the value of 9958 identifying the
event block to the module.
1 Event Count This field contains the number of events contained in
the block. Valid values for this field are 1 to 12.
2 Sequence
Counter
3 DNP Binary Input
Data point
4 Month/Day/State Formatted: bits 0 to 4 = Day, bits 8 to 11 = Month, bit
5 Hour/Minute Formatted: bits 0 to 5 = Minutes, bits 8 to 12 = Hour.
6 Sec/Millisecond Formatted: bits 0 to 9 = Milliseconds, bits 10 to 15 =
7 Year This is the four digit year for the event.
8 to 12 Five words of data for Event #2.
13 to 17 Five words of data for Event #3.
18 to 22 Five words of data for Event #4.
23 to 27 Five words of data for Event #5.
28 to 32 Five words of data for Event #6.
33 to 37 Five words of data for Event #7.
38 to 42 Five words of data for Event #8.
43 to 47 Five words of data for Event #9.
48 to 52 Five words of data for Event #10.
53 to 57 Five words of data for Event #11.
58 to 62 Five words of data for Event #12.
63 to 247 Spare Not Used
This field holds the sequence counter for each 9958
block transfer. This synchronizes and confirms
receipt of the block by the module.
This is the data point in the DNP binary input
database represented by the event.
15 = digital state for point. All other bits are ignored.
All other bits are ignored.
Seconds.
ProSoft Technology, Inc. Page 83 of 139
February 11, 2011
Reference MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Up to 12 events can be passed from the PLC to the module in each block. To
insure that the block reached the module and was processed, the module will
send a response read block 9958 to the PLC. The following table describes the
format of the block.
Word Offset in Block Data Field(s) Description
0 Reserved Reserved (0)
1 Block ID Block identification code for request from PLC by the
module.
2 Event Count This field contains the number of events processed
by the module.
3 Sequence
Counter
4 to 248 Spare Not used
249 Block ID Identification code for block set to 9958.
This field contains the sequence counter of the last
successful block 9958 received.
The sequence counter field in the returned block is set to the last successfully
processed block 9958 from the PLC. Compare this value to that sent by the PLC.
If the values match, the events can be removed from the PLC. If the values do
not match, or the PLC does not receive a 9958 block, the PLC must re-send the
block.
Page 84 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Reference
DNP 3.0 Server over Ethernet Communication Module User Manual
Analog Input Event Block (9959)
If the PLC sends a block 9959, the module will place the analog input event data
in the block into the event buffer and alter the data values for the points in the
DNP analog input database. The format for the event message is shown in the
following table.
Word Offset in Block Data Field(s) Description
0 Block ID This field contains the value of 9959 identifying the
event block to the module.
1 Event Count This field contains the number of events contained in
the block. Valid values for this field are 1 to 10.
2 Sequence Counter This field holds the sequence counter for each 9959
block transfer. This synchronizes and confirms
receipt of the block by the module.
3 DNP Analog Input
Data point
4 Analog Input
Value
5 Month/Day Formatted: bits 0 to 4 = Day, bits 8 to 11 = Month. All
6 Hour/Minute Formatted: bits 0 to 5 = Minutes, bits 8 to 12 = Hour.
7 Sec/Millisecond Formatted: bits 0 to 9 = Milliseconds, bits 10 to 15 =
8 Year Four digit year value for event.
9 to 14 Six words of data for Event #2.
15 to 20 Six words of data for Event #3.
21 to 26 Six words of data for Event #4.
27 to 32 Six words of data for Event #5.
33 to 38 Six words of data for Event #6.
39 to 44 Six words of data for Event #7.
45 to 50 Six words of data for Event #8.
51 to 56 Six words of data for Event #9.
57 to 62 Six words of data for Event #10.
63 to 247 Spare Not Used
This is the data point in the DNP analog input
database represented by the event.
This is the new analog input value represented in the
event.
other bits are ignored.
All other bits are ignored.
Seconds.
ProSoft Technology, Inc. Page 85 of 139
February 11, 2011
Reference MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Up to 10 events can be passed from the PLC to the module in each block. To
insure that the block reached the module and was processed, the module will
send a response read block 9959 to the PLC. The following table describes the
format of the block.
Word Offset in Block Data Field(s) Description
0 Reserved Reserved (0)
1 Block ID Block identification code for request from PLC by the
module.
2 Event Count This field contains the number of events processed
by the module.
3 Sequence Counter This field contains the sequence counter of the last
successful block 9959 received.
4 to 248 Spare Not used
249 Block ID Identification code for block set to 9959.
The sequence counter field in the returned block is set to the last successfully
processed block 9959 from the PLC. Compare this value to that sent by the PLC.
If the values match, the events can be removed from the PLC. If the values do
not match, or the PLC does not receive a 9959 block, the PLC must re-send the
block.
SOE Input Events Block (9961)
Block 9961 identification code is used by the PLC to send a set of SOE input
events to the module that use 64-bit time. This is based at a starting point of
January 1st, 1972. This block is for RS Logix versions prior to version 16.
Page 86 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Reference
DNP 3.0 Server over Ethernet Communication Module User Manual
Block Format for Write (9961)
Word Offset in
Data Field(s) Description
Block
0 Block ID This field contains the value of 9961 identifying the SOE
event block to the module.
1 Event Count This field contains the number of events contained in the
block. Valid values for this field are 1 to 20.
2 Sequence Counter This field is used to hold the sequence counter for each
9961 block transfer. This is used to synchronize and
confirm receipt of the block by the module.
3 DNP Binary Input
Data point
This is the data point in the DNP binary input database
represented by the event.
4 to 7 64-bit time This is the 64-bit time value generated by the SOE module.
8 Value This is the value for the event data. It is either a 0 or 1.
9 to 14 Six words of data for Event #2.
15 to 20 Six words of data for Event #3.
21 to 26 Six words of data for Event #4.
27 to 32 Six words of data for Event #5.
33 to 38 Six words of data for Event #6.
39 to 44 Six words of data for Event #7.
45 to 50 Six words of data for Event #8.
51 to 56 Six words of data for Event #9.
57 to 62 Six words of data for Event #10.
63 to 68 Six words of data for Event #11.
69 to 74 Six words of data for Event #12.
75 to 80 Six words of data for Event #13.
81 to 86 Six words of data for Event #14.
87 to 92 Six words of data for Event #15.
93 to 98 Six words of data for Event #16.
99 to 104 Six words of data for Event #17.
105 to 110 Six words of data for Event #18.
111 to 116 Six words of data for Event #19.
117 to 122 Six words of data for Event #20.
123 to 247 Spare Not Used
To insure the receipt of this block of information, the module returns a BTR block
9961 with the sequence counter set to the value of the last successful block 9961
received.
ProSoft Technology, Inc. Page 87 of 139
February 11, 2011
Reference MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Block Format for Read (9961)
Word Offset in
Data Field(s) Description
Block
0 Reserved Reserved (0)
1 Block ID Block identification code for request from PLC by the
module.
2 Event Count This field contains the number of events processed by the
module.
3 Sequence Counter This field contains the sequence counter of the last
successful block 9961 received.
4 to 248 Spare Not used
249 Block ID Identification code for block set to 9961.
SOE Input Events Block (9962)
Block 9962 identification code is used by the PLC to send a set of SOE input
events to the module that use 64-bit time. This is based at a starting point of
January 1st, 1970. This block is for RS Logix versions 16 and later.
Page 88 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Reference
DNP 3.0 Server over Ethernet Communication Module User Manual
Block Format for Write (9962)
Word Offset in
Data Field(s) Description
Block
0 Block ID This field contains the value of 9962 identifying the SOE
event block to the module.
1 Event Count This field contains the number of events contained in the
block. Valid values for this field are 1 to 20.
2 Sequence Counter This field is used to hold the sequence counter for each
9961 block transfer. This is used to synchronize and
confirm receipt of the block by the module.
3 DNP Binary Input
Data point
This is the data point in the DNP binary input database
represented by the event.
4 to 7 64-bit time This is the 64-bit time value generated by the SOE module.
8 Value This is the value for the event data. It is either a 0 or 1.
9 to 14 Six words of data for Event #2.
15 to 20 Six words of data for Event #3.
21 to 26 Six words of data for Event #4.
27 to 32 Six words of data for Event #5.
33 to 38 Six words of data for Event #6.
39 to 44 Six words of data for Event #7.
45 to 50 Six words of data for Event #8.
51 to 56 Six words of data for Event #9.
57 to 62 Six words of data for Event #10.
63 to 68 Six words of data for Event #11.
69 to 74 Six words of data for Event #12.
75 to 80 Six words of data for Event #13.
81 to 86 Six words of data for Event #14.
87 to 92 Six words of data for Event #15.
93 to 98 Six words of data for Event #16.
99 to 104 Six words of data for Event #17.
105 to 110 Six words of data for Event #18.
111 to 116 Six words of data for Event #19.
117 to 122 Six words of data for Event #20.
123 to 247 Spare Not Used
To insure the receipt of this block of information, the module returns a BTR block
9962 with the sequence counter set to the value of the last successful block 9962
received.
ProSoft Technology, Inc. Page 89 of 139
February 11, 2011
Reference MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Block Format for Read (9962)
Word Offset in
Data Field(s) Description
Block
0 Reserved Reserved (0)
1 Block ID Block identification code for request from PLC by the
module.
2 Event Count This field contains the number of events processed by the
module.
3 Sequence Counter This field contains the sequence counter of the last
successful block 9962 received.
4 to 248 Spare Not used
249 Block ID Identification code for block set to 9962.
Set Processor Time Block (9970)
This block transfers the module's time to the ControlLogix processor. Ladder
logic must be used to set the processor's clock using the data received. The
format of the block sent from the PLC has the following format:
Word Offset in Block Data Field(s) Description
0 Block ID This field contains the value of 9970 identifying the
block type to the module.
1 to 247 Not Used Not Used
The module responds to the request with a read block 9970 with the following
format:
Word Offset in Block Data Field(s) Description
0 Reserved Reserved (0)
1 Block Write ID This is the next block requested by the module.
2 Year This field contains the four-digit year for the new time
value.
3 Month This field contains the month value for the new time.
Valid entry for this field is in the range of 1 to 12.
4 Day This field contains the day value for the new time. Valid
entry for this field is in the range of 1 to 31.
5 Hour This field contains the hour value for the new time.
Valid entry for this field is in the range of 0 to 23.
6 Minute This field contains the minute value for the new time.
Valid entry for this field is in the range of 0 to 59.
7 Seconds This field contains the second value for the new time.
Valid entry for this field is in the range of 0 to 59.
8 Milliseconds This field contains the millisecond value for the new
time. Valid entry for this field is in the range of 0 to 999.
9 Remote Time
Synchronization
10 to 248 Not Used Not Used
249 Block Read ID This field contains the block identification code of 9970
This field informs the PLC if the date and time passed
has been synchronized with a remote DNP master
device on the module's slave port.
for the block.
Page 90 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Reference
DNP 3.0 Server over Ethernet Communication Module User Manual
Set Module Time Block (9971)
This block sets the clock in the module to match the clock in the ControlLogix
processor. If the PLC sends a block 9971, the module will set its time using the
data contained the block. The following table describes the format of the block.
Word Offset in Block Data Field(s) Description
0 Block ID This field contains the block identification code of 9971
for the block.
1 Year This field contains the four-digit year for the new time
value.
2 Month This field contains the month value for the new time.
Valid entry for this field is in the range of 1 to 12.
3 Day This field contains the day value for the new time. Valid
entry for this field is in the range of 1 to 31.
4 Hour This field contains the hour value for the new time. Valid
entry for this field is in the range of 0 to 23.
5 Minute This field contains the minute value for the new time.
Valid entry for this field is in the range of 0 to 59.
6 Seconds This field contains the second value for the new time.
Valid entry for this field is in the range of 0 to 59.
7 Milliseconds This field contains the millisecond value for the new
time. Valid entry for this field is in the range of 0 to 999.
8 to 247 Not Used Not Used
The module will respond to a valid 9971 block with a read block of the following
format:
Word Offset in
Block
0 Reserved Reserved (0)
1 Block Write ID This is the next block requested by the module.
2 to 248 Not Used Not Used
249 Block Read ID This field contains the block identification code of 9971
Data Field(s) Description
for the block.
Warm Boot Block (9998)
If the ControlLogix processor sends a block number 9998, the module will
perform a warm-boot operation.
Cold Boot Block (9999)
If the ControlLogix processor sends a block number 9999, the application
performs the cold-boot operation. The module exits the program and performs a
soft restart on the module.
ProSoft Technology, Inc. Page 91 of 139
February 11, 2011
Reference MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Data Flow Between MVI56-DNPSNET Module and the ControlLogix Processor
The following topics describe the flow of data between the two pieces of
hardware (ControlLogix processor and MVI56-DNPSNET module) and other
nodes on the DNP network. The DNP Server Driver allows the MVI56-DNPSNET
module to respond to data read and write commands issued by a master on the
DNP network. The following flow chart and associated table describe the flow of
data into and out of the module.
Step Description
1 The configuration information for the module is retrieved from the DNPSNET.CFG file on
the Compact Flash Disk. This information configures the module and define the Ethernet
node characteristics.
2 A Host device (DNP Master unit) issues a read or write command to the module’s node
address. The driver qualifies the message before accepting it into the module.
3 After the module accepts the command, the data is immediately transferred to or from
the appropriate internal database in the module. If the command is a read command, the
data is read out of the database and a response message is built. If the command is a
write command, the data is written directly into the database and a response message is
built.
4 After the data processing has been completed in Step 3, the response is issued to the
originating master node.
5 Counters are available in the Status Block that permit the ladder logic program to
determine the level of activity of the Slave Driver.
6 The module constantly monitors for command control blocks from the processor. If a
valid block is received, the function is executed. Additionally, data is constantly being
exchanged between the module and the processor.
Review the Module Configuration section for a complete list of the parameters
that must be defined for a slave port.
Page 92 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Reference
DNP 3.0 Server over Ethernet Communication Module User Manual
5.3 MVI56-DNPSNET Application Design
This documentation describes the MVI56-DNPSNET module configuration and
setup as it applies to application design. Before attempting to implement this
module with a DNP network, verify that the whole design of the system is
complete. This includes definition of all the data types and point counts required
for each type, all communication parameters required for the network including
media type and the use of advanced features such as unsolicited messaging.
These must be defined for all master and slave devices on the network.
Additionally, the DNP Device Profiles and DNP Subset Definition documents for
each device must be reviewed to make sure all the devices will interact on the
network as expected. Failure to fully understand these important documents for
all devices on the network will usually lead to many problems when implementing
the design.
It is important to fully understand the DNP specification as outlined in the Basic
Four Documents. These are available to users of the DNP users group. It is
recommended that all users of the module have access to these important
documents as they define the DNP data types, functions and variations. It will be
very difficult to implement the module without an understanding of the protocol
and the rules that are defined in the specification. Additionally, potential users
should review the DNP Subset and Conformance Test documents and the
document that discusses DNP protocol support on Ethernet using the UDP and
TCP protocols. These documents provide auxiliary information on the protocol.
All of these documents are available to members of the DNP User Group at
http://www.dnp.org (http://www.dnp.org). Please check this site for other
important information regarding the DNP protocol.
In order to implement a solution using the module, the ControlLogix processor
must be set up using predefined user data structures. The data transfer interface
requires ladder logic in order to interface data in the module with that in the
processor. The program required for data transfer is developed in ladder and is
discussed in the Module Set Up section. This program will interact with the
module by sending and receiving data and issuing special control commands.
Data tags in the ControlLogix processor contain the data to be used by the
module and the configuration information is stored in the text file,
DNPSNET.CFG, stored on the module's Compact Flash Disk. Before you
generate the program or layout the data files, you must first design your system.
Time spent doing system design at the outset of the project will greatly enhance
the success and ease of development of the project.
5.3.1 Designing the system
System design defines the data requirements of the system, communication
parameters, and module functionality. The application developer should refer to
the person responsible for the DNP master and slave device configurations to
verify that the functionality and data types required for the whole system are
consistent. Review the DNP Device Profile and DNP Subset documentation for a
definition of the level of DNP support offered by the module.
The following topics describe each element of system design.
ProSoft Technology, Inc. Page 93 of 139
February 11, 2011
Reference MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Data Requirements
This phase of design defines what data elements are to be interfaced in the
ControlLogix processor with the DNP master. The module provides the following
data types: digital input, digital output, counter, analog input, analog output, float
input and float output. All communications between the DNP master and the PLC
is through these data types. Therefore, all data to be used by the system must be
contained and configured in one of these data types.
The following illustration shows the databases maintained by the module for the
DNP data.
DATA AREA
DNP DATA
FROZEN DATA FROZEN COUNTER DATA
LAST VALUE DATA
EVENT DATA BINARY INPUT EVENTS
BINARY INPUTS
ANALOG INPUTS
FLOAT INPUTS
COUNTER DATA
BINARY OUTPUTS
ANALOG OUTPUTS
FLOAT OUTPUTS
BINARY INPUTS
ANALOG INPUTS
FLOAT INPUTS
ANALOG INPUT EVENTS
FLOAT INPUT EVENTS
The module is responsible for maintaining the databases using data acquired
from the PLC and DNP master attached network port.
The following illustration shows the interaction of the binary and analog input
points with the databases.
All data for these data types is derived from the processor and is passed to the
module over the backplane. The module will constantly monitor for changes in
this data and generate event messages when point values change. For binary
input points, events will be generated on any state change. For analog input
points, events will be generated for points that have a current value outside of the
user-set deadband based on the last value used for an event.
Page 94 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Reference
DNP 3.0 Server over Ethernet Communication Module User Manual
The following illustration shows the interaction of the counter points with the
databases.
This data is constantly sourced from the processor and placed in the module’s
internal database. This information is available to the remote master for
monitoring. When the module receives a freeze command from the master unit, it
will copy the current counter values into the frozen counter database area. The
remote master can then monitor this information. If the module receives a
counter freeze with reset command, the current counter values will be passed to
the frozen counter database and only the module’s values will be set to 0.
Note: This data is not sent to the controller, and the zero data can be overwritten by the counter
data contained in the controller. Therefore, the freeze with reset should not be used with this
module. The results will not be as expected. There is no way to guarantee that counts will not be
lost during the reset step in the module and controller. As a result, this feature was not
implemented in the module.
The following illustration shows the interaction of the binary, analog and Float
output points with the databases.
Output data is sourced from the controlling master station and passed to the
processor over backplane from the module. These data are used in the ladder
logic to control operations and I/O in the processor.
ProSoft Technology, Inc. Page 95 of 139
February 11, 2011
Reference MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
Data Transfer Interface
Data is transferred between the ControlLogix processor and the module using
module’s I/O images. Each block transfer operation transfers up to a maximum of
200 words of data. The other words in the block contain block header
identification codes, or not used. The module defines the blocks to be transferred
between the PLC and the module when the system is initialized. For the PLC
read operations, word 249 of the module’s input image identifies the data set
contained in the image. Word 1 contains the block index the module is requesting
the processor to write. The PLC constructs the write image to send to the module
in the module’s output image. The first word of the block identifies the data set
contained in the block.
The module determines the block numbers required based on the module read
and write register counts defined in the configuration file. The user is responsible
for defining these parameters and the starting location of these data areas in the
module’s database correctly. These data must correspond to the DNP database
definitions defined. The module stores the data in fixed order for the data types.
The size of each data area for each type is determined by the user configuration.
An example is given in the following table.
DATA AREA Cfg Points Words Offset
DNP DATA BINARY
INPUTS
ANALOG
INPUTS
FLOAT INPUTS 10 10 20 50 to 69
COUNTER
DATA
BINARY
OUTPUTS
ANALOG
OUTPUTS
FLOAT
OUTPUTS
2 32 2 0 to 1
48 48 48 2 to 49
25 25 50 70 to 119
4 64 4 120 to 123
52 52 52 124 to 175
20 20 40 176 to 215
For the example above, 120 registers will be transferred from the processor (all
the input data) and 96 registers will be transferred to the processor (all the output
data). The data transfer parameters should be defined as follows:
Parameter Value
Write Register Start: 120
Write Register Count: 96
Read Register Start: 0
Read Register Count: 120
The configuration above will require one block to read and one block to write all
the DNP data between the module and the processor.
Page 96 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Reference
DNP 3.0 Server over Ethernet Communication Module User Manual
Note that in one block, one or more data types may be transferred. This is
especially important when considering the counter and Float data. They require
two registers to store their value. The value of a counter should never be passed
in two separate blocks. To avoid this potential problem, always configure the
module to have the counter data start on an even word number same rule
applies to Float points.
The following figure displays the direction of movement of the DNP database
data between the module and the processor.
DNP MEMORY
WRITE BLOCK FROM
PROCESSOR
WRITE BLOCK FROM
PROCESSOR
READ BLOCK FROM
MODULE
READ BLOCK FROM
MODULE
→
→
→
→
←
←
←
←
→
→
→
→
←
←
←
←
DIGITAL INPUT DATA
ANALOG INPUT DATA
FLOAT INPUT DATA
COUNTER DATA
BINARY OUTPUT DATA
ANALOG OUTPUT DATA
FLOAT OUTPUT DATA
FROZEN COUNTER, LAST
VALUE AND EVENT DATA
It is important to understand the relationship of the block identifications and the
data in the module. Confident data handling in the module is only accomplished if
the user defines a consistent set of parameters in the module configuration,
handles the read and write operations for the blocks in the module in the PLC
ladder logic and understands the requirements of the DNP master unit.
The Reference chapter contains forms to aid in designing your system. They can
be used to document the relationship between the point assignments, block
identification numbers and the PLC file and offset values and to define the
program configuration. Use these forms during your design phase.
ProSoft Technology, Inc. Page 97 of 139
February 11, 2011
Reference MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
DNP Digital Input Data
This data type stores the binary value of 1 or 0. The size of this data area is
determined from the configuration parameter Binary Inputs (number of words,
each containing 16 binary input points). These data are transferred to the module
from the PLC using the read operation. Therefore, these data are read-only for
the module and the DNP master unit communicating with the module. When the
module receives a new block of this data from the PLC, it compares the new
values to those currently in the database. If there is a change in any of the data,
the module will generate an event message for the points that change.
The remote DNP master unit can read the current status data and the event data
from the module. Event messages generated by the module can be retrieved
using a poll for Class 2 data, as all digital input events are considered a Class 2
data type. If unsolicited message generation is enabled in the application, the
events will automatically be sent by the module to the DNP master unit when the
maximum event count for Class 2 data is reached or when the timeout for
unsolicited messages is exceeded. A data flow diagram for the digital input data
is shown in the following figure.
Page 98 of 139 ProSoft Technology, Inc.
February 11, 2011
MVI56-DNPSNET ♦ ControlLogix Platform Reference
DNP 3.0 Server over Ethernet Communication Module User Manual
DNP Digital Output Data
This data type stores digital control and command state data received from the
DNP master unit with a value of 1 or 0. The size of this data area is determined
from the configuration parameter Binary Outputs (defines number of words, each
containing 16 binary output points). These data are transferred from the module
to the PLC using the write operation. Therefore, these data are read-only for the
PLC, as the PLC cannot directly alter these values in module. It is the
responsibility of the DNP master unit to maintain this data. For example, if the
DNP master sets a digital point on, it will remain on until the master resets the
point. A data flow diagram for the digital output data is shown in the following
figure.
ProSoft Technology, Inc. Page 99 of 139
February 11, 2011
Reference MVI56-DNPSNET ♦ ControlLogix Platform
User Manual DNP 3.0 Server over Ethernet Communication Module
DNP Counter Data
This data type stores accumulated count data. These data are stored in the
module in a double word value and have a data range of 0 to 4,294,967,296. The
size of this data area is determined from the configuration parameter Counters.
The PLC transfers data of this type to the module using the read operation. The
module maintains two values for each counter point: a current running value and
a frozen value. The DNP master must send the freeze command to the module in
order to transfer the current running values to the frozen area.
Note: The freeze-reset command is not supported in the data transfer operation. There is no way
to guarantee counts will not be lost using the freeze-reset operation, therefore, this feature is not
implemented.
A data flow diagram for the counter data is shown in the following figure.
Page 100 of 139 ProSoft Technology, Inc.
February 11, 2011
Loading...