ProSoft Technology InRax MVI71-DNPSNET User Manual
MVI71-DNPSNET
PLC Platform
Distributed Network Protocol Interface
Module
September 22, 2008
USER MANUAL
Please Read This Notice
Successful application of this module requires a reasonable working knowledge of the Rockwell Automation PLC
hardware, the MVI71-DNPSNET 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 ensure that the information provided is
accurate and a true reflection of the product's installation requirements. In order to ensure a complete understanding
of the operation of the product, the user should read all applicable Rockwell Automation documentation on the
operation of the Rockwell Automation 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.
Battery Life Advisory
All modules in the MVI series use a rechargeable Lithium Vanadium Pentoxide battery to backup the 512K SRAM
memory, 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 it becomes fully charged. After it is fully charged,
the battery provides backup power for the CMOS setup and configuration data, the real-time clock, and the 512K
SRAM memory for approximately 21 days.
Before you remove a module from its power source, ensure that the battery within the module is fully charged. A fully
charged battery will hold the BIOS settings (after being removed from its power source) for a limited number of days.
When the battery is fully discharged, the module will revert to the default BIOS settings.
Note: The battery is not user replaceable.
ProSoft® 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 and are
available at no charge from our web site: http://www.prosoft-technology.com
Printed documentation is available for purchase. Contact ProSoft Technology for pricing and availability.
Asia Pacific: +603.7724.2080
Europe, Middle East, Africa: +33.5.34.36.87.20
Latin America: +1.281.298.9109
North America: +1.661.716.5100
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 - 2008. All Rights Reserved.
MVI71-DNPSNET User Manual
September 22, 2008
ProSoft Technology ®, ProLinx ®, inRAx ®, ProTalk® and RadioLinx ® are Registered Trademarks of ProSoft
Technology, Inc.
Contents MVI71-DNPSNET ♦ PLC Platform
Distributed Network Protocol Interface Module
Contents
Please Read This Notice 2
Battery Life Advisory ...........................................................................................................................3
ProSoft® Product Documentation....................................................................................................... 3
Your Feedback Please........................................................................................................................3
Guide to the MVI71-DNPSNET User Manual 7
1 Start Here 9
1.1 System Requirements............................................................................................... 9
1.2 Package Contents................................................................................................... 10
1.3 Setting Jumpers ......................................................................................................11
1.4 Install the Module in the Rack .................................................................................12
1.5 Connect your PC to the Processor.......................................................................... 13
1.6 Download the Sample Program to the Processor................................................... 14
1.7 Connect your PC to the Module ..............................................................................17
2 Module Configuration 19
2.1 Installing and Configuring the Module..................................................................... 19
2.2 IP Address............................................................................................................... 22
2.3 Uploading and Downloading the Configuration File................................................23
3 Ladder Logic 29
3.1 Module Data ............................................................................................................29
4 Diagnostics and Troubleshooting 33
4.1 Reading Status Data from the Module.................................................................... 33
4.2 LED Status Indicators..............................................................................................43
5 Reference 47
5.1 Product Specifications.............................................................................................47
5.2 Functional Overview................................................................................................49
5.3 Cable Connections..................................................................................................62
5.4 MVI71-DNPSNET Configuration Forms.................................................................. 65
5.5 MVI71-DNPSNET Status Data................................................................................ 69
5.6 MVI71-DNPSNET Module Internal Indication Bits (IIN Bits) for DNP Server .........70
5.7 Device Profile ..........................................................................................................72
5.8 DNP Subset Definition.............................................................................................73
5.9 MVI71-DNPSNET Application Design.....................................................................76
5.10 Event Size Computation..........................................................................................88
ProSoft Technology, Inc. Page 5 of 100
September 22, 2008
Contents MVI71-DNPSNET ♦ PLC Platform
Distributed Network Protocol Interface Module
Support, Service & Warranty 91
6
6.1 How to Contact Us: Technical Support................................................................... 91
6.2 Return Material Authorization (RMA) Policies and Conditions............................... 92
6.3 LIMITED WARRANTY............................................................................................ 94
Index 99
Page 6 of 100 ProSoft Technology, Inc.
September 22, 2008
Start Here MVI71-DNPSNET ♦ PLC Platform
Distributed Network Protocol Interface Module
Guide to the MVI71-DNPSNET 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 9)
Verifying
Communication
(page 43)
Diagnostics and
Troubleshooting
(page 33)
Reference (page 47)
Functional Overview
(page 49)
Product
Specifications (page
47)
Support, Service
and Warranty (page
91)
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 7 of 100
September 22, 2008
MVI71-DNPSNET ♦ PLC Platform Start Here
Distributed Network Protocol Interface Module
Page 8 of 100 ProSoft Technology, Inc.
September 22, 2008
Start Here MVI71-DNPSNET ♦ PLC Platform Distributed Network Protocol Interface Module
1 Start Here
In This Chapter
System Requirements .............................................................................9
Package Contents .................................................................................10
Setting Jumpers ....................................................................................11
Install the Module in the Rack ...............................................................12
Connect your PC to the Processor........................................................ 13
Download the Sample Program to the Processor.................................. 14
Connect your PC to the Module ............................................................17
Installing the MVI71-DNPSNET module requires a reasonable working
knowledge of the Rockwell Automation hardware, the MVI71-DNPSNET Module
and the application in which they will be used.
Caution: It is important that those responsible for implementati on can complete the
application without exposing personnel, or equipment, to unsafe or inappropriate working
conditions. Safety, quality and experience ar e key factors in a successful installation.
1.1 System Requirements
The MVI71-DNPSNET 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-DNPSNET module. The module requires
800mA of available power.
The PLC Processor must provide for at least 64 words of BTR/BTW area,
otherwise the module may not function correctly.
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 9 of 100
September 22, 2008
MVI71-DNPSNET ♦ PLC Platform Start Here
Distributed Network Protocol Interface 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 Zmodem protocol.
1.2 Package Contents
The following components are included with your MVI71-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
1 Cable
3 Cable
2 Adapter 1454-9F
1
MVI71DNPSNET
Module
ProSoft
Solutions CD
MVI71-DNPSNET Distributed Network Protocol Interface Module
Cable #15, RS232
Null Modem
Cable #14, RJ45 to
DB9 Male Adapter
cable
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-DNPSNET module.
If any of these components are missing, please contact ProSoft Technology
Support for replacement parts.
Page 10 of 100 ProSoft Technology, Inc.
September 22, 2008
Start Here MVI71-DNPSNET ♦ PLC Platform
Distributed Network Protocol Interface Module
1.3 Setting Jumpers
Note: 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.
ProSoft Technology, Inc. Page 11 of 100
September 22, 2008
MVI71-DNPSNET ♦ PLC Platform Start Here
Distributed Network Protocol Interface Module
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-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 pla n to
connect to verify that suitable safety procedures ar e in place before installing or servicing the
device.
After you have checked the placement of the jumpers, insert MVI71-DNPSNET
into the PLC™ chassis. Use the same technique recommended by Rockwell
Automation to remove and install PLC modules.
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.
Page 12 of 100 ProSoft Technology, Inc.
September 22, 2008
Start Here MVI71-DNPSNET ♦ PLC Platform
Distributed Network Protocol Interface Module
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.
1.5 Connect your PC to the Processor
1 Connect the right-angle connector end of the cable to your controller at the
communications port.
ProSoft Technology, Inc. Page 13 of 100
September 22, 2008
MVI71-DNPSNET ♦ PLC Platform Start Here
Distributed Network Protocol Interface Module
2 Connect the straight connector end of the cable to the serial port on your
computer.
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.
Page 14 of 100 ProSoft Technology, Inc.
September 22, 2008
Start Here MVI71-DNPSNET ♦ PLC Platform
Distributed Network Protocol Interface Module
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.
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.
ProSoft Technology, Inc. Page 15 of 100
September 22, 2008
MVI71-DNPSNET ♦ PLC Platform Start Here
Distributed Network Protocol Interface Module
This action opens the Configure Drivers dialog box.
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 driv er 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.
Page 16 of 100 ProSoft Technology, Inc.
September 22, 2008
Start Here MVI71-DNPSNET ♦ PLC Platform
Distributed Network Protocol Interface Module
Note: If the auto-configuration procedure fails, verify that the cables are connected correct ly
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 yo ur RSLinx documentation for further troubleshooting
steps.
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 17 of 100
September 22, 2008
MVI71-DNPSNET ♦ PLC Platform Start Here
Distributed Network Protocol Interface Module
Page 18 of 100 ProSoft Technology, Inc.
September 22, 2008
Module Configuration MVI71-DNPSNET ♦ PLC Platform Distributed Network Protocol Interface Module
2 Module Configuration
In This Chapter
Installing and Configuring the Module ...................................................19
IP Address.............................................................................................22
Uploading and Downloading the Configuration File............................... 23
In order for the MVI71-DNPSNET module to function, a minimum amount of
configuration data must be transferred to the module. A text file named
DNPSNET.CFG is shipped with the module. This file can serve as a starting
point to develop a user application. Edit the file to configure the module for the
application.
A terminal server program is used to upload and download the configuration file
to the module. An additional file, WATTCP.CFG, must be configured for the
specific network on which the module resides.
2.1 Installing and Configuring the Module
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 existin g 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 DNPSNET.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.
ProSoft Technology, Inc. Page 19 of 100
September 22, 2008
MVI71-DNPSNET ♦ PLC Platform Module Configuration
Distributed Network Protocol Interface Module
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
Ethernet 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.
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).
Next, 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:
File Number Example Size Description
Cfg File N10 100 Control/Status File
Cfg File+1 N11 to 1000 Data transferred from the module to the processor
Other files for read data
Cfg File+1+n N12 to 1000 Data transferred from the processor to the module
Cfg File+1+n+m Other files for write data
n is the number of read data files minus one. Each file contains up to 1000
words.
m is the number of write data files minus one. Each file contains up to 1000
words.
More than one read and/or write file may exist in an application. This is required
when more than 1000 words of data are required. Two examples are given for
the files used with different data set sizes:
Page 20 of 100 ProSoft Technology, Inc.
September 22, 2008
Module Configuration MVI71-DNPSNET ♦ PLC Platform
Distributed Network Protocol Interface Module
2.1.1 Example of 240 words of read and write data (cfg file=10)
Data Files Description
N11:0 to 239 Read data
N12:0 to 239 Write data
Example of 2300 read and 3500 write data registers (cfg file=10)
Data Files Description
N11:0 to 999 Read data words 0 to 999
N12:0 to 999 Read data words 1000 to 1999
N13:0 to 299 Read data words 2000 to 2299
N14:0 to 999 Write data words 0 to 999
N15:0 to 999 Write data words 1000 to 1999
N16:0 to 999 Write data words 2000 to 2999
N17:0 to 499 Write data words 3000 to 3499
Even if the files are not required for an application, they still are reserved and
should only be used for that purpose. The read and write data contained in the
last set of files possess the data transferred between the module and the
processor. The read data file (Cfg File + 1) will contain data transferred from the
module to the processor and should be associated with control data types. The
write data file (Cfg File + 1 + n) will contain data passed to the module from the
processor and should be associated with monitor data types.
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 DNPSNET.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.
ProSoft Technology, Inc. Page 21 of 100
September 22, 2008
MVI71-DNPSNET ♦ PLC Platform Module Configuration
Distributed Network Protocol Interface Module
2.2 IP Address
In addition to the DNPSNET.CFG, the MVI71-DNPSNET module requires a
second configuration file that identifies its Ethernet configuration. Without this
configuration file, the module will not communicate properly on the network.
This file contains the Ethernet address information to be used by the module and
may be transferred to and from the module from the Network command
available on the debug port of the module. Please consult your network
administrator for the correct settings for your network before placing this or any
other Ethernet TCP/IP device upon your network.
Important: If the field "my_ip" does not exist, or if the wattcp.cfg file is corrupted or does not exist,
the module will not function.
To set the Module's IP Address
1 Locate the sample configuration files for your module on the ProSoft
Solutions CD.
2 Copy the configuration files and ladder to a location on your PC's hard drive.
We recommend C:\temp.
3 After you move the files, right-click on each of the files, choose Properties,
and clear the READ ONLY check box.
4 Start Notepad.exe, or any other editor that can save plain text files.
5 Open the file WATTCP.CFG. The following example shows the contents of a
typical WATTCP.CFG file.
# ProSoft Technology
# Default private class 3 address
my_ip=192.168.0.100
# Default class 3 network mask
netmask=255.255.255.0
# The gateway I wish to use
gateway=192.168.0.1,192.168.0.0,255.255.255.0
6 Edit the file, using the IP addresses supplied by your network administrator.
Important: The module does not support DHCP (Dynamic Host Configuration Protocol) for
obtaining an IP address from a server. This module must have its own static IP address that does
not duplicate the IP address of any other device on the Ethernet netw ork.
7 Save the file as WATTCP.CFG. You must now transfer the file to the module.
Refer to Transferring WATTCP.CFG to the module (page 26, page 42) for the
correct procedure.
Page 22 of 100 ProSoft Technology, Inc.
September 22, 2008
Module Configuration MVI71-DNPSNET ♦ PLC Platform
Distributed Network Protocol Interface Module
2.3 Uploading and Downloading the Configuration File
ProSoft modules are shipped with a pre-loaded configuration file. In order to edit
this file, you must transfer the file from the module to your PC. After editing, you
must transfer the file back to the module.
This section describes these procedures.
Important: The illustrations of configuration/debug menus in this section are intended as a general
guide, and may not exactly match the configuration/debug menus in your own module. For specific
information about the configuration/debug menus in your module, refer to The Configuration/Debug
Menu (page 33).
2.3.1 Required Hardware
You can connect directly from your computer's serial port to the serial port on the
module to view configuration information, perform maintenance, and send
(upload) or receive (download) configuration files.
ProSoft Technology recommends the following minimum hardware to connect
your computer to the module:
80486 based processor (Pentium preferred)
1 megabyte of memory
At least one UART hardware-based serial communications port available.
USB-based virtual UART systems (USB to serial port adapters) often do not
function reliably, especially during binary file transfers, such as when
uploading/downloading configuration files or module firmware upgrades.
A null modem serial cable.
2.3.2 Required Software
In order to send and receive data over the serial port (COM port) on your
computer to the module, you must use a communication program (terminal
emulator).
A simple communication program called HyperTerminal is pre-installed with
recent versions of Microsoft Windows operating systems. If you are connecting
from a machine running DOS, you must obtain and install a compatible
communication program. The following table lists communication programs that
have been tested by ProSoft Technology.
DOS ProComm, as well as several other terminal emulation programs
Windows 3.1 Terminal
Windows 95/98 HyperTerminal
Windows NT/2000/XP HyperTerminal
The module uses the Zmodem file transfer protocol to send (upload) and receive
(download) configuration files from your module. If you use a communication
program that is not on the list above, please be sure that it supports Zmodem file
transfers.
ProSoft Technology, Inc. Page 23 of 100
September 22, 2008
MVI71-DNPSNET ♦ PLC Platform Module Configuration
Distributed Network Protocol Interface Module
2.3.3 Transferring the Configuration File to Your PC
1 Connect your PC to the Configuration/Debug port of the module using a
terminal program such as HyperTerminal. Press [?] to display the main
menu.
2 From the Transfer menu in HyperTerminal, select Receive File.
3 In the Receive File dialog box, browse to the location on your PC where the
configuration file should be stored, and select Zmodem (or Zmodem with
Crash Recovery) as the receiving protocol.
When you have completed your selections, click Close.
Page 24 of 100 ProSoft Technology, Inc.
September 22, 2008
Module Configuration MVI71-DNPSNET ♦ PLC Platform
Distributed Network Protocol Interface Module
4 Press [S] (Send Module Configuration), and then press [Y] to confirm the
transfer.
The file transfer will then begin automatically, using the protocol and location
you specified in Step 3.
When the configuration file has been transferred to your PC, the dialog box
will indicate that the transfer is complete.
The configuration file is now on your PC at the location you specified.
5 You can now open and edit the file in a text editor such as Notepad. When
you have finished editing the file, save it and close Notepad.
ProSoft Technology, Inc. Page 25 of 100
September 22, 2008
MVI71-DNPSNET ♦ PLC Platform Module Configuration
Distributed Network Protocol Interface Module
2.3.4 Transferring the Configuration File to the Module
Perform the following steps to transfer a configuration file from your PC to the
module.
1 Connect your PC to the Configuration/Debug port of the module using a
terminal program such as HyperTerminal. Press [?] to display the main
menu.
2 Press [R] (Receive Module Configuration). The message "Press Y key to
confirm configuration receive!" is displayed at the bottom of the screen.
3 Press [Y]. The screen now indicates that the PC is ready to send.
Page 26 of 100 ProSoft Technology, Inc.
September 22, 2008
Module Configuration MVI71-DNPSNET ♦ PLC Platform
Distributed Network Protocol Interface Module
4 From the Transfer menu in HyperTerminal, select Send File.
The Send File dialog appears.
5 Use the Browse button to locate the configuration file your computer.
Note: This procedure assumes that you are uploading a newly edited configuration file from your
PC to the module. However, configuration files ar e also available on the ProSoft CD as well as the
ProSoft Technology web site.
6 Select Zmodem as the protocol.
ProSoft Technology, Inc. Page 27 of 100
September 22, 2008
MVI71-DNPSNET ♦ PLC Platform Module Configuration
Distributed Network Protocol Interface Module
7 Click the Send button. This action opens the Zmodem File Send dialog box.
When the upload is complete, the screen indicates that the module has
reloaded program values and displays information about the module.
8 Your module now contains the new configuration.
Page 28 of 100 ProSoft Technology, Inc.
September 22, 2008
Ladder Logic MVI71-DNPSNET ♦ PLC Platform Distributed Network Protocol Interface Module
3 Ladder Logic
In This Chapter
Module Data .......................................................................................... 29
Ladder logic is required for application of the MVI71-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.
3.1 Module Data
All data related to the MVI71-DNPSNET 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.
3.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 29 of 100
September 22, 2008
MVI71-DNPSNET ♦ PLC Platform Ladder Logic
Distributed Network Protocol Interface Module
Word Variable Name Description
12 Block number error
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
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)
DNP Slave object
unknown 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.
This value counts the number of times a request for an
unsupported object is received by the slave device.
Page 30 of 100 ProSoft Technology, Inc.
September 22, 2008
Loading...