ProSoft Technology MVI71-DNP User Manual
MVI71-DNP
PLC Platform
DNP 3.0 Master/Slave Communication
Module
User Manual
August 23, 2007
Please Read This Notice
Successful application of this module requires a reasonable working knowledge of the PLC
hardware, the MVI71-DNP Module and the application in which the combination is to be used. For
this reason, it is important that those responsible for implementation satisfy themselves that the
combination will meet the needs of the application without exposing personnel or equipment to
unsafe or inappropriate working conditions.
This manual is provided to assist the user. Every attempt has been made to assure that the
information provided is accurate and a true reflection of the product's installation requirements. In
order to assure a complete understanding of the operation of the product, the user should read all
applicable documentation on the operation of the hardware.
Under no conditions will ProSoft Technology be responsible or liable for indirect or consequential
damages resulting from the use or application of the product.
Reproduction of the contents of this manual, in whole or in part, without written permission from
ProSoft Technology is prohibited.
Information in this manual is subject to change without notice and does not represent a
commitment on the part of ProSoft Technology Improvements and/or changes in this manual or the
product may be made at any time. These changes will be made periodically to correct technical
inaccuracies or typographical errors.
Warning: This module is not hot-swappable! Always remove power from the rack
before inserting or removing this module, or damage may result to the module, the
processor, or other connected devices.
Power, Input, and Output (I/O) wiring must be in accordance with Class 1,
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.
A Warning – Explosion Hazard – Substitution of components may impair
suitability for Class 1, Division 2.
B Warning – Explosion Hazard – When in hazardous locations, turn off
power before replacing or wiring modules.
C Warning – Explosion Hazard – Do not disconnect equipment unless power
has been switched off or the area is known to be non-hazardous.
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 the product, documentation or support,
please write or call us.
ProSoft Technology
1675 Chester Avenue, Fourth Floor
Bakersfield, CA 93301
+1 (661) 716-5100
+1 (661) 716-5101 (Fax)
http://www.prosoft-technology.com
Copyright © ProSoft Technology, Inc. 2000 - 2007. All Rights Reserved.
MVI71-DNP User Manual
August 23, 2007
PSFT.DNP.MVI71.UM.07.08.23
ProSoft Technology ®, ProLinx ®, inRAx ®, ProTalk® and RadioLinx ® are Registered Trademarks
of ProSoft Technology, Inc.
Contents MVI71-DNP ♦ PLC Platform
DNP 3.0 Master/Slave Communication Module
Contents
PLEASE READ THIS NOTICE.............................................................................................................................. 2
Your Feedback Please ...................................................................................................................................... 3
GUIDE TO THE MVI71-DNP USER MANUAL...................................................................................................... 9
1 START HERE ..............................................................................................................................................11
1.1 System Requirements.............................................................................................................................11
1.2 Package Contents ..................................................................................................................................12
1.3 Setting Jumpers......................................................................................................................................13
1.4 Install the Module in the Rack.................................................................................................................13
1.5 Connect your PC to the Processor .........................................................................................................15
1.6 Download the Sample Program to the Processor ...................................................................................16
1.6.1 Configuring RSLinx .......................................................................................................................17
1.7 Connect your PC to the Module..............................................................................................................19
2 INSTALLING AND CONFIGURING THE MODULE....................................................................................21
2.1 Module Data ...........................................................................................................................................23
2.1.1 Status Data ...................................................................................................................................23
2.1.2 User Data ......................................................................................................................................25
2.2 Configuration File....................................................................................................................................26
2.2.1 [Module] ........................................................................................................................................27
2.2.2 [DNP Slave]...................................................................................................................................27
2.2.3 [DNP Slave Database] ..................................................................................................................34
2.2.4 [DNP Slave Binary Inputs].............................................................................................................36
2.2.5 [DNP Slave Analog Inputs]............................................................................................................36
2.2.6 [DNP Slave Float Inputs] ...............................................................................................................37
2.2.7 [Secondary Port]............................................................................................................................37
2.2.8 [DNP Master].................................................................................................................................39
2.2.9 [IED Database]..............................................................................................................................40
2.2.10 [DNP Master Slave List] ................................................................................................................41
2.2.11 [DNP Master Commands] .............................................................................................................41
2.2.12 Slave List.......................................................................................................................................46
2.2.13 Command List ...............................................................................................................................47
2.3 Uploading and Downloading the Configuration File ................................................................................50
2.3.1 Transferring the Configuration File to Your PC..............................................................................50
2.3.2 Transferring the Configuration File to the Module .........................................................................52
3 LADDER LOGIC..........................................................................................................................................57
4 DIAGNOSTICS AND TROUBLESHOOTING..............................................................................................59
4.1 Reading Status Data From the Module...................................................................................................59
4.1.1 The Configuration/Debug Menu ....................................................................................................59
4.1.2 Required Hardware .......................................................................................................................60
4.1.3 Required Software.........................................................................................................................61
4.1.4 Using the Configuration/Debug Port..............................................................................................61
4.1.5 Main Menu ....................................................................................................................................62
4.1.6 The Class Assignment Menu ........................................................................................................65
4.1.7 DNP Database View Menu............................................................................................................67
4.1.8 Master Command List Menu .........................................................................................................70
4.1.9 Master Command Error List Menu ................................................................................................71
ProSoft Technology, Inc. Page 5 of 172
August 23, 2007
MVI71-DNP ♦ PLC Platform Contents
DNP 3.0 Master/Slave Communication Module
4.2 LED Status Indicators.............................................................................................................................72
4.3 Clearing a Fault Condition ......................................................................................................................72
4.4 Troubleshooting......................................................................................................................................73
5 REFERENCE...............................................................................................................................................75
5.1 Product Specifications ............................................................................................................................75
5.1.1 Features and Benefits ...................................................................................................................76
5.1.2 General Specifications ..................................................................................................................76
5.1.3 Hardware Specifications ...............................................................................................................76
5.1.4 Functional Specifications ..............................................................................................................77
5.2 Functional Overview ...............................................................................................................................78
5.2.1 General Concepts .........................................................................................................................78
5.2.2 Data Flow Between MVI71-DNP Module and PLC Processor ......................................................91
5.3 Designing the system .............................................................................................................................94
5.3.1 System Design Considerations .....................................................................................................94
5.3.2 Data Requirements .......................................................................................................................95
5.4 Cable Connections ...............................................................................................................................111
5.4.1 RS-232 Configuration/Debug Port...............................................................................................111
5.4.2 RS-232........................................................................................................................................113
5.4.3 RS-422........................................................................................................................................115
5.4.4 RS-485........................................................................................................................................116
5.4.5 DB9 to RJ45 Adaptor (Cable 14).................................................................................................116
5.5 Collision Avoidance (DNP modules only) .............................................................................................117
5.6 Block Assignments ...............................................................................................................................118
5.6.1 PLC Program Block Assignments vs. File:Offset ........................................................................118
5.7 DNP Configuration Forms.....................................................................................................................121
5.7.1 DNP User File Configuration.......................................................................................................121
5.8 MVI71-DNP Communication Module Configuration..............................................................................124
5.9 Error Status Table.................................................................................................................................132
5.10 Module Error Codes.........................................................................................................................136
5.10.1 Slave Port Communication Errors ...............................................................................................136
5.10.2 System Configuration Errors .......................................................................................................137
5.10.3 DNP Port Configuration Errors ....................................................................................................137
5.11 Command Error Codes ....................................................................................................................138
5.11.1 General Command Errors ...........................................................................................................138
5.11.2 Application Layer Errors ..............................................................................................................139
5.12 Event Size Computation ..................................................................................................................140
5.13 Device Profile...................................................................................................................................141
5.14 Slave Unit Device Profile Object Subset ..........................................................................................142
5.15 Master Unit Device Profile Object Subset ........................................................................................150
6 PROSOFT TECHNOLOGY, INC., SUPPORT, SERVICE & WARRANTY................................................159
6.1 How to Contact Us: Sales and Support ................................................................................................160
6.2 Return Material Authorization (RMA) Policies and Conditions..............................................................161
6.2.1 All Product Returns .....................................................................................................................161
6.3 Procedures for Return of Units Under Warranty ...................................................................................161
6.4 Procedures for Return of Units Out of Warranty ...................................................................................162
6.4.1 Un-repairable Units .....................................................................................................................162
6.4.2 Purchasing Warranty Extension..................................................................................................163
Page 6 of 172 ProSoft Technology, Inc.
August 23, 2007
Contents MVI71-DNP ♦ PLC Platform
DNP 3.0 Master/Slave Communication Module
6.5 LIMITED WARRANTY ..........................................................................................................................163
6.5.1 What Is Covered By This Warranty .............................................................................................163
6.5.2 What Is Not Covered By This Warranty.......................................................................................164
6.5.3 DISCLAIMER REGARDING HIGH RISK ACTIVITIES................................................................165
6.5.4 DISCLAIMER OF ALL OTHER WARRANTIES...........................................................................165
6.5.5 LIMITATION OF REMEDIES**....................................................................................................165
6.5.6 Time Limit for Bringing Suit .........................................................................................................165
6.5.7 No Other Warranties ...................................................................................................................166
6.5.8 Intellectual Property.....................................................................................................................166
6.5.9 Additional Restrictions Relating To Software And Other Intellectual Property.............................166
6.5.10 Allocation of risks ........................................................................................................................166
6.5.11 Controlling Law and Severability .................................................................................................167
INDEX.................................................................................................................................................................169
ProSoft Technology, Inc. Page 7 of 172
August 23, 2007
MVI71-DNP ♦ PLC Platform Contents
DNP 3.0 Master/Slave Communication Module
Page 8 of 172 ProSoft Technology, Inc.
August 23, 2007
Start Here MVI71-DNP ♦ PLC Platform
DNP 3.0 Master/Slave Communication Module
Guide to the MVI71-DNP User Manual
Function Section to Read Details
Introduction
(Must Do)
Verify Communication,
Diagnostic and
Troubleshooting
Reference
Product Specifications
Functional Overview
Glossary
Support, Service, and
Warranty
Index
→
→
→
→
Start Here (page
21, page 11)
Verifying
Communication
(page 59)
Diagnostics and
Troubleshooting
(page 59)
Reference
75)
Functional
Overview (page 78)
Product
Specifications
(page 75)
Support, Service
and Warranty
(page 159)
(page
This Section introduces the customer to the
module. Included are: package contents,
system requirements, hardware installation,
and basic configuration.
This section describes how to verify
communications with the network. Diagnostic
and Troubleshooting procedures.
These sections contain general references
associated with this product, Specifications,
and the Functional Overview.
This section contains Support, Service and
Warranty information.
Index of chapters.
ProSoft Technology, Inc. Page 9 of 172
August 23, 2007
MVI71-DNP ♦ PLC Platform Start Here
DNP 3.0 Master/Slave Communication Module
Page 10 of 172 ProSoft Technology, Inc.
August 23, 2007
Start Here MVI71-DNP ♦ PLC Platform DNP 3.0 Master/Slave Communication Module
1 Start Here
In This Chapter
¾ System Requirements............................................................ 11
¾ Package Contents.................................................................. 12
¾ Setting Jumpers ..................................................................... 13
¾ Install the Module in the Rack ................................................ 13
¾ Connect your PC to the Processor......................................... 15
¾ Download the Sample Program to the Processor ..................16
¾ Connect your PC to the Module ............................................. 19
Installing the MVI71-DNP module requires a reasonable working knowledge of
the Rockwell Automation hardware, the MVI71-DNP Module and the application
in which they will be used.
Caution: It is important that those responsible for implementation can complete
the application without exposing personnel, or equipment, to unsafe or inappropriate
working conditions. Safety, quality and experience are key factors in a successful
installation.
1.1 System Requirements
The MVI71-DNP module requires the following minimum hardware and software
components:
Rockwell Automation PLC processor, with compatible power supply and one
free slot in the rack, for the MVI71-DNP module. The module requires 800mA
of available power.
Rockwell Automation RSLogix 5 programming software.
Rockwell Automation RSLinx communication software
Pentium® 100 MHz minimum. Pentium III 700 MHz (or better) recommended
Supported operating systems:
o Microsoft Windows XP
o Microsoft Windows 2000
o Microsoft Windows NT v4.0 with Service Pack 3 or greater
o Microsoft Windows ME
o Microsoft Windows 98
64 Mbytes of RAM minimum, 256 Mbytes of RAM recommended
ProSoft Technology, Inc. Page 11 of 172
August 23, 2007
MVI71-DNP ♦ PLC Platform Start Here
DNP 3.0 Master/Slave Communication Module
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
3.5 inch floppy disk drive
HyperTerminal or other terminal emulator program capable of file transfers
using Ymodem protocol.
1.2 Package Contents
The following components are included with your MVI71-DNP 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
1 Cable
3 Cable
2 Adapter 1454-9F
1
MVI71-DNP
Module
ProSoft
Solutions
CD
MVI71-DNP DNP 3.0 Master/Slave Communication Module
RS232 Null
Modem
Cable #14, RJ45 to
DB9 Male Adapter
For RS232 Connection to the CFG Port
For DB9 Connection to Module’s Port
Two Adapters, DB9 Female to Screw Terminal.
For RS422 or RS485 Connections to Port 1 and 2
of the Module
Contains sample programs, utilities and
documentation for the MVI71-DNP module.
If any of these components are missing, please contact ProSoft Technology
Support for replacement parts.
Page 12 of 172 ProSoft Technology, Inc.
August 23, 2007
Start Here MVI71-DNP ♦ PLC Platform
DNP 3.0 Master/Slave Communication Module
1.3 Setting Jumpers
The following illustration shows the jumper configurations for the various RS
interfaces. If you are using an interface other than RS-232 (default), you must
change the jumpers as shown:
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.
1.4 Install the Module in the Rack
If you have not already installed and configured your PLC processor and power
supply, please do so before installing the MVI71-DNP 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 MVI71-DNP into the
PLC™ chassis. Use the same technique recommended by Rockwell Automation
to remove and install PLC modules.
ProSoft Technology, Inc. Page 13 of 172
August 23, 2007
MVI71-DNP ♦ PLC Platform Start Here
DNP 3.0 Master/Slave Communication Module
Warning: This module is not hot-swappable! Always remove power from the rack
before inserting or removing this module, or damage may result to the module, the
processor, or other connected devices.
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 will need to 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 PLC
rack.
6 Turn power ON.
Note: If you insert the module improperly, the system may stop working, or may
behave unpredictably.
Page 14 of 172 ProSoft Technology, Inc.
August 23, 2007
Start Here MVI71-DNP ♦ PLC Platform
DNP 3.0 Master/Slave Communication Module
1.5 Connect your PC to the Processor
7 Connect the right-angle connector end of the cable to your controller at the
communications port.
8 Connect the straight connector end of the cable to the serial port on your
computer.
ProSoft Technology, Inc. Page 15 of 172
August 23, 2007
MVI71-DNP ♦ PLC Platform Start Here
DNP 3.0 Master/Slave Communication Module
1.6 Download the Sample Program to the Processor
¾ To download the sample program from RSLogix 5 to the PLC
processor:
Note: The key switch on the front of the PLC processor must be in the REM position.
1 If you are not already online to the processor, open the Communications
menu, and then choose Download. RSLogix will establish communication
with the processor.
2 Click the Download button to transfer the sample program to the processor.
3 When prompted, choose Computer to PLC
4 RSLogix will compile the program and transfer it to the processor. This
process may take a few minutes.
Page 16 of 172 ProSoft Technology, Inc.
August 23, 2007
Start Here MVI71-DNP ♦ PLC Platform
DNP 3.0 Master/Slave Communication Module
5 When the download is complete, RSLogix will open another confirmation
dialog box. 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.
1.6.1 Configuring RSLinx
¾ If RSLogix is unable to establish communication with the processor,
follow these steps:
1 Open RSLinx.
2 Open the Communications menu, and choose Configure Drivers.
This action opens the Configure Drivers dialog box.
ProSoft Technology, Inc. Page 17 of 172
August 23, 2007
MVI71-DNP ♦ PLC Platform Start Here
DNP 3.0 Master/Slave Communication Module
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".
3 Click to select the driver, and then click Configure. This action opens the
Configure Allen-Bradley DF1 Communications Device dialog box.
4 Click the Auto-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 18 of 172 ProSoft Technology, Inc.
August 23, 2007
Start Here MVI71-DNP ♦ PLC Platform
DNP 3.0 Master/Slave Communication Module
1.7 Connect 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 or laptop.
ProSoft Technology, Inc. Page 19 of 172
August 23, 2007
MVI71-DNP ♦ PLC Platform Start Here
DNP 3.0 Master/Slave Communication Module
Page 20 of 172 ProSoft Technology, Inc.
August 23, 2007
Installing and Configuring the Module MVI71-DNP ♦ PLC Platform
DNP 3.0 Master/Slave Communication Module
2 Installing and Configuring the Module
In This Chapter
¾ Module Data........................................................................... 23
¾ Configuration File................................................................... 26
¾ Uploading and Downloading the Configuration File ............... 50
This chapter describes how to install and configure the module to work with your
application. The configuration process consists of the following steps.
1 Modify the module's configuration files to meet the needs of your application,
and copy the updated configuration to the module. Example configuration
files are provided on the CD-ROM. Refer to the Modifying the Example
Configuration File section, later in this chapter, for more information on the
configuration files.
2 Modify the example ladder logic to meet the needs of your application, and
copy the ladder logic to the processor. Example ladder logic files are provided
on the CD-ROM.
Note: If you are installing this module in an existing application, you can copy the
necessary elements from the example ladder logic into your application.
The rest of this chapter describes these steps in more detail.
Before installing and configuring the module, design the application. Determine
the number points for each data type. Review the Application Design section to
aid in application design.
It is now time to edit the DNP.CFG file to set up the module for the specific
application. Refer to the Configuration File section of this document. Download
this configuration to the module along with the associated ladder logic.
The next step in installing and configuring the module is to define whether the
block transfer or side-connect interface will be utilized. If the block transfer
interface is to be used you should be ready to connect the module to the DNP
network if the ladder logic is defined correctly. If the side-connect interface is to
be used, you must obtain the side-connect kit, which is sold separately.
ProSoft Technology, Inc. Page 21 of 172
August 23, 2007
MVI71-DNP ♦ PLC Platform Installing and Configuring the Module
DNP 3.0 Master/Slave Communication Module
If the side-connect interface is utilized, make sure the file SC_DATA.TXT on the
Compact Flash Disk contains the correct first file number. You can run the
setdnpsc.exe program to set the file number to be used with your application.
Install the module in the rack and turn on the power. Connect the terminal server
to the module's debug/configuration port and exit the program by pressing the
Esc key followed by the 'X' key. This will cause the program to exit and remain at
the operating system prompt. Run the setdnpsc.exe program with a command
line argument of the file number to use for the first file. For example, to select
N10: as the first file, enter the following:
SETDNPSC 10
The program will build the SC_DATA.TXT on the Compact Flash Disk (C: drive in
the root directory).
The next step in module setup is to define the data files to be used with the
application. If the block transfer interface is used, define the data files to hold the
user data (read and write data). Enter the ladder logic to handle the blocks
transferred between the module and the PLC. Download the program to the PLC
and test the program with the module.
If the side-connect interface is used, no ladder logic is required for data transfer.
The user data files to interface with the module must reside in contiguous order
in the processor. The first file to be used by the interface is the status/control file.
This is file number set in the SC_DATA.TXT file using the SETDNPSC.EXE
program. The following table lists the files used by the side-connect interface:
Cfg+# File # File Size Description
0 N 150
1 N Reserved
2 N 124 Error/Status and Error List data destination
3 N (960 max) Digital input data source
4 N (960 max) Digital output data source
5 N (960 max) Counter data source and destination
6 N (960 max) Analog input data source
7 N (960 max) Analog output data destination
8 N (960 max) IED digital input data destination
9 N (960 max) IED digital output data source
10 N (960 max) IED counter data destination
11 N (960 max) IED analog input data destination
12 N (960 max) IED analog output data source
13 F (240 max) DNP slave floating-point input data
14 N Reserved
15 F (240 max) DNP slave floating-point output data
16 N Reserved
Command control data starting at offset 80 (80
to 143 data area)
n is the number of read data files minus one. Each file contains up to a maximum
of 960 words.
Page 22 of 172 ProSoft Technology, Inc.
August 23, 2007
Installing and Configuring the Module MVI71-DNP ♦ PLC Platform
DNP 3.0 Master/Slave Communication Module
Special care must be taken when defining the files for the side-connect interface.
Because the module directly interacts with the PLC processor and its memory,
any errors in the configuration may cause the processor to fault and it may even
lose its configuration and program. After defining the files and populating them
with the correct data, download the program to the processor, and place the
processor in run mode. If everything is configured correctly, the module should
start its normal operation.
The module is now and ready to be used with your application. Insert the module
in the rack (with the power turned off) and attach the serial communication cable.
Download the new application to the controller and place the processor in run
mode. Download the new DNP.CFGfile to the module using a terminal emulation
program. If all the configuration parameters are set correctly and the module is
attached to a network, the module's Application LED (APP LED) should remain
off and the backplane activity LED (BP ACT) should blink very rapidly. Refer to
the Diagnostics and Trouble Shooting section if you encounter errors. Attach a
computer or terminal to Port 0 on the module and look at the status of the module
using the Configuration/Debug Menu in the module.
2.1 Module Data
All data related to the MVI71-DNP module is stored in a user defined data file. It
is the responsibility of the ladder logic programmer to construct all the data files
required by the program and to write the ladder logic required to interface to
these files.
2.1.1 Status Data
When the side-connect interface is employed in the application, the status data is
automatically transferred from the module to the first file used by the interface.
The data is placed at an offset of 0 in the file and has the following format:
Word Variable Name Description
0 Scan Counter
1 to 2 Product Name (ASCII)
3 to 4 Revision (ASCII)
5 to 6
7 to 8
9 Read Block Count
10 Write Block Count
11 Parse Block Count
Operating System
Revision (ASCII)
Production Run
Number (ASCII)
Program scan counter incremented each time the program
loop is executed.
These two words contain the product name of the module
in ASCII format.
These two words contain the product revision level of the
firmware in ASCII format.
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.
Total number of blocks transferred from the module to the
processor.
Total number of blocks transferred from the processor to
the module.
Total number of blocks parsed by the module that were
received from the processor.
ProSoft Technology, Inc. Page 23 of 172
August 23, 2007
MVI71-DNP ♦ PLC Platform Installing and Configuring the Module
DNP 3.0 Master/Slave Communication Module
Word Variable Name Description
12 Block number error
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
DNP Slave Port total
number of message
frames received by
slave
DNP Slave Port total
number of response
message frames sent
from slave
DNP Slave Port total
number of message
frames seen by slave
DNP Slave
synchronization error
count (Physical Layer
Error)
DNP Slave overrun
error count (Physical
Layer Error)
DNP Slave length error
count (Physical Layer
Error)
DNP Slave bad CRC
error (Data Link Layer
Error)
DNP Slave user data
overflow error
(Transport Layer Error)
DNP Slave sequence
error (Transport Layer
Error)
DNP Slave address
error
(Transport Layer Error)
DNP Slave Binary
Input Event count
DNP Slave Binary
Input Event count in
buffer
DNP Slave Analog
Input Event count
DNP Slave Analog
Input Event count in
buffer
DNP Slave bad
function code error
(Application Layer
Error)
Number of BTW requests that resulted in an incorrect 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.
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.
Page 24 of 172 ProSoft Technology, Inc.
August 23, 2007
Installing and Configuring the Module MVI71-DNP ♦ PLC Platform
DNP 3.0 Master/Slave Communication Module
Word Variable Name Description
28
29
30
31
32 Free MemoryLSB
33 Free MemoryMSB
DNP Slave object
unknown error
(Application Layer
Error)
DNP Slave out of
range error (Application
Layer Error)
DNP Slave message
overflow error
(Application Layer
Error)
DNP Slave multi-frame
message from DNP
Master error
(Application Layer
Error)
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.
Free memory in module
When the block transfer interface is used, the status data is placed in the
module's internal database. If this data area is transferred to the processor in the
read data area, it will be passed from the module to the processor in a normal
BTR block. The format of the data is exactly the same as shown above, but the
user determines its position. Refer to the Reference Chapter for a complete
listing of the data stored in this object.
2.1.2 User Data
When the side-connect interface is utilized, the read and write data is moved
between the module and the processor without any ladder logic. The size of the
data area and position of the data areas in the module's database is determined
by the parameters set in the configuration file.
When the block transfer interface is used, ladder logic is required to page the
data between the module and the processor. The size of the data area and
position of the data areas in the module's database is determined by the
parameters set in the configuration file.
Module data is paged up to 60 words at a time from the module to the processor.
The Ladder Logic task is responsible for placing the data received into the proper
position in the data files.
ProSoft Technology, Inc. Page 25 of 172
August 23, 2007
MVI71-DNP ♦ PLC Platform Installing and Configuring the Module
DNP 3.0 Master/Slave Communication Module
2.2 Configuration File
In order for the module to operate, a configuration file (DNP.CFG) is required.
This configuration file contains information to set the data transfer characteristics
between the module and the processor, to configure the communication
information, to establish the DNP protocol parameters and to define the
databases required to hold the protocol data sets. Each parameter in the file
must be set carefully in order for the application to be implemented successfully.
Before editing the file, design your system using the forms located in the
Reference chapter of this document.
The configuration file is separated into sections with topic header names
enclosed in the [ ] characters. The configuration file consists of the following
topics:
[Section] Description
[Module] General Module configuration section
[DNP Slave] DNP slave protocol definitions
[DNP Slave Database] Database definition for the DNP slave driver
[DNP Slave Binary Inputs]
[DNP Slave Analog Inputs]
[DNP Slave Float Inputs]
[Secondary Port]
[DNP Master] Definitions of the DNP Master port on the module if utilized
[IED Database]
[DNP Master Slave List]
[DNP Master Commands]
Class assignments for each binary input point in the DNP
database. These assignments will override the default
setting.
Class and deadband assignments for each analog input
point in the DNP database. These assignments will override
the default settings.
Class and deadband assignments for each analog floatingpoint input point in the DNP database. These assignments
will override the default settings.
Communication settings for the secondary port on the
module (secondary slave or master port)
Database definition for the DNP Master port to hold data to
interface with the IEDs.
Slave set up information for the DNP Master port. This list
contains the settings required for each IED unit the master
will interface with.
This list contains the command list to be utilized by the DNP
Master port. These commands will be issued to configured
IED units.
After each section header, the file contains a set of parameters. Unique labels
are used under each section to specify a parameter. Each label in the file must
be entered exactly as shown in the file for the parameter to be identified by the
program. If the module is not considering a parameter, look at the label for the
data item. Each parameter's value is separated from the label with the ':'
character. This character is used by the program to delimit the position in the
data record where to start reading data. All data for a parameter must be placed
after the ':' character. For numeric parameter values any text located after the
value will not be used. There must be at least one space character between the
end of the parameter value and the following text. The following example shows
a parameter entry:
Page 26 of 172 ProSoft Technology, Inc.
August 23, 2007
Installing and Configuring the Module MVI71-DNP ♦ PLC Platform
DNP 3.0 Master/Slave Communication Module
RTS On : 6 #Set RTS On delay value from 0 to 65535 milliseconds
The parameter label is "RTS On" and the parameter value is 6. The characters
after the parameter value are ignored and are used for internal documentation of
the configuration file.
Any record that begins with the '#' character is considered to be a comment
record. These records can be placed anywhere in the file as long as the '#'
character is found in the first column of the line. These lines are ignored in the file
and can be used to provide documentation within the configuration file. Liberal
use of comments within the file can ease the use and interpretation of the data in
the file.
Sections of the configuration file that contain lists of data are formatted
differently. Each list begins with the label START and ends when the END label
is reached. When entering the list data, make certain that the first character in
each line is left blank.
2.2.1 [Module]
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 [DNP 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. Another item of concern is the maximum
size of the total database, although it is possible to configure a database of
considerable size, this would not work, as the maximum Class 0 request may not
exceed 2048 bytes in size.
The following example shows a sample [DNP Slave] section:
# This section is used to define the configuration for the Module.
# port. This port will receive requests from a remote DNP master unit.
#
[DNP Slave]
Internal Slave ID : 6 #0-65534 slave identification code for this unit
# DNP slave communication port configuration
Baud Rate : 19200 #Baud rate for port 110-115200
RTS On : 0 #0-32000 mSec before message
RTS Off : 0 #0-32000 mSec after message
Min Response Delay : 0 #0-32000 mSec before response sent from slave
# DNP slave modem configuration
Modem : No #Use a dial-up modem on this port (Yes or No)
ProSoft Technology, Inc. Page 27 of 172
August 23, 2007
MVI71-DNP ♦ PLC Platform Installing and Configuring the Module
DNP 3.0 Master/Slave Communication Module
Connect Timeout : 20000 #0-65535 milliseconds before connect timeout
First Character Delay : 1000 #0-65535 milliseconds before 1st char after connect
Redial Delay Time : 100 #0-65535 1/10 seconds min before redial attempt
Redial Random Delay : 150 #0-65535 1/10 seconds random before redial attempt
Idle Timeout : 200 #0-65535 1/10 seconds inactive timeout
Phone Number : ATDT18001234567
# Collision Avoidance parameters
Collision Avoidance : No #Use Collision Avoidance (Yes or No)
CD Idle Time : 10 #0-32000 mSec min idle time before transmit
CD Random Time : 15 #0-32000 mSec random idle time before transmit
CD Time Before Receive : 5 #0-65535 milliseconds before receive
#Default Class Settings
BI Class : 1 #Default class for binary input events
AI Class : 2 #Default class for analog input events
Float Class : 3 #Default class for float input events
Double Class : 0 #(Not Used)
# DNP specific parameters
AI Deadband : 10 #0-32767 analog deadband value for events
Float Deadband : 10.0 #Single float deadband
Double Deadband : 0 #(Not Used)
Select/Operate Arm Time: 2000 #1-65535 milliseconds arm timeout for select/op
outputs
Write Time Interval : 60 #0-1440 minutes for time sync from master
Data Link Confirm Mode : Never #DL confirm mode (N=Never,S=Sometimes,A=Always)
Data Link Confirm Tout : 1000 #1-65535 milliseconds DL confirm timeout
Data Link Max Retry : 2 #0-255 maximum DL confirm retry count
App Layer Confirm Tout : 2000 #1-65535 milliseconds App Layer confirm timeout
Unsolicited Response : No #Generate Unsolicited responses (Yes or No)
Class 1 Unsol Resp Min : 2 #1-255 min number of events before send
Class 2 Unsol Resp Min : 3 #1-255 min number of events before send
Class 3 Unsol Resp Min : 4 #1-255 min number of events before send
Unsol Resp Delay : 10000 #0-65535 milliseconds before events sent
UResp Master Address : 2 #DNP address of master to send UResp data
UResp Retry Count : 0 #0-255 Number of retries before switching ports
AI Events with time : No #timestamp AI Event data default (Yes or No)
Time Sync Before Events: No #timesync module before events gen (Yes or No)
Initialize DNP Database: No #Initialize the DNP Slave output database areas (Y/N)
Modify each parameter based on the needs of your application:
Internal Slave ID
Internal Slave ID : 6 #0-65534 slave identification code for this unit
This is the DNP address for the module. All messages with this address received
from the master will be processed by the module. This example shows the slave
identification code of 6.
Page 28 of 172 ProSoft Technology, Inc.
August 23, 2007
Installing and Configuring the Module MVI71-DNP ♦ PLC Platform
DNP 3.0 Master/Slave Communication Module
Baud Rate
Baud Rate : 19200 #Baud rate for port 110-115200
Primary DNP Port Baud Rate: 300, 600, 1200, 2400, 4800, 9600, 19200, 384
(38400) , 576 (57600), 115 (115200). The module has been tested for baud rates
up to 19200.
RTS On
RTS On : 0 #0-65535 milliseconds before message
This value represents the number of 1 ms increments to be inserted between
asserting the RTS modem line and the actual transmission of the data.
RTS Off
RTS Off : 0 #0-65535 milliseconds after message
This value represents the number of 1 ms increments to be inserted after the last
character of data is transmitted before the RTS modem line is dropped.
Minimum Response Delay
Min Response Delay : 0 #0-65535 milliseconds before response sent from
slave
Minimum time between receiving a request and transmitting a response. Allows
master time to disable transmitter on an RS-485 network.
Modem
Modem : No #Use a dial-up modem on this port (Yes or No)
This parameter defines if a dial-up modem is used on the secondary DNP slave
port. A modem cannot be used if the port is configured as a master.
Connect Timeout
Connect Timeout : 20000 #0-65535 milliseconds before connect timeout
Defines the number of milliseconds to wait for the CD signal to be set high. The
CD signal indicates a connection is made using a dial-up modem.
First Character Delay
First Character Delay : 1000 #0-65535 milliseconds before 1st char after connect
Defines the number of milliseconds to wait before sending the first message after
the connection is first made. This delay only applies to the first packet sent to the
modem.
Redial Delay Time
Redial Delay Time : 100 #0-65535 1/10 seconds min before redial attempt
Defines the minimum number of milliseconds to wait before a redial attempt is
made by the slave.
ProSoft Technology, Inc. Page 29 of 172
August 23, 2007
MVI71-DNP ♦ PLC Platform Installing and Configuring the Module
DNP 3.0 Master/Slave Communication Module
Redial Random Delay
Redial Random Delay : 150 #0-65535 1/10 seconds random before redial attempt
Defines a random millisecond time range to be added to the redial delay time
before the modem is accessed.
Idle Timeout
Idle Timeout : 200 #0-65535 1/10 seconds inactive timeout
Defines the number of milliseconds the modem is inactive before it will
disconnect.
Phone Number
Phone Number : ATDT18001234567
This field contain a null-terminated, ASCII character string used by the dial-up
modem. The string must contain all characters required by the modem. An
example string is ATDT18001234567. Maximum length is 34 bytes including the
terminating 0.
Collision Avoidance
Collision Avoidance : No #Use Collision Avoidance (Yes or No)
This parameter defines if collision avoidance will be utilized on the primary DNP
slave port.
CD Idle Time
CD Idle Time : 10 #0-32000 mSec min idle time before transmit
Defines the minimum number of milliseconds to wait before transmitting a
message after the CD signal is recognized as low.
CD Random Time
CD Random Time : 15 #0-32000 mSec random idle time before transmit
Defines the range of random time to be added to the CD Idle Time before a
message will be transmitted from the slave.
CD Time Before Receive
CD Time Before Receive : 5 #0-65535 milliseconds before receive
Defines the number of milliseconds to wait before receiving characters after the
CD signal is recognized as high.
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.
Page 30 of 172 ProSoft Technology, Inc.
August 23, 2007
Loading...