ProSoft Technology InRax MVI71-DNPSNET User Manual

Download

Page 1

MVI71-DNPSNET

PLC Platform

Distributed Network Protocol Interface Module

September 22, 2008

USER MANUAL

Page 2

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.

Page 3

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

MVI71-DNPSNET User Manual September 22, 2008

ProSoft Technology ®, ProLinx ®, inRAx ®, ProTalk® and RadioLinx ® are Registered Trademarks of ProSoft Technology, Inc.

Page 4

Page 5

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

Page 6

Contents MVI71-DNPSNET ♦ PLC Platform Distributed Network Protocol Interface Module

Support, Service & Warranty 91

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

Page 7

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

Page 8

MVI71-DNPSNET ♦ PLC Platform Start Here Distributed Network Protocol Interface Module

Page 8 of 100 ProSoft Technology, Inc.

September 22, 2008

Page 9

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

Page 10

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 Cable

3 Cable

2 Adapter 1454-9F

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

Page 11

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

Page 12

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

Page 13

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

Page 14

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

Page 15

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

Page 16

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

Page 17

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

Page 18

MVI71-DNPSNET ♦ PLC Platform Start Here Distributed Network Protocol Interface Module

Page 18 of 100 ProSoft Technology, Inc.

September 22, 2008

Page 19

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

Page 20

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

Page 21

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

Page 22

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

Page 23

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

Page 24

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

Page 25

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

Page 26

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

Page 27

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

Page 28

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

Page 29

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

Page 30

MVI71-DNPSNET ♦ PLC Platform Ladder Logic Distributed Network Protocol Interface Module

Word Variable Name Description

12 Block number error

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

Page 31

Ladder Logic MVI71-DNPSNET ♦ PLC Platform Distributed Network Protocol Interface Module

Word Variable Name Description

32 Free MemoryLSB 33 Free MemoryMSB

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 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 at the location specified by the Error Offset parameter in the configuration file. 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. This will be placed in the normal read data area. 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.

3.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.

The read data area should be set to match the value entered in the Read Register Count parameter of the DNPSNET.CFG file. For ease of use, this array should be dimensioned as an even increment of 60 words. This data is paged up to 60 words at a time from the module to the processor. The Read Data task is responsible for placing the data received into the proper position in the read data array. Use this data for status and control in the ladder logic of the processor.

The write data area should be set to match the value entered in the Write Register Count parameter of the DNPSNET.CFG file. For ease of use, this array should be dimensioned as even increments of 60 words. This data is paged up to 60 words at a time from the processor to the module. The Write Data task is responsible for placing the write data into the output image for transfer to the module. This data is passed from the processor to the module for status and control information for use in other nodes on the network.

ProSoft Technology, Inc. Page 31 of 100 September 22, 2008

Page 32

MVI71-DNPSNET ♦ PLC Platform Ladder Logic Distributed Network Protocol Interface Module

Page 32 of 100 ProSoft Technology, Inc.

September 22, 2008

Page 33

Diagnostics and Troubleshooting MVI71-DNPSNET ♦ PLC Platform Distributed Network Protocol Interface Module

4 Diagnostics and Troubleshooting

In This Chapter

 Reading Status Data from the Module ..................................................33

 LED Status Indicators............................................................................ 43

The module provides information on diagnostics and troubleshooting in the following forms:

 Status data values are transferred from the module to the processor.  Data contained in the module can be viewed through the

Configuration/Debug port attached to a terminal emulator.

 LED status indicators on the front of the module provide information on the

module's status.

4.1 Reading Status Data from the Module

The MVI71-DNPSNET module returns a 34-word Status Data block that can be used to determine the module's operating status. This data can be located in the module's database at registers at the location specified in the configuration. This data is transferred to the PLC processor continuously when the side-connect interface is used.

The Configuration/Debug port provides the following functionality:

 Full view of the module's configuration data  View of the module's status data  Complete display of the module's internal database (registers 0 to 8999)  Version Information  Control over the module (warm boot and cold boot)  Facility to upload and download the module's configuration file

4.1.1 The Configuration/Debug Menu

The Configuration and Debug menu for this module is arranged as a tree structure, with the Main Menu at the top of the tree, and one or more sub-menus for each menu command. The first menu you see when you connect to the module is the Main menu.

Because this is a text-based menu system, you enter commands by typing the command letter from your computer keyboard in the terminal application (for example, HyperTerminal). The module does not respond to mouse movements or clicks. The command executes as soon as you press the command letter — you do not need to press [Enter]. When you type a command letter, a new screen will be displayed in your terminal application.

ProSoft Technology, Inc. Page 33 of 100 September 22, 2008

Page 34

MVI71-DNPSNET ♦ PLC Platform Diagnostics and Troubleshooting Distributed Network Protocol Interface Module

Navigation

All of the sub-menus for this module contain commands to redisplay the menu or return to the previous menu. You can always return from a sub-menu to the next higher menu by pressing [M] on your keyboard.

The organization of the menu structure is represented in simplified form in the following illustration:

The remainder of this section shows you the menus available for this module, and briefly discusses the commands available to you.

Keystrokes

The keyboard commands on these menus are almost always non-case sensitive. You can enter most commands in lower case or capital letters.

The menus use a few special characters ([?], [-], [+], [@]) that must be entered exactly as shown. Some of these characters will require you to use the [Shift], [Ctrl] or [Alt] keys to enter them correctly. For example, on US English keyboards, enter the [?] command as [Shift][/].

Also, take care to distinguish capital letter [I] from lower case letter [l] (L) and number [1]; likewise for capital letter [O] and number [0]. Although these characters look nearly the same on the screen, they perform different actions on the module.

4.1.2 Required Hardware

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.

 A null modem serial cable.

Page 34 of 100 ProSoft Technology, Inc.

September 22, 2008

Page 35

Diagnostics and Troubleshooting MVI71-DNPSNET ♦ PLC Platform Distributed Network Protocol Interface Module

4.1.3 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).

DOS ProComm, as well as several other terminal emulation programs Windows 3.1 Terminal Windows 95/98 HyperTerminal Windows NT/2000/XP HyperTerminal

4.1.4 Using the Configuration/Debug Port

To connect to the module's Configuration/Debug port:

1 Connect your computer to the module's port using a null modem cable. 2 Start the communication program on your computer and configure the

communication parameters with the following settings:

Baud Rate 57,600 Parity None Data Bits 8 Stop Bits 1 Software Handshaking None

3 Open the connection. When you are connected, press the [?] key on your

keyboard. If the system is set up properly, you will see a menu with the module name followed by a list of letters and the commands associated with them.

If there is no response from the module, follow these steps: 1 Verify that the null modem cable is connected properly between your

computer's serial port and the module. A regular serial cable will not work.

2 Verify that RSLinx is not controlling the COM port. Refer to Disabling the

RSLinx Driver for the Com Port on the PC (page 63).

3 Verify that your communication software is using the correct settings for baud

rate, parity and handshaking.

4 On computers with more than one serial port, verify that your communication

program is connected to the same port that is connected to the module.

If you are still not able to establish a connection, you can contact ProSoft Technology Technical Support for further assistance.

ProSoft Technology, Inc. Page 35 of 100 September 22, 2008

Page 36

MVI71-DNPSNET ♦ PLC Platform Diagnostics and Troubleshooting Distributed Network Protocol Interface Module

4.1.5 Main Menu

When you first connect to the module from your computer, your terminal screen will be blank. To activate the main menu, press the [?] key on your computer's keyboard. If the module is connected properly, the following menu will appear on your terminal screen:

Caution: Some of the commands available to you from this menu ar e designed for advanced debugging and system testing only, and can cause the module to stop communicating with the processor or with other devices, resulting in potential data loss or other failures. Only use these commands if you are specifically directed to do so by ProSoft Technology Technical Support staff. Some of these command keys are not listed on the menu, but are active nevertheless. Please be careful when pressing keys so that you do not accidentally execute an unwante d command.

Viewing Block Transfer Statistics

Press [B] from the Main Menu to view the Block Transfer Statistics screen. Use this command to display the configuration and statistics of the backplane

data transfer operations between the module and the processor. The information on this screen can help determine if there are communication problems between the processor and the module.

Tip: To determine the number of blocks transferred each second, mark the numbers displayed at a specific time. Then some seconds later activate the command again. Subtract the previous numbers from the current numbers and divide by the quantity of seconds passed between the two readings.

Viewing Module Configuration

Press [C] to view the Module Configuration screen. Use this command to display the current configuration and statistics for the

module.

Opening the Database Menu

Press [D] to open the Database View menu. Use this menu command to view the current contents of the module's database.

Page 36 of 100 ProSoft Technology, Inc.

September 22, 2008

Page 37

Diagnostics and Troubleshooting MVI71-DNPSNET ♦ PLC Platform Distributed Network Protocol Interface Module

Opening the DNP Menu

Press [I] from the Main Menu to open the DNP Menu. This menu allows you to view all data associated with the DNP Server driver. For more information about the commands on this menu, refer to DNP Menu (page 38).

Receiving the Configuration File

Press [R] to download (receive) the current configuration file from the module. For more information on receiving and sending configuration files, please see Uploading and Downloading the Configuration File (page 23).

Sending the Configuration File

Press [S] to upload (send) an updated configuration file to the module. For more information on receiving and sending configuration files, please see Uploading and Downloading the Configuration File (page 23).

Viewing Version Information

Press [V] to view Version information for the module. Use this command to view the current version of the software for the module, as

well as other important values. You may be asked to provide this information when calling for technical support on the product.

Values at the bottom of the display are important in determining module operation. The Program Scan Counter value is incremented each time a module's program cycle is complete.

Tip: Repeat this command at one-second intervals to determine the frequency of program execution.

Warm Booting the Module

Press [W] from the Main Menu to warm boot (restart) the module. This command will cause the program to exit and reload, refreshing configuration parameters that must be set on program initialization. Only use this command if you must force the module to re-boot.

Opening the Network Menu

Press [@] to open the network menu. The network menu allows you to send, receive and view the WATTCP.CFG file that contains the IP, gateway and other network specification information. You can find more information about the commands on this menu in the Network Menu (page 42) section.

ProSoft Technology, Inc. Page 37 of 100 September 22, 2008

Page 38

MVI71-DNPSNET ♦ PLC Platform Diagnostics and Troubleshooting Distributed Network Protocol Interface Module

Exiting the Program

Press [Esc] to restart the module and force all drivers to be loaded. The module will use the configuration stored in the module's Flash ROM to configure the module.

4.1.6 DNP Menu

This opens the DNP menu. After the option is selected, press the '?' key to display the menu and the following is displayed:

Each option on the menu is discussed in the following topics.

Viewing DNP Set Up & Pointers

Press [B] to display the memory allocation and the database setup parameters.

Viewing DNP Configuration

Press [C] to displays the configuration information for the server. Use this command to confirm that the module is configured as desired. If any parameter is not set correctly, adjust the configuration file and download the altered file to the unit.

Opening the DNP Database View Menu

Press [D] to open the DNP Database View menu. Use this command to display the database associated with each data type.

Viewing a List of Valid Hosts

Press [I] to view the list of IP addresses from which the module will accept connections This list is only used if the module configuration parameter, Use IP List, is set to a value other than 0.

Page 38 of 100 ProSoft Technology, Inc.

September 22, 2008

Page 39

Diagnostics and Troubleshooting MVI71-DNPSNET ♦ PLC Platform Distributed Network Protocol Interface Module

Returning to the Main Menu

Press [M] to return to the Main Menu.

Viewing DNP Communication Status

Press [1] to view DNP Communication Status. Use this command to view the communication status data for the DNP driver.

Viewing TCP Socket Status

Press [2] to view the status of the TCP socket in the module. After selecting the option, the following is displayed:

The parameters displayed have the following definitions:

Rx Count - Number of messages received on TCP socket Tx Count - Number of messages transmitted on TCP socket Tx State - 0=not transmitting, 1=transmitting TCP State - Value used for TCP/IP socket state machine Busy Flag - 0=not busy, 1=TCP has control of DNP server, 2=UDP has control

of DNP server, 3=Unsolicited message being sent

App Frame - 0=no application data frame data, 1=application data available Tx Frame - 0=Data link level frame ready to send, 1=Data link level message not

ready to send Packet Length - Length of message left to process

Viewing UDP Socket Status

Press [3] to view the status of the UDP socket in the module. After selecting the option, the following is displayed:

ProSoft Technology, Inc. Page 39 of 100 September 22, 2008

Page 40

MVI71-DNPSNET ♦ PLC Platform Diagnostics and Troubleshooting Distributed Network Protocol Interface Module

The parameters displayed have the following definitions:

Rx Count - Number of messages received on UDP socket Tx Count - Number of messages transmitted on UDP socket Tx State - 0=not transmitting, 1=transmitting TCP State - Value used for UDP/IP socket state machine Busy Flag - 0=not busy, 1=TCP has control of DNP server, 2=UDP has control

of DNP server, 3=Unsolicited message being sent

App Frame - 0=no application data frame data, 1=application data available Tx Frame - 0=Data link level frame ready to send, 1=Data link level message not

ready to send Packet Length - Length of message left to process

4.1.7 Database View Menu

Press [D] from the Main Menu to open the Database View menu. Use this menu command to view the current contents of the module's database. Press [?] to view a list of commands available on this menu.

Viewing Register Pages

To view sets of register pages, use the keys described below:

Command Description [0] [1] [2]

Display registers 0 to 99 Display registers 1000 to 1099 Display registers 2000 to 2099

And so on. The total number of register pages available to view depends on your module's configuration.

Page 40 of 100 ProSoft Technology, Inc.

September 22, 2008

Page 41

Diagnostics and Troubleshooting MVI71-DNPSNET ♦ PLC Platform Distributed Network Protocol Interface Module

Displaying the Current Page of Registers Again

This screen displays the current page of 100 registers in the database.

Moving Back Through 5 Pages of Registers

Press [-] from the Database View menu to skip back to the previous 500 registers of data.

Viewing the Previous 100 Registers of Data

Press [P] from the Database View menu to display the previous 100 registers of data.

Skipping 500 Registers of Data

Hold down [Shift] and press [=] to skip forward to the next 500 registers of data.

Viewing the Next 100 Registers of Data

Press [N] from the Database View menu to select and display the next 100 registers of data.

Viewing Data in Decimal Format

Press [D] to display the data on the current page in decimal format.

Viewing Data in Hexadecimal Format

Press [H] to display the data on the current page in hexadecimal format.

Viewing Data in Floating Point Format

Press [F] from the Database View menu. Use this command to display the data on the current page in floating point format. The program assumes that the values are aligned on even register boundaries. If floating-point values are not aligned as such, they are not displayed properly.

Viewing Data in ASCII (Text) Format

Press [A] to display the data on the current page in ASCII format. This is useful for regions of the database that contain ASCII data.

Returning to the Main Menu

Press [M] to return to the Main Menu.

ProSoft Technology, Inc. Page 41 of 100 September 22, 2008

Page 42

MVI71-DNPSNET ♦ PLC Platform Diagnostics and Troubleshooting Distributed Network Protocol Interface Module

4.1.8 Network Menu

The network menu allows you to send, receive and view the WATTCP.CFG file that contains the IP and gateway addresses, and other network specification information.

Transferring WATTCP.CFG to the module

Press [R] to transfer a new WATTCP.CFG file from the PC to the module. Use this command to change the network configuration for the module (for example, the module's IP address).

Press [Y] to confirm the file transfer, and then follow the instructions on the terminal screen to complete the file transfer process.

Transferring WATTCP.CFG to the PC

Press [S] to transfer the WATTCP.CFG file from the module to your PC. Press [Y] to confirm the file transfer, and then follow the instructions on the

terminal screen to complete the file transfer process. After the file has been successfully transferred, you can open and edit the file to

change the module's network configuration.

Viewing the WATTCP.CFG file on the module

Press [V] to view the module's WATTCP.CFG file. Use this command to confirm the module's current network settings.

Returning to the Main Menu

Press [M] to return to the Main Menu.

Page 42 of 100 ProSoft Technology, Inc.

September 22, 2008

Page 43

Diagnostics and Troubleshooting MVI71-DNPSNET ♦ PLC Platform Distributed Network Protocol Interface Module

4.2 LED Status Indicators

The LEDs indicate the module's operating status as follows:

ProSoft Module

CFG Green

BP Amber

OK Red/

If the APP, BP ACT and OK LEDs blink at a rate of every one-second, this indicates a serious problem with the module. Call ProSoft Technology support to arrange for repairs.

Color Status Indication

Off No data is being transferred on the Configuration/Debug port. On Port not used P1 Green Off Port not used On Port not used P2 Green Off Port not used Off The MVI71-DNPSNET is working normally. APP Status Amber On

Off

Green

Green The module is operating normally. Red

Off The battery voltage is OK and functioning. BAT Red On

Data is being transferred between the module and a remote terminal using the Configuration/Debug port.

The MVI71-DNPSNET module program has recognized a communication error on one of its DNP ports.

The LED is on when the module is performing a write operation on the backplane.

The LED is off when the module is performing a read operation on the backplane. Under normal operation, the LED should blink rapidly on and off.

The card is not receiving any power and is not securely plugged into the rack.

The program has detected an error or is being configured. If the LED remains red for over 10 seconds, the program has probably halted. Remove the card from the rack and re-insert the card to restart the module's program.

The battery voltage is low or battery is not present. Allow battery to charge by keeping module plugged into rack for 24 hours. If BAT LED still does not go off, contact ProSoft Technology, as this is not a user serviceable item.

In addition to these LEDs, the module contains two LEDs under the module's door. The LED on the left (green) displays the link status. If the module is connected properly to a hub, this LED should be illuminated. The LED on the right (amber) is the data indication LED. Whenever the module is sending or receiving data on the Ethernet interface, this LED is illuminated.

4.2.1 Ethernet LED Indicators

LED State Description

Off No activity on the port. Data Green Flash The port is either actively transmitting or receiving data. Off No connection to hub or network is detected. Link Green Solid

ProSoft Technology, Inc. Page 43 of 100 September 22, 2008

Connected to hub or network correctly. This is the normal operating state.

Page 44

MVI71-DNPSNET ♦ PLC Platform Diagnostics and Troubleshooting Distributed Network Protocol Interface Module

4.2.2 Clearing a Fault Condition

Typically, if the OK LED on the front of the module turns red for more than ten seconds, a hardware problem has been detected in the module, or the program has exited.

To clear the condition, follow these steps:

1 Turn off power to the rack 2 Remove the card from the rack 3 Verify that all jumpers are set correctly 4 If the module requires a Compact Flash card, verify that the card is installed

correctly

5 Re-insert the card in the rack and turn the power back on 6 Verify the configuration data being transferred to the module from the PLC

processor.

If the module's OK LED does not turn green, verify that the module is inserted completely into the rack. If this does not cure the problem, contact ProSoft Technology Support.

4.2.3 Troubleshooting

Use the following troubleshooting steps if you encounter problems when the module is powered up. If these steps do not resolve your problem, please contact ProSoft Technology Technical Support.

Processor Errors

Problem Description Steps to take

Processor Fault

Processor I/O LED flashes

Module Errors

Problem Description Steps to take

BP ACT LED remains off or blinks slowly

OK LED remains red

Verify that the module is plugged into the slot that has been configured for the module.

Verify that the slot in the rack configuration has been set up correctly in the ladder logic.

This indicates a problem with backplane communications. Verify that all modules in the rack are configured in the ladder logic.

This indicates that backplane transfer operations are failing. Connect to the module's Configuration/Debug port to check this.

To establish backplane communications, verify the following items:

 The processor is in Run mode.  The backplane driver is loaded in the module.  The module is configured for read and write block data transfer.  The ladder logic handles all read and write block situations.  The module is configured in the processor.

The program has halted or a critical error has occurred. Connect to the Configuration/Debug port to see if the module is running. If the program has halted, turn off power to the rack, remove the card from the rack and re-insert the card in the rack, and then restore power to the rack.

Page 44 of 100 ProSoft Technology, Inc.

September 22, 2008

Page 45

Diagnostics and Troubleshooting MVI71-DNPSNET ♦ PLC Platform Distributed Network Protocol Interface Module

4.2.4 Error Status Table

The program maintains an error/status table that is transferred to the processor in each read block. Ladder logic should be programmed to accept this block of data and place it in the module's controller tag. You can use the error/status data to determine the "health" of the module.

The data in the block is structured as shown in the following table.