0% found this document useful (0 votes)

115 views133 pages

User Manual: Mvi56E-Dnpnet

Uploaded by

Juan K Peña

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

115 views133 pages

User Manual: Mvi56E-Dnpnet

Uploaded by

Juan K Peña

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 133

USER MANUAL

MVI56E-DNPNET
DNP3 Ethernet Module for ControlLogix®

July 2, 2020
MVI56E-DNPNET

Your Feedback Please

We always want you to feel that you made the right decision to use our products. If you have suggestions,
comments, compliments or complaints about our products, documentation, or support, please write or call us.

How to Contact Us
ProSoft Technology, Inc.
+1 (661) 716-5100
+1 (661) 716-5101 (Fax)
www.prosoft-technology.com
[email protected]

MVI56E-DNPNET User Manual

July 2, 2020

ProSoft Technology®, is a registered copyright of ProSoft Technology, Inc. All other brand or product names are
or may be trademarks of, and are used to identify products and services of, their respective owners.
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 at our
website: http://www.prosoft-technology.com

Content Disclaimer
This documentation is not intended as a substitute for and is not to be used for determining suitability or reliability
of these products for specific user applications. It is the duty of any such user or integrator to perform the
appropriate and complete risk analysis, evaluation and testing of the products with respect to the relevant
specific application or use thereof. Neither ProSoft Technology nor any of its affiliates or subsidiaries shall be
responsible or liable for misuse of the information contained herein. Information in this document including
illustrations, specifications and dimensions may contain technical inaccuracies or typographical errors. ProSoft
Technology makes no warranty or representation as to its accuracy and assumes no liability for and reserves the
right to correct such inaccuracies or errors at any time without notice. If you have any suggestions for
improvements or amendments or have found errors in this publication, please notify us.
No part of this document may be reproduced in any form or by any means, electronic or mechanical, including
photocopying, without express written permission of ProSoft Technology. All pertinent state, regional, and local
safety regulations must be observed when installing and using this product. For reasons of safety and to help
ensure compliance with documented system data, only the manufacturer should perform repairs to components.
When devices are used for applications with technical safety requirements, the relevant instructions must be
followed. Failure to use ProSoft Technology software or approved software with our hardware products may
result in injury, harm, or improper operating results. Failure to observe this information can result in injury or
equipment damage.
Copyright © 2020 ProSoft Technology, Inc. All Rights Reserved.

For professional users in the European Union

If you wish to discard electrical and electronic equipment (EEE), please contact your dealer or
supplier for further information.

Warning – Cancer and Reproductive Harm – www.P65Warnings.ca.gov

Agency Approvals and Certifications

Please visit our website: www.prosoft-technology.com

ProSoft Technology, Inc. Page 2 of 133

MVI56E-DNPNET

Important Safety Information

North America Warnings

A This Equipment is Suitable For Use in Class I, Division 2, Groups A, B, C, D or Non-Hazardous Locations
Only.
B Warning – Explosion Hazard – Substitution of Any Components May Impair Suitability for Class I, Division 2.
C Warning – Explosion Hazard – Do Not Disconnect Equipment Unless Power Has Been Switched Off Or The
Area is Known To Be Non-Hazardous.
D The subject devices are powered by a Switch Model Power Supply (SMPS) that has regulated output
voltage of 5 VDC.

ATEX/IECEx Warnings and Conditions of Safe Usage:

Power, Input, and Output (I/O) wiring must be in accordance with the authority having jurisdiction.
A Warning - Explosion Hazard - When in hazardous locations, turn off power before replacing or wiring
modules.
B Warning - Explosion Hazard - Do not disconnect equipment unless power has been switched off or the area
is known to be non-hazardous.
C These products are intended to be mounted in an ATEX/IECEx Certified, tool-secured, IP54 enclosure. The
devices shall provide external means to prevent the rated voltage being exceeded by transient disturbances
of more than 40%. This device must be used only with ATEX certified backplanes.
D Before operating the reset switch, be sure the area is known to be non-hazardous.
E If the equipment is used in a manner not specified by the manufacturer, the protection provided by the
equipment may be impaired.

ProSoft Technology, Inc. Page 3 of 133

MVI56E-DNPNET

Contents
How to Contact Us ............................................................................................................................. 2
Content Disclaimer ............................................................................................................................ 2
Important Safety Information ............................................................................................................. 3

1 Start Here 6
1.1 System Requirements ............................................................................................. 6
1.2 Package Contents ................................................................................................... 7
1.3 Setting Jumpers ....................................................................................................... 7
1.4 Installing the Module in the Rack ............................................................................. 8
1.5 Creating a New RSLogix 5000 Project .................................................................... 9
1.5.1 Before You Import the Add-On Instruction ............................................................ 10
1.5.2 Creating the Module .............................................................................................. 10
1.5.3 Importing the Add-On Instruction ........................................................................... 13
1.5.4 Adding Multiple Modules (Optional) ....................................................................... 16
1.6 Downloading the Sample Program to the Processor............................................. 20

2 MVI56E-DNPNET Configuration 21
2.1 Assigning a Permanent IP Address ....................................................................... 21
2.2 DNPNET Module User-Defined Data Types ......................................................... 21
2.3 DNPNET Controller Tags Definitions .................................................................... 22
2.3.1 DNPNET Controller Tag Overview ........................................................................ 22
2.3.2 DNPNET.CONFIG.DNP_Module_Name ............................................................... 23
2.3.3 DNPNET.CONFIG.DNP3_Server .......................................................................... 23
2.3.4 DNPNET.CONFIG.DNP3_WhiteList[x] .................................................................. 26
2.3.5 DNPNET.CONFIG.DNP3_Client ........................................................................... 27
2.3.6 DNPNET.CONFIG.DNP_Server_Override ............................................................ 28
2.3.7 DNPNET.CONFIG.DNP_Server_List[x] ................................................................ 31
2.3.8 DNPNET.CONFIG.DNP_Client_Commands[x] ..................................................... 33
2.3.9 DNPNET.CONFIG.IP_Settings[x] .......................................................................... 35

3 Diagnostics and Troubleshooting 36

3.1 Ethernet LED Indicators ......................................................................................... 36
3.1.1 Scrolling LED Status Indicators ............................................................................. 37
3.1.2 Non-Scrolling LED Status Indicators ..................................................................... 38
3.2 Clearing a Fault Condition ..................................................................................... 38
3.3 Troubleshooting ..................................................................................................... 39
3.4 Setting Up ProSoft Configuration Builder .............................................................. 40
3.4.1 Installing ProSoft Configuration Builder ................................................................. 40
3.4.2 Setting Up the Project ............................................................................................ 41
3.5 Connecting Your PC to the Module ....................................................................... 43
3.5.1 Using CIPconnect® to Connect to the Module ....................................................... 43
3.5.2 Using RSWho to Connect to the Module ............................................................... 53
3.5.3 Connecting Your PC to the Module's Ethernet Port .............................................. 54
3.6 Using the Diagnostics Menu in ProSoft Configuration Builder .............................. 54
3.6.1 The Diagnostics Menu ........................................................................................... 57
3.6.2 Monitoring General Information ............................................................................. 57
3.6.3 Monitoring Backplane Information ......................................................................... 57
3.6.4 DNP3 Ethernet Point Count Module Information ................................................... 58
3.6.5 Monitoring MVI56E-DNPNET Information ............................................................. 59

ProSoft Technology, Inc. Page 4 of 133

MVI56E-DNPNET

3.6.6 Monitoring MVI56E-DNPNET Client Information ...................................................59

3.6.7 Monitoring MVI56E-DNPNET Class Assignments Information .............................60
3.6.8 Monitoring MVI56E-DNPNET Deadband Assignments Information .....................60
3.6.9 Monitoring DNP3 Ethernet Data Values .................................................................61
3.7 Communication Error Codes ..................................................................................61
3.7.1 General Command Errors ......................................................................................61
3.7.2 Slave Port Communication Errors ..........................................................................62
3.7.3 System Configuration Errors ..................................................................................63
3.7.4 Port Configuration Errors........................................................................................64
3.7.5 Application Layer Errors .........................................................................................65
3.8 Connect to the MVI56E-DNPNET Webpage..........................................................66

4 Reference 67
4.1 Product Specifications ............................................................................................67
4.1.1 General Specifications ...........................................................................................67
4.1.2 Functional Specifications........................................................................................69
4.1.3 Hardware Specifications.........................................................................................70
4.2 Functional Overview ...............................................................................................70
4.2.1 MVI56E-DNPNET Backplane Data Exchange .......................................................70
4.2.2 Function Blocks ......................................................................................................76
4.2.3 Module Function Blocks .........................................................................................77
4.2.4 Special Function Blocks .........................................................................................81
4.3 MVI56E-DNPNET Database Overview ..................................................................99
4.3.1 Normal Data Transfer ...........................................................................................100
4.3.2 DNPNETModuleDef Object ..................................................................................105
4.3.3 DNPNETCONFIG Object .....................................................................................105
4.3.4 DNPNETCONTROL Object..................................................................................106
4.3.5 DNPNETDATA Object..........................................................................................108
4.3.6 DNPNETSTATUS Object .....................................................................................108
4.3.7 DNPNETUTIL Object ...........................................................................................109
4.4 MVI56E-DNPNET User Defined Data Types .......................................................110
4.4.1 DNPNET.CONFIG Controller Tags ......................................................................111
4.4.2 DNPNET.CONFIG.Override Controller Tags .......................................................111
4.4.3 DNPNET.DATA Controller Tags ..........................................................................112
4.4.4 DNPNET.STATUS Controller Tags ......................................................................113
4.4.5 DNPNET.CONTROL Controller Tags ..................................................................113
4.4.6 DNPNET.UTIL Controller Tags ............................................................................115
4.5 Cable Connections ...............................................................................................116
4.5.1 Ethernet Cable Specifications ..............................................................................116
4.5.2 Ethernet Cable Configuration ...............................................................................116
4.5.3 Ethernet Performance ..........................................................................................116

5 Support, Service & Warranty 131

5.1 Contacting Technical Support ..............................................................................131
5.2 Warranty Information ............................................................................................131

6 Index 132

ProSoft Technology, Inc. Page 5 of 133

Start Here MVI56E-DNPNET
User Manual DNP3 Ethernet

1 Start Here
To get the most benefit from this User Manual, you should have the following
skills:
 Rockwell Automation® RSLogix™ software: launch the program, configure
ladder logic, and transfer the ladder logic to the processor
 Microsoft Windows®: install and launch programs, execute menu
commands, navigate dialog boxes, and enter data
 Hardware installation and wiring: install the module, and safely connect
DNP3 Ethernet and ControlLogix devices to a power source and to the
MVI56E-DNPNET’s application port(s)

1.1 System Requirements

The MVI56E-DNPNET module requires the following minimum hardware and
software components:
 Rockwell Automation® ControlLogix® processor (firmware version 10 or
higher) with compatible limited voltage power supply and one free slot in the
rack for the MVI56E-DNPNET module. The module requires 800 mA of
available 5 VDC and 3 mA of available 24 VDC power.

 Rockwell Automation RSLogix™ 5000 programming software

o Version 16 or higher required for Add-On Instruction
 Rockwell Automation RSLinx® communication software version 2.51 or higher
 ProSoft Configuration Builder (PCB)
 ProSoft Discovery Service (PDS)

Note: The Hardware and Operating System requirements in this list are the minimum
recommended to install and run software provided by ProSoft Technology®. Other third party
applications may have different minimum requirements. Refer to the documentation for any third
party applications for system requirements.

Note: You can install the module in a local or remote rack. For remote rack installation, the module
requires EtherNet/IP or ControlNet communication with the processor.
MVI56E-DNPNET

1.2 Package Contents

Qty. Part Name Part Number Part Description

1 MVI56E-DNPNET MVI56E-DNPNET DNPNET Ethernet Client/Server
Communication Module

1.3 Setting Jumpers

The Setup Jumper acts as "write protection" for the module’s firmware. In "write
protected" mode, the Setup pins are not connected, and the module’s firmware
cannot be overwritten. The module is shipped with the Setup jumper OFF. Do not
jumper the Setup pins together unless you are directed to do so by ProSoft
Technical Support (or you want to update the module firmware).
The following illustration shows the MVI56E-DNPNET jumper configuration with
the Setup Jumper OFF.

Note: If you are installing the module in a remote rack, you may prefer to leave the Setup pins
jumpered. That way, you can update the module’s firmware without requiring physical access to
the module.

ProSoft Technology, Inc. Page 7 of 133

MVI56E-DNPNET

1.4 Installing the Module in the Rack

Make sure your ControlLogix processor and power supply are installed and
configured, before installing the MVI56E-DNPNET. Refer to your Rockwell
Automation product documentation for installation instructions.

Warning: You must follow all safety instructions when installing this or any other electronic
devices. Failure to follow safety procedures could result in damage to hardware or data, or even
serious injury or death to personnel. Refer to the documentation for each device you plan to
connect to verify that suitable safety procedures are in place before installing or servicing the
device.

After you have checked the placement of the jumpers, insert the MVI56E-
DNPNET into the ControlLogix chassis. Use the same technique recommended
by Rockwell Automation to remove and install ControlLogix modules.
You can install or remove ControlLogix system components while chassis power
is applied and the system is operating. However, please note the following
warning.

Warning: When you insert or remove the module while backplane power is on, an electrical arc
can occur. An electrical arc can cause personal injury or property damage by sending an
erroneous signal to the system’s actuators. This can cause unintended machine motion or loss of
process control. Electrical arcs may also cause an explosion when they happen in a hazardous
environment. Verify that power is removed or the area is non-hazardous before proceeding.

Repeated electrical arcing causes excessive wear to contacts on both the module and its mating
connector. Worn contacts may create electrical resistance that can affect module operation.

1 Align the module with the top and bottom guides, and then slide it into the
rack until the module is firmly against the backplane connector.

2 With a firm, steady push, snap the module into place.

3 Check that the holding clips on the top and bottom of the module are securely
in the locking holes of the rack.

ProSoft Technology, Inc. Page 8 of 133

MVI56E-DNPNET

4 Make a note of the slot location. You must identify the slot in which the
module is installed in order for the sample program to work correctly. Slot
numbers are identified on the green circuit board (backplane) of the
ControlLogix rack.
5 Turn power ON.

Note: If you insert the module improperly, the system may stop working or may behave
unpredictably.

Note: When using the XT version (if applicable), you must use the 1756-A5XT or 1756-A7LXT
chassis to uphold the XT specifications. In these chassis, modules are spaced further apart than in
standard ControlLogix chassis. Blank spacers are inserted between active modules.

1.5 Creating a New RSLogix 5000 Project

1 Open the FILE menu, and then choose NEW.

2 Select your ControlLogix controller model.

3 Select the REVISION of your controller. Depending on the revision, there may
be some small differences in the appearance of dialog boxes from the ones
shown.
4 Enter a name for your controller, such as My_Controller.
5 Select your ControlLogix chassis type.
6 Select SLOT 0 for the controller.
7 Click OK.

ProSoft Technology, Inc. Page 9 of 133

MVI56E-DNPNET

1.5.1 Before You Import the Add-On Instruction

One Add-On Instruction is provided for the MVI56E-DNPNET module. It is
required for setting up the module.
Download the files from www.prosoft-technology.com. Save them to a convenient
location in your PC, such as Desktop or My Documents.

File Name Description

Example: L5X file containing Add-On Instruction, user defined
MVI56(E)DNPNET_AddOn_Rung_vX.L5X data types, controller tags and ladder logic required
to configure the MVI56E-DNPNET module

1.5.2 Creating the Module

Add the MVI56E-DNPNET module to the project.
1 In the Controller Organizer window, right-click I/O CONFIGURATION or the
backplane and then choose NEW MODULE...

This action opens the SELECT MODULE dialog box. Enter generic in the text
box and select the GENERIC 1756 MODULE. If you're using a controller
revision of 15 or less, expand OTHER in the SELECT MODULE dialog box,
and then select the GENERIC 1756 MODULE.

ProSoft Technology, Inc. Page 10 of 133

MVI56E-DNPNET

2 Click CREATE. This action opens the NEW MODULE dialog box.

3 In the NEW MODULE dialog box, enter the following values.

Parameter Value
NAME DNPNET
DESCRIPTION Enter a description for the module. Example: DNPNET
Ethernet Client/Server Communication Module
COMM FORMAT Select DATA-INT
SLOT Enter the slot number in the rack where the MVI56E-DNPNET
module is located
INPUT ASSEMBLY INSTANCE 1
INPUT SIZE 250
OUTPUT ASSEMBLY INSTANCE 2
OUTPUT SIZE 248
CONFIGURATION ASSEMBLY INSTANCE 4
CONFIGURATION SIZE 0

4 Click OK to continue.
5 Edit the Module Properties.
6 Select the REQUESTED PACKET INTERVAl value for scanning the I/O on the
module. This value represents the minimum frequency at which the module
will handle scheduled events. This value should not be set to less than 1
millisecond. The default value is 5 milliseconds. Values between 1 and 10
milliseconds should work with most applications.

ProSoft Technology, Inc. Page 11 of 133

MVI56E-DNPNET

7 Click OK to save the module and close the dialog box. Notice that the module
now appears in the Controller Organizer window.

ProSoft Technology, Inc. Page 12 of 133

MVI56E-DNPNET

1.5.3 Importing the Add-On Instruction

1 In the CONTROLLER ORGANIZATION window, expand the TASKS folder and
subfolders until you reach the MAINPROGRAM folder.
2 In the MAINPROGRAM folder, double-click to open the MAINROUTINE ladder.
3 Select an empty rung in the routine, and then click the right mouse button to
open a shortcut menu. On the shortcut menu, choose IMPORT RUNGS…

4 Navigate to the location on your PC where you saved the Add-On Instruction
(for example, My Documents or Desktop). Select the
MVI56(E)DNPNET_ADDON_RUNG_VX.L5X file.

ProSoft Technology, Inc. Page 13 of 133

MVI56E-DNPNET

This action opens the IMPORT CONFIGURATION dialog box. Click TAGS under
MAINROUTINE to show the controller tags that will be created.

Note that if you are using a controller revision number of 16 or less, the
IMPORT CONFIGURATION dialog box does not show the IMPORT CONTENT
tree.

Note that if you are using a controller revision number of 16 or less, the
IMPORT CONFIGURATION dialog box does not show the IMPORT CONTENT tree.

5 If you are using the module in a different slot (or remote rack), edit the
connection input and output variables that define the path to the module. Edit
the text in the FINAL NAME column (NAME column for controller revision 16 or
less). For example, if your module is located in slot 3, change Local:1:I in the
above picture to Local:3:I. Do the same for Local:1:O. If your module is
located in Slot 1 of the local rack, this step is not required.
6 Click OK to confirm the import. RSLogix 5000 indicates that the import is in
progress:

ProSoft Technology, Inc. Page 14 of 133

MVI56E-DNPNET

When the import is completed, the new rung with the Add-On Instruction will
be visible as shown in the following illustration.

The procedure also imports new User Defined Data Types, Controller Tags,
and the Add-On instruction for your project.

7 Save the application and then download the sample ladder logic into the
processor.

ProSoft Technology, Inc. Page 15 of 133

MVI56E-DNPNET

1.5.4 Adding Multiple Modules (Optional)

Important: If your application requires more than one MVI56E-DNPNET module in the same
project, follow the steps below.

1 In the I/O CONFIGURATION folder, click the right mouse button to open a
shortcut menu, and then choose NEW MODULE.

2 Select 1756-MODULE. If you're using a controller revision of 16 or less,

expand OTHER in the SELECT MODULE dialog box, and then select the 1756-
MODULE.

ProSoft Technology, Inc. Page 16 of 133

MVI56E-DNPNET

3 Fill the module properties as follows:

Parameter Value
NAME Enter a module identification string. Example: DNPNET_2.
DESCRIPTION Enter a description for the module. Example: DNPNET
Ethernet Client/Server Communication Module.
COMM FORMAT Select DATA-INT.
SLOT Enter the slot number in the rack where the MVI56E-DNPNET
module is located.
INPUT ASSEMBLY INSTANCE 1
INPUT SIZE 250
OUTPUT ASSEMBLY INSTANCE 2
OUTPUT SIZE 248
CONFIGURATION ASSEMBLY INSTANCE 4
CONFIGURATION SIZE 0

4 Click OK to confirm. The new module is now visible:

1.6 Downloading the Sample Program to the Processor

Note: The key switch on the front of the ControlLogix processor must be in the REM or PROG
position.

1 If you are not already online with the processor, in RSLogix 5000 open the
Communications menu, and then choose DOWNLOAD. RSLogix 5000 will
establish communication with the processor. You do not have to download
through the processor's serial port, as shown here. You may download
through any available network connection.
2 When communication is established, RSLogix 5000 opens a confirmation
dialog box. Click the DOWNLOAD button to transfer the sample program to the
processor.

3 RSLogix 5000 will compile the program and transfer it to the processor. This
process may take a few minutes.
4 When the download is complete, RSLogix 5000 will open another
confirmation dialog box. If the key switch is in the REM position, click OK to
switch the processor from PROGRAM mode to RUN mode.

Note: If you receive an error message during these steps, refer to your RSLogix documentation to
interpret and correct the error.

ProSoft Technology, Inc. Page 20 of 133

MVI56E-DNPNET

2 MVI56E-DNPNET Configuration
The DNP3 Ethernet configuration resides in the DNPNET controller tags. This
section covers the tag structure and descriptions of the DNPNET Client and
Server parameters.

2.1 Assigning a Permanent IP Address

The module’s IP address, subnet mask, and gateway parameters are configured
in the DNPNET.CONFIG.IP_Settings controller tags only.

Any changes to the DNPNET.CONFIG.IP_Settings.IP, Netmask, or Gateway

tags require the trigger of the DNPNET.CONFIG.IP_Settings.Write tag. This
sends the parameters to the module.
You can also read the current IP settings from the module by triggering the
DNPNET.CONFIG.IP_Settings.Read tag. They will populate in the
DNPNET.CONFIG.IP_Settings.IP, Netmask, and Gateway tags.

2.2 DNPNET Module User-Defined Data Types

The sample ladder logic relies heavily on the use of User-Defined Data Types
(UDTs) to help group and structure the wide variety and volume of data and
control features the module offers. Lower-order UDT structures are often
embedded in higher-order structures to help further organize data into more
easily understood data collections.
All data and control parameters related to the MVI56E-DNPNET are contained in
User-defined Data Types (UDTs). The DNPNETMODULEDEF UDT is the
primary, top level data structure in which all other lower-order data types are
grouped and organized. All groups branch down from this UDT.
To utilize all the features and functions of the module, an instance of each data
type is required. This is accomplished by declaring controller tag variables using
these data types in the Controller Tags Edit Tags dialog box.

ProSoft Technology, Inc. Page 21 of 133

MVI56E-DNPNET

Some UDTs hold process or status data (Module Data Objects). This data can be
monitored and manipulated by the application-specific ladder logic program.
Other UDTs are used to store and organize the parameters needed for special
functions and control features (Special Data Objects). These data types will be
discussed in more detail in succeeding topics.

2.3 DNPNET Controller Tags Definitions

2.3.1 DNPNET Controller Tag Overview

Name Description
DNPNET.CONFIG Configuration information
DNPNET.DATA DNPNET input and output data transferred between the processor and
the module
DNPNET.STATUS Status information
DNPNET.CONTROL Governs the data movement between the PLC rack and the module
DNPNET.UTIL Generic tags used for internal ladder processing (DO NOT MODIFY)

ProSoft Technology, Inc. Page 22 of 133

MVI56E-DNPNET

2.3.2 DNPNET.CONFIG.DNP_Module_Name
Configures the name of the MVI56E-DNPNET.

Tag Name Range Description

DNPNET.Config.DNP 0 or 32 to 126 String of ASCII characters (up to 40) that gives
_Module_Name[0] to [39] the module a unique name. Terminate the string
with a byte = 0. Module is named "MVI56E-
DNPNET" by default.

2.3.3 DNPNET.CONFIG.DNP3_Server
This array configures the MVI56E-DNPNET server.

DNPNET.Config.DNP3_Server. Range Description

Internal_Server_ID 0 to 32767 This is the DNP address for the module. All
messages with this address from the client will be
processed by the module.
Use_WhiteList 0 or 1 This parameter specifies if the IP address of the
host connected to the system will be validated. If
the parameter is set to 0, any host may connect
to the unit. If the parameter is set to 1, only hosts
in the IP list will be permitted to connect to the
module. All other IP addresses will be ignored by
the module and the module will issue a RST to
the TCP/IP connection. The IP_List is contained
in DNP.Config.DNP_ENET_IP_Addresses.
Binary_Input_Class 0 to 3 This parameter specifies the default class to be
utilized for all the binary input points in the DNP
database that are not defined in the override list
section.
Analog16_Input_Class 0 to 3 This parameter specifies the default class to be
utilized for all the 16-bit analog input points in the
DNP database that are not defined in the
override list section.
Analog32_Input_Class 0 to 3 This parameter specifies the default class to be
utilized for all the 32-bit analog input points in the
DNP database that are not defined in the
override list section.
Float_Class 0 to 3 This parameter specifies the default class to be
utilized for all the float input points in the DNP
database that are not defined in the override list
section.
Double_Class 0 to 3 This parameter specifies the default class to be
utilized for all the double input points in the DNP
database that are not defined in the override list
section.
Analog16_Input_Deadband 0 to 32767 This parameter specifies the default deadband
value assigned to all points not defined in the
override list for the 16-bit analog input point type
in the DNP database.
Analog32_Input_Deadband 0 to This parameter specifies the default deadband
2,147,483,647 value assigned to all points not defined in the
override list for the 32-bit analog input point type
in the DNP database.

ProSoft Technology, Inc. Page 23 of 133

MVI56E-DNPNET

DNPNET.Config.DNP3_Server. Range Description

Float_Deadband 0 to maximum This parameter specifies the default deadband
float value value assigned to all points not defined in the
override list for the float input point type in the
DNP database.
Double_Deadband 0 to maximum This parameter specifies the default deadband
double value value assigned to all points not defined in the
override list for the double input point type in the
DNP database.
SelectOperate_Arm_Time 1 to 32767 Time period, in milliseconds, after select
command received in which operate command
will be performed. After the select command is
received, the operate command will only be
honored if it arrives within this period of time.
Write_Time_Interval 0 to 1440 Time interval, in minutes, to set the need time IIN
bit (0=never), which will cause the client to write
the time.
Data_Link_Confirm_Mode 0,1, or 2 IED can request acknowledgement from client
(Coded Value) station when sending data. The codes are as
follows: 0=Never, 1=Sometimes, 2=Always.
Recommended value = 0.
Data_Link_Confirm_Tout 1 to 32767 Time period to wait for client Data Link
confirmation of last frame sent. This time is in
milliseconds. This parameter is only used if the
frame is sent with confirmation requested.
Recommended value = 1000.
Data_Link_Max_Retry 0 to 255 Maximum number of retries at the Data Link level
to obtain a confirmation. If this value is set to 0,
retries are disabled at the data link level of the
protocol. This parameter is only used if the frame
is sent with confirmation requested.
Recommended value = 2.
App_Layer_Confirm_Tout 1 to 32767 Event data contained in the last response may be
sent again if not confirmed within the millisecond
time period set. If application layer confirms are
used with data link confirms, ensure that the
application layer confirm timeout is set long
enough.
Unsolicited_Response 0 or 1 If set to 0, the server will not send unsolicited
responses. If set to 1, the server will send
unsolicited responses.
Class_1_Unsol_Resp_Min 1 to 255 Minimum number of events in Class 1 required
before an unsolicited response will be generated.
Class_2_Unsol_Resp_Min 1 to 255 Minimum number of events in Class 2 required
before an unsolicited response will be generated.
Class_3_Unsol_Resp_Min 1 to 255 Minimum number of events in Class 3 required
before an unsolicited response will be generated.
Unsol_Resp_Delay 1 to 32767 Maximum number of milliseconds to wait after an
event occurs before sending an unsolicited
response message. If set to 0, only use minimum
number of events.
UResp_Client_Address 0 to 255 DNP destination address where unsolicited
response messages are sent.

ProSoft Technology, Inc. Page 24 of 133

MVI56E-DNPNET

DNPNET.Config.DNP3_Server. Range Description

AnalogInput_Events_with_time 0 or 1 This parameter sets if the analog input events
generated by the module will include the date
and time of the event. If the parameter is set to 0,
the default is set to no time data. If the parameter
is set to 1, the default object will include the time
of the event.
Events_Require_Time_Sync 0 or 1 This parameter is used to determine if events will
be generated by the server module when its time
is not synchronized from a client. If the parameter
is set to 1, no events will be generated until the
module's time has been synchronized. If the
parameter is set to 0, events will always be
generated.
Initialize_DNP_Output_Database 0 or 1 This parameter determines if the module will
request data from the processor to initialize the
DNP database output data areas. If this option is
utilized, ladder logic is required to send the
requested blocks from the processor to the
module.
PassThrough_CROB 0 or 1 This parameter determines if the module will
pass all received CROB messages received
through to the processor. If it is set to 0 (default),
then the messages will not be sent to the
processor. If the parameter is set to 1, then block
9910 will be sent to the processor with the CROB
information. The database will still be controlled
by the CROB message, but the ladder can
control other virtual BO data in the processor
using this data. This feature is useful if the
controlling station sends CROB data to the server
driver with very short on or off times.
Use_TripClose_Single_Point 0 or 1 This parameter determines if data associated
with CROB commands operate on a single or
dual point. If the value of 0 is supplied (default
value), then all points will be dual-point unless
neither the trip or close bit is set in the control
code of the command. If either bit is set, then the
CROB block will interact with the bit database as
a dual-point database. If the parameter is set to
1, then all CROB blocks received will operate on
the database as single bits.
Unsol_Retry_Limit 7 to 32768 Configurable unsolicited retry limit. The module
sends an unsolicited message and waits for a
confirmation with the Application Layer Confirm
Timeout up to the limit specified until the
unsolicited message is confirmed. If the amount
of unsolicited messages are exceeded, the
Ethernet connection will be lost. Another DNP
message could wake up the connection.
The allowable limits are 7 to 32768.
Use_SOE_card 0 or 1 Using Allen Bradley 1756-SOE Sequence of
Events Module. 0 = No, 1 = Yes
Use_Data_from_Client_Connection 0 or 1 This parameter enables data from the MVI client
connection to be shared with the MVI server
database. 0 = No, 1 = Yes
Use_Double_Floats 0 or 1 This parameter enables the DNP Double Float
(64bit) database. 0 = Disable, 1 = Enable

ProSoft Technology, Inc. Page 25 of 133

MVI56E-DNPNET

DNPNET.Config.DNP3_Server. Range Description

Block_Timeout_MS 11 to 5000 Backplane block heartbeat. If an out of range
milliseconds value is entered, the value will default to 1500.
Server_Timeout 5 to 32767 Configurable TCP Server Connection timeout
seconds parameter. After the initial TCP connections has
been made and there is no activity on the
connection, the server will timeout and close the
connection. If an out of range value is entered,
the value will default to 5 seconds.
Reserved_0 Reserved

2.3.4 DNPNET.CONFIG.DNP3_WhiteList[x]
To avoid unknown or outside devices from trying to connect to the MVI56E-
DNPNET, you can create an exclusive list of IP addresses allowed to access the
device. There are a maximum of 10 IP addresses that can be configured. This
tag array is used if the DNPNET.CONFIG.DNP3_Server.Use_WhiteList tag is set
to 1.

Tag Name Range Description

DNPNET.CONFIG.DNP3_WhiteList[0].a 1 to 254 IP Address Octet A
DNPNET.CONFIG.DNP3_WhiteList[0].b 0 to 254 IP Address Octet B
DNPNET.CONFIG.DNP3_WhiteList[0].c 0 to 254 IP Address Octet C
DNPNET.CONFIG.DNP3_WhiteList[0].d 1 to 254 IP Address Octet D
DNPNET.CONFIG.DNP3_WhiteList[1].a
DNPNET.CONFIG.DNP3_WhiteList[1].b
DNPNET.CONFIG.DNP3_WhiteList[1].c
DNPNET.CONFIG.DNP3_WhiteList[1].d
… … …
DNPNET.CONFIG.DNP3_WhiteList[9].a
DNPNET.CONFIG.DNP3_WhiteList[9].b
DNPNET.CONFIG.DNP3_WhiteList[9].c
DNPNET.CONFIG.DNP3_WhiteList[9].d

ProSoft Technology, Inc. Page 26 of 133

MVI56E-DNPNET

2.3.5 DNPNET.CONFIG.DNP3_Client
This array configures the MVI56E-DNPNET client.

DNPNET.CONFIG.DNP3_Client. Range Description

Internal_ID 0 to 32767 This is the DNP address for the module. All
messages with this address from the client will be
processed by the module.
Event_Messages_to_PLC 0 or 1 This parameter determines if event messages
received on the client port will be sent to the
processor. If this option is utilized, ladder logic must
be written to handle the 9903 blocks generated by
the module.
Initialize_IED_Input_Database 0 or 1 This parameter determines if the module will
request data from the processor to initialize the IED
database input data areas. If this option is utilized,
ladder logic is required to send the requested blocks
from the processor to the module.
Only_Time_Sync_Servers_If_Synced 0 or 1 This parameter determines if the client will send a
time sync message to servers when its own time
has not yet been synced via PLC or a connected
client. If set to 0, the client will send a time sync to
connected servers even if its own clock has not
been synced by the PLC or another connected
client. If set to 1, the client will not send time syncs
to servers until it has been synced by the PLC or a
connected client.
Use_Binary_Output_status_Data 0 or 1 Enable database and functions for reading the
status of Binary Outputs (object 10).
Use_Analog_Output_status_Data 0 or 1 Enable database and functions for reading the
status of Analog Outputs (object 40).
Dont_Process_IIN 0 or 1 By default (0), the Client module will automatically
make requests to servers that have IIN bits set for
class data, need time, restart, or buffer overflow
until these IIN bits have been cleared. If this
parameter is set to 1, the Client will NOT
automatically make these requests as a result of
these IIN bits being set.

ProSoft Technology, Inc. Page 27 of 133

MVI56E-DNPNET

2.3.6 DNPNET.CONFIG.DNP_Server_Override
This array assigns Class and Deadband overrides to individual point types. You
can adjust the size of each of the 5 point type arrays.

DNPNET.CONFIG.DNP_ Range Description

Server_Override.
Binary_Inputs. n/a Number of binary input words contained in the
IED database to be transferred to the PLC and
obtained from the attached IED units.
This array size ranges from 0 to 1000.
Point_Number 0 to Number of points Point number index to be overridden
configured Point
number index to be
overridden
Class 1 to 3 Class number assigned to point number specified
above
Analog16_Inputs. n/a Number of 16-bit analog input points contained in
the IED database to be transferred to the PLC
and obtained from the attached IED units.
This array size ranges from 0 to 1000.
Point_Number 0 to Number of points Point number index to be overridden
configured
Class 1 to 3 Class number assigned to point number specified
Deadband 0 to 32767 Deadband assigned to point number specified
Analog32_Inputs. n/a Number of 32-bit analog input points contained in
the IED database to be transferred to the PLC
and obtained from the attached IED units. This
array size ranges from 0 to 500.
Point_Number 0 to Number of points Point number index to be overridden
configured
Class 1 to 3 Class number assigned to point number specified
Deadband 0 to 32767 Deadband assigned to point number specified
Float_Inputs. n/a Number of float input points contained in the IED
database to be transferred to the PLC and
obtained from the attached IED units
This array size ranges from 0 to 500.
Point_Number 0 to Number of points Point number index to be overridden
configured
Class 1 to 3 Class number assigned to point number specified
Deadband 0 to 32767 Deadband assigned to point number specified
Double_Inputs. n/a Number of counter points contained in the IED
database to be transferred to the PLC and
obtained from the attached IED units. This array
size ranges from 0 to 250.
Point_Number 0 to Number of points Point number index to be overridden
configured
Class 1 to 3 Class number assigned to point number specified
Deadband 0 to 32767 Deadband assigned to point number specified

ProSoft Technology, Inc. Page 28 of 133

MVI56E-DNPNET

1 To edit the length of the Client Commands array, double-click the

DNPNETCONFIG UDT.
2 Edit the length inside the [ ] of the DNPNET_Client_Commands[ ] Data Type.

3 Click APPLY and then click YES to accept changes to the Data Type.
4 Click OK to close this window.
5 Save and download the RSLogix program to the processor. Reboot the
MVI56E-DNPNET module to download changes to module.

ProSoft Technology, Inc. Page 34 of 133

MVI56E-DNPNET

2.3.9 DNPNET.CONFIG.IP_Settings[x]
Assigns the IP address configuration of the MVI56E-DNPNET.

DNPNET.CONFIG.IP_Settings. Range Description

Read 0 or 1 Triggers a request of the IP Address, Subnet
Mask, and Gateway parameters from the
module to the PLC. These parameters will
display in the IP, Netmask, Gateway tags
below.
Write 0 or 1 Triggers a transfer of the IP Address, Subnet
Mask, and Gateway parameters from the PLC
to the module. These parameters will come
from the IP, Netmask, Gateway tags below.
Config.IP 0 to 255 IP Address of MVI56E-DNPNET
Config.Netmask 0 to 255 Subnet Mask of MVI56E-DNPNET
Config.Gateway 0 to 255 Gateway of MVI56E-DNPNET

After setting these parameters they must be sent to the module by triggering a
download of these parameters.

ProSoft Technology, Inc. Page 35 of 133

MVI56E-DNPNET

3 Diagnostics and Troubleshooting

The module provides information on diagnostics and troubleshooting in the

following forms:
 LED status indicators on the front of the module provide information on the
module’s status.
 Status data contained in the module can be viewed in ProSoft Configuration
Builder through the Ethernet port.
 Status data values are transferred from the module to the processor.

3.1 Ethernet LED Indicators

The Ethernet LEDs indicate the module's Ethernet port status as follows:

LED State Description

Data OFF Ethernet connected at 10Mbps duplex speed
AMBER Solid Ethernet connected at 100Mbps duplex speed
Link OFF No physical network connection is detected. No Ethernet
communication is possible. Check wiring and cables.
GREEN Solid Physical network connection detected. This LED must be ON solid
or Blinking for Ethernet communication to be possible.

ProSoft Technology, Inc. Page 36 of 133

MVI56E-DNPNET

3.1.1 Scrolling LED Status Indicators

The scrolling LED display indicates the module’s operating status as follows:

Initialization Messages
Code Message
Boot / DDOK Module is initializing
Ladd Module is waiting for required module configuration data from
ladder logic to configure the Modbus ports
Waiting for Processor Connection Module did not connect to processor during initialization
 Sample ladder logic or AOI is not loaded on processor
 Module is located in a different slot than the one
configured in the ladder logic/AOI
 Processor is not in RUN or REM RUN mode
Last config: <date> Indicates the last date when the module changed its IP
address. You can update the module date and time through
the Connect to the Module’s Webpage (page 66), or with the
MVI56E Add-On Instruction.

Operation Messages
After the initialization step, the following message pattern will be repeated.
<Backplane Status> <IP Address> <Backplane Status> <Port Status>

Code Message
<Backplane Status> OK: Module is communicating with processor
ERR: Module is unable to communicate with processor. For
this scenario, the <Port Status> message above is replaced
with "Processor faulted or is in program mode".
<IP Address> Module IP address
<Port Status> OK: Port is communicating without error
Client/Server Communication Errors: port is having
communication errors. Refer to Diagnostics and
Troubleshooting (page 36) for further information about the
error.

ProSoft Technology, Inc. Page 37 of 133

MVI56E-DNPNET

3.1.2 Non-Scrolling LED Status Indicators

The non-scrolling LEDs indicate the module’s operating status as follows:

LED Label Status Indication

APP OFF The module is not receiving adequate power or is not securely plugged
into the rack. May also be OFF during configuration download.
GREEN The MVI56E-DNPNET is working normally.
RED The most common cause is that the module has detected a
communication error during operation of an application port.
The following conditions may also cause a RED LED:
 The firmware is initializing during startup
 The firmware detects an on-board hardware problem during startup
 Failure of application port hardware during startup
 The module is shutting down
 The module is rebooting due to a ColdBoot or WarmBoot request
from the ladder logic or Debug Menu
OK OFF The module is not receiving adequate power or is not securely plugged
into the rack.
GREEN The module is operating normally.
RED The module has detected an internal error or is being initialized. If the
LED remains RED for over 10 seconds, the module is not working.
Remove it from the rack and re-insert it to restart its internal program.
ERR RED Not used.

3.2 Clearing a Fault Condition

Typically, if the OK LED on the front of the module remains RED for more than
ten seconds, a hardware problem has been detected 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 it is installed correctly.
5 Re-insert the card in the rack and turn the power back on.
6 Verify correct configuration data is being transferred to the module from the
ControlLogix controller.
If the module's OK LED does not turn GREEN, verify that the module is inserted
completely into the rack. If this does not cure the problem, contact ProSoft
Technology Technical Support.

ProSoft Technology, Inc. Page 38 of 133

MVI56E-DNPNET

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

Processor Errors
Problem Description Steps to take
Processor Fault Verify that the module is plugged into the slot that has been configured
for the module in the I/O Configuration of RSLogix.
Verify that the slot location in the rack has been configured correctly in
the ladder logic.
Processor I/O LED This indicates a problem with backplane communications. A problem
flashes could exist between the processor and any installed I/O module, not just
the MVI56E-DNPNET. Verify that all modules in the rack are correctly
configured in the ladder logic.

Module Errors
Problem Description Steps to take
MVI56E modules with This indicates that backplane transfer operations are failing. Connect to
scrolling LED display: the module’s Configuration/Debug port to check this.
<Backplane Status> To establish backplane communications, verify the following items:
condition reads ERR  The processor is in RUN or REM RUN mode.
 The backplane driver is loaded in the module.
 The module is configured for read and write data block transfer.
 The ladder logic handles all read and write block situations.
 The module is properly configured in the processor I/O configuration
and ladder logic.
OK LED remains RED 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.

ProSoft Technology, Inc. Page 39 of 133

MVI56E-DNPNET

3.4 Setting Up ProSoft Configuration Builder

ProSoft Configuration Builder (PCB) software provides a convenient way to

configure, monitor, and troubleshoot your MVI56E-DNPNET module.

3.4.1 Installing ProSoft Configuration Builder

Use the ProSoft Configuration Builder (PCB) software to configure the module.
You can find the latest version of the ProSoft Configuration Builder (PCB) on our
web site: www.prosoft-technology.com. The installation filename contains the
PCB version number.

Installing PCB from the ProSoft website:

1 Open a browser window and navigate to www.prosoft-technology.com.
2 Perform a search for 'pcb' in the Search bar. Click on the ProSoft
Configuration Builder search result.
3 On the PCB page, click the download link for ProSoft Configuration Builder,
and save the file to your Windows desktop.
4 After the download completes, double-click the file to install. If you are using
Windows 7, right-click the PCB installation file and then choose RUN AS
ADMINISTRATOR. Follow the instructions that appear on the screen.
5 If you want to find additional software specific to your MVI56E-DNPNET,
enter the model number into the ProSoft website search box and press the
ENTER key.

ProSoft Technology, Inc. Page 40 of 133

MVI56E-DNPNET

3.4.2 Setting Up the Project

To begin, start PROSOFT CONFIGURATION BUILDER (PCB).

If you have used other Windows configuration tools before, you will find the
screen layout familiar. PCB’s window consists of a tree view on the left, and an
information pane and a configuration pane on the right side of the window. When
you first start PCB, the tree view consists of folders for Default Project and
Default Location, with a Default Module in the Default Location folder. The
following illustration shows the PCB window with a new project.

Your first task is to add the MVI56E-DNPNET module to the project.

ProSoft Technology, Inc. Page 41 of 133

MVI56E-DNPNET

1 Right-click DEFAULT MODULE in the tree view and then choose CHOOSE
MODULE TYPE. This opens the Choose Module Type dialog box.

2 In the Product Line Filter area of the dialog box, select MVI56E. In the Select
Module Type dropdown list, select MVI56E-DNPNET, and then click OK to
save your settings and return to the ProSoft Configuration Builder window.

ProSoft Technology, Inc. Page 42 of 133

MVI56E-DNPNET

3.5 Connecting Your PC to the Module

3.5.1 Using CIPconnect® to Connect to the Module

You can use CIPconnect® to connect a PC to the ProSoft Technology MVI56E-
DNPNET module over Ethernet using Rockwell Automation’s 1756-ENBT
EtherNet/IP® module. This allows you to configure the MVI56E-DNPNET network
settings and view module diagnostics from a PC. RSLinx is not required when
you use CIPconnect. All you need are:
 The IP addresses and slot numbers of any 1756-ENBT modules in the path
 The slot number of the MVI56E-DNPNET in the destination ControlLogix
chassis (the last ENBTx and chassis in the path).

To use CIPconnect, follow these steps:

1 In the tree view in ProSoft Configuration Builder, right-click the MVI56E-
DNPNET icon and then choose DIAGNOSTICS.

2 In the Diagnostics window, click the SET UP CONNECTION button.

ProSoft Technology, Inc. Page 43 of 133

MVI56E-DNPNET

3 In the Select Connection Type dropdown list, choose 1756-ENBT. The

default path appears in the text box, as shown in the following illustration.

4 Click CIP PATH EDIT to open the CIPconnect Path Editor dialog box.

The CIPconnect Path Editor allows you to define the path between the PC and
the MVI56E-DNPNET module. The first connection from the PC is always a
1756-ENBT (Ethernet/IP) module.

ProSoft Technology, Inc. Page 44 of 133

MVI56E-DNPNET

Each row corresponds to a physical rack in the CIP path.

 If the MVI56E-DNPNET module is located in the same rack as the first 1756-
ENBT module, select RACK NO. 1 and configure the associated parameters.
 If the MVI56E-DNPNET is available in a remote rack (accessible through
ControlNet or Ethernet/IP), include all racks (by using the ADD RACK button).

Parameter Description
Source Module Source module type. This field is automatically selected
depending on the destination module of the last rack (1756-
CNB or 1756-ENBT).
Source Module IP Address IP address of the source module (only applicable for 1756-
ENBT)
Source Module Node Address Node address of the source module (only applicable for 1756-
CNB)
Destination Module Select the destination module associated to the source module
in the rack. The connection between the source and destination
modules is performed through the backplane.
Destination Module Slot Number The slot number where the destination MVI56E module is
located.

To use the CIPconnect Path Editor, follow these steps:

1 Configure the path between the 1756-ENBT connected to your PC and the
MVI56E-DNPNET module.
o If the module is located in a remote rack, add more racks to configure the
full path.
o The path can only contain ControlNet or Ethernet/IP networks.
o The maximum number of supported racks is six.
2 Click CONSTRUCT CIP PATH to build the path in text format
3 Click OK to confirm the configured path.

The following examples should provide a better understanding on how to set up

the path for your network.

ProSoft Technology, Inc. Page 45 of 133

MVI56E-DNPNET

Example 1: Local Rack Application

For this example, the MVI56E-DNPNET module is located in the same rack as
the 1756-ENBT that is connected to the PC.

MVI56E Module 1756-ENBT

Rack 1

0 1 2 3
Ethernet

Rack 1
Slot Module Network Address
0 ControlLogix Processor -
1 Any -
2 MVI56E-DNPNET -
3 1756-ENBT IP=192.168.0.100

1 In the tree view in ProSoft Configuration Builder, right-click the MVI56E-

DNPNET icon to open a shortcut menu.
2 On the shortcut menu, choose DIAGNOSTICS.

3 In the Diagnostics window, click the SET UP CONNECTION button.

ProSoft Technology, Inc. Page 46 of 133

MVI56E-DNPNET

4 In the Connection Setup dialog box, click CIP PATH EDIT.

5 Configure the path as shown in the following illustration, and click

CONSTRUCT CIP PATH to build the path in text format.

Click OK to close the CIPconnect Path Editor and return to the Connection
Setup dialog box.

ProSoft Technology, Inc. Page 47 of 133

MVI56E-DNPNET

6 Check the new path in the Connection Setup dialog box.

7 Click TEST CONNECTION to verify that the physical path is available. The
following message should be displayed upon success.

8 Click OK to close the Test Connection pop-up and then click CONNECT to
close the Connection Set up dialog box. The Diagnostics menu is now
connected through CIPconnect.

ProSoft Technology, Inc. Page 48 of 133

MVI56E-DNPNET

Example 2: Remote Rack Application

For this example, the MVI56E-DNPNET module is located in a remote rack
accessible through ControlNet, as shown in the following illustration.

1756-CNB 1756-ENBT
Rack 1

0 1 2 3
Ethernet

ControlNet

1756-CNB MVI56E Module

Rack 2

0 1 2 3 4 5 6

Rack 1
Slot Module Network Address
0 ControlLogix Processor -
1 1756-CNB Node = 1
2 1756-ENBT IP=192.168.0.100
3 Any -

Rack 2
Slot Module Network Address
0 Any -
1 Any -
2 Any -
3 Any -
4 Any -
5 1756-CNB Node = 2
6 MVI56E-DNPNET -

ProSoft Technology, Inc. Page 49 of 133

MVI56E-DNPNET

1 In the tree view in ProSoft Configuration Builder, right-click the MVI56E-

DNPNET icon to open a shortcut menu.
2 On the shortcut menu, choose DIAGNOSTICS.

3 In the Diagnostics window, click the SET UP CONNECTION button.

4 In the Connection Setup dialog box, click CIP PATH EDIT.

ProSoft Technology, Inc. Page 50 of 133

MVI56E-DNPNET

5 Configure the path as shown in the following illustration and click CONSTRUCT
CIP PATH to build the path in text format.

Click OK to close the CIPconnect Path Editor and return to the Connection
Setup dialog box.
6 Check the new path in the Connection Setup dialog box.

ProSoft Technology, Inc. Page 51 of 133

MVI56E-DNPNET

7 Click TEST CONNECTION to verify that the physical path is available. The
following message should be displayed upon success.

8 Click OK to close the Test Connection pop-up and then click CONNECT to
close the Connection Set up dialog box. The Diagnostics menu is now
connected through CIPconnect.

ProSoft Technology, Inc. Page 52 of 133

MVI56E-DNPNET

3.5.2 Using RSWho to Connect to the Module

You need to have RSLinx installed on your PC to use this feature. You also need an ENBT module
set up in the rack. For information on setting up the ENBT module, see Using CIPconnect® to
Connect to the Module (page 43).

1 In ProSoft Configuration Builder, click the PROJECT menu, then choose

MODULE > DOWNLOAD FROM PC TO DEVICE.
2 In the Download dialog box, choose 1756 ENBT from the Select Connection
Type dropdown box.

3 Click RSWHO to display modules on the network. The MVI56E-DNPNET

module will automatically be identified on the network.

4 Select the module, and then click OK.

5 In the Download dialog box, click DOWNLOAD.

ProSoft Technology, Inc. Page 53 of 133

MVI56E-DNPNET

3.5.3 Connecting Your PC to the Module's Ethernet Port

With the module securely mounted, connect one end of the Ethernet cable to the
CONFIG (E1) Port, and the other end to an Ethernet hub or switch accessible from
the same network as your PC. Or, you can connect directly from the Ethernet
Port on your PC to the CONFIG (E1) Port on the module.

3.6 Using the Diagnostics Menu in ProSoft Configuration Builder

The Diagnostics menu, available through the Ethernet configuration port for this
module, is arranged as a tree structure, with the Main menu at the top of the tree,
and one or more submenus for each menu command. The first menu you see
when you connect to the module is the Main menu.

Tip: You can have a ProSoft Configuration Builder Diagnostics window open for more than one
module at a time.

To connect to the module, refer to Connecting Your PC to the Module (page 43).
1 In the tree view in ProSoft Configuration Builder, right-click the MVI56E-
DNPNET icon to open a shortcut menu.
2 On the shortcut menu, choose DIAGNOSTICS.

ProSoft Technology, Inc. Page 54 of 133

MVI56E-DNPNET

3 In the Diagnostics window, click the SET UP CONNECTION button.

4 In the Ethernet field of the Connection Setup dialog box, enter the IP address
that was assigned the module in Assigning a Permanent IP Address (page
21). In the Connection Setup dialog box, click the TEST CONNECTION button to
verify that the module is accessible with the current settings.

You can also use CIPconnect® to connect to the module through a 1756-
ENBT card by choosing 1756-ENBT in the SELECT CONNECTION TYPE list.
Refer to Using CIPconnect® to Connect to the Module (page 43) for
information on how to construct a CIP path.

ProSoft Technology, Inc. Page 55 of 133

MVI56E-DNPNET

5 If the Test Connection is successful, click CONNECT to display the Diagnostics

menu in the Diagnostics Window.

If PCB is unable to connect to the module:

3.8 Connect to the MVI56E-DNPNET Webpage

The module's internal web server provides access to module status, diagnostics,
and firmware updates. If the module's IP address has already been assigned,
simply enter in the IP address into a web browser. If not, follow the steps below:
1 In ProSoft Configuration Builder, click the PROJECT menu, then choose
MODULE > DOWNLOAD FROM PC TO DEVICE. This opens the Download dialog
box.
2 In the Download dialog box, choose the connection type in the Select
Connection Type dropdown box:
o Choose ETHERNET if you are connecting to the module through the
Ethernet cable.
o Choose 1756 ENBT if you are connecting to the module through
CIPconnect or RSWho.
Refer to Connecting Your PC to the Module (page 43) for more
information.
3 In the Download files from PC to module dialog box, click BROWSE DEVICE(S).
4 In ProSoft Discovery Service, right-click the MVI56E-DNPNET icon and
choose VIEW MODULE’S WEBPAGE from the shortcut menu.

This displays the module webpage.

ProSoft Technology, Inc. Page 66 of 133

MVI56E-DNPNET

4 Reference

4.1 Product Specifications

The MVI56E-DNPNET (DNP3 Ethernet Client/Server Communication Module)
allows Rockwell Automation ControlLogix I/O compatible processors to interface
easily with other DNP3 Ethernet protocol compatible devices. The module
supports DNP3 Ethernet Subset Level 2 features and some of the Level 3
features.
The module acts as an input/output communications module between the DNP3
Ethernet network and the ControlLogix backplane. The data transfer from the
ControlLogix processor is asynchronous from the actions on the DNP3 Ethernet
network. Databases are user-defined and stored in the module to hold the data
required by the protocol.
This product features:
 ProSoft Configuration Builder (PCB): Microsoft Windows®-based utility
software for diagnostics. Connect through the module's Ethernet port or use
CIPconnect® to access troubleshooting features and functions.
 ProSoft Discovery Service (PDS): New Windows-based utility software to find
and display a list of MVI56E modules on the network and to temporarily
change a module's IP address to be able to connect with a module's
webpage.
 CIPconnect-enabled: Allows PC-to-module diagnostics from the Ethernet
network through a ControlLogix® 1756-ENxT EtherNet/IP™ module.
 Personality Card: An industrial-grade compact flash memory card storing the
module’s Ethernet settings, allowing quick and easy replacement.
 LED Scrolling Diagnostic Display: 4-character, alphanumeric display,
providing messages for status and alarm data, and for processor and network
communication status.

4.1.1 General Specifications

 Single Slot - 1756 ControlLogix® backplane compatible
 10/100 MB Ethernet port for network configuration and diagnostics with Auto
Cable Crossover Detection
 Add-On Instruction (AOI) used for data transfers between module and
processor and for module configuration
 User-definable module data memory mapping of thousands of DNP3
Ethernet points based on the various types of data.

ProSoft Technology, Inc. Page 67 of 133

MVI56E-DNPNET

DNP 3.0
Ethernet Data Point Type Range
DNP_Outputs Binary Outputs 0 to 8000 points (500 16-bit words)
Analog Outputs
16-bit Analog Outputs 0 to 5000 points (if all other DNP Outputs are 0)
32-bit Analog Outputs 0 to 2500 points (if all other DNP Outputs are 0)
Float Outputs 0 to 2500 points (if all other DNP Outputs are 0)
Double Float Outputs 0 to 1250 points (if all other DNP Outputs are 0)
DNP_Inputs Binary Inputs 0 to 8000 points (‘500’ 16-bit words)
Analog Inputs
16-bit Analog Inputs 0 to 5000 points (if all other DNP Inputs are 0)
32-bit Analog Inputs 0 to 2500 points (if all other DNP Inputs are 0)
Float Inputs 0 to 2500 points (if all other DNP Inputs are 0)
Double Float Inputs 0 to 1250 points (if all other DNP Inputs are 0)
Counters 0 to 1000 points
IED_Outputs Binary Outputs 0 to 8000 points (500 16-bit words)
Analog Outputs
16-bit Analog Outputs 0 to 20000 points (if all other IED Outputs are 0)
32-bit Analog Outputs 0 to 10000 points (if all other IED Outputs are 0)
Float Outputs 0 to 10000 points (if all other IED Outputs are 0)
IED_Inputs Binary Inputs 0 to 8000 points (‘500’ 16-bit words)
Analog Inputs
16-bit Analog Inputs 0 to 20000 points (if all other IED Inputs are 0)
32-bit Analog Inputs 0 to 10000 points (if all other IED Inputs are 0)
Float Inputs 0 to 10000 points (if all other IED Inputs are 0)
Counters 0 to 1000 points
Binary Output Status 0 to 8000 points (‘500’ 16-bit words)
16-bit Analog Output Status 0 to 20000 points
32-bit Analog Output Status 0 to 10000 points
Float Output Status 0 to 10000 points

ProSoft Technology, Inc. Page 68 of 133

MVI56E-DNPNET

4.1.2 Functional Specifications

The MVI56E-DNPNET operates on a Local or Remote rack CIPconnect® enabled
for module and network configuration using 1756-ENxT module with EtherNet/IP
pass-through communications.
 4-digit LED Display for status and diagnostics information
 Error codes, network error counters, and port status data available in user
data memory

Server Specifications
The DNP3 Ethernet port can accept DNP3 Ethernet commands to control and
monitor data stored in the module’s DNP3 Ethernet server database. If a DNP3
Ethernet Client is also configured, a portion of the server database can be
derived from or can control IED devices connected to the DNP3 Ethernet Client.
 Report-by-Exception data is logged to the module’s database
 Supports unsolicited messaging
 Each DNP3 Ethernet point type is user-configurable in the DNPNET
Controller tags of RSLogix 5000 software
 Class assignments are user-definable on a Type and point basis (BI, AI, FI,
DI point types)
 Supports clock synchronization from a remote Client or from the processor
 Up to 20,000 events are stored for Binary Inputs, Analog Inputs, Floats and
Double Inputs. This varies based on point types in the table above.

Client Specifications
The DNP3 Ethernet port can be configured as a virtual DNP3 Ethernet Client
device that actively issues user-defined DNP3 Ethernet commands to nodes on
the network.
 The Module supports 300 user defined commands, each one containing its
own set of data link and application layer characteristics
 Client logically supports up to 40 server devices
 Individual command configuration includes conditional or continuous polling
and Poll Delay Time
 Server status and Command status available for transfer to the processor
 Event data received from the server devices updates the module database
with the latest data values. Optionally date and time stamped data can be
passed to the processor through a special block 9903 that is
enabled/disabled through the parameter Pass Event Messages to PLC within
the configuration of the module. When this option is used, events from the
attached servers are passed to an array in the ladder logic containing the
event data (server device, point index, point value) as well as the time stamp
of the event from the attached server device (value is presented as the 64 bit
UCT time matching the ControlLogix processor date/time format).
 Special command handling for Digital Output CROB under processor control
for pulse output control

ProSoft Technology, Inc. Page 69 of 133

MVI56E-DNPNET

4.1.3 Hardware Specifications

Specification Description
Backplane Current Load 800 mA @ 5 Vdc
3 mA @ 24 Vdc
Operating Temperature 0°C to 60°C (32°F to 140°F)
Storage Temperature -40°C to 85°C (-40°F to 185°F)
Shock 30 g operational
50 g non-operational
Vibration: 5 g from 10 to 150 Hz
Relative Humidity 5% to 95% (without condensation)
LED Indicators Battery Status (ERR)
Application Status (APP)
Module Status (OK)
4-Character, Scrolling, Alpha- Shows Module, Version, IP, Port Client/Server Setting, Port
Numeric LED Display Status, and Error Information
Communication Ethernet Port
Ethernet Port 10/100 Base-T, RJ45 Connector, for CAT5 cable
Link and Activity LED indicators
Auto-crossover cable detection

4.2 Functional Overview

4.2.1 MVI56E-DNPNET Backplane Data Exchange

General Concepts of MVI56E-DNPNET Data Transfer

Ladder logic is required for the MVI56E-DNPNET module to communicate along
the backplane with the ControlLogix processor. The ladder logic handles the
module data transfer, transfer of configuration data, 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.
For most applications, the sample Add-On Instruction (which includes the ladder
logic) will work without modification.

The following topics describe several concepts that are important for
understanding the operation of the MVI56E-DNPNET module.
1 On power up the module begins the following logical functions:
o Initialize hardware components
o Initialize ControlLogix backplane driver
o Test and Clear all RAM
2 Reads configuration from the ControlLogix processor via ladder logic
3 Allocate and initialize Module Register space
4 Enable Client and Server Driver on Ethernet port
5 After the module has received the Module Configuration, the module will
begin communicating with other nodes on the DNP3 Ethernet network,
depending on the configuration.

ProSoft Technology, Inc. Page 70 of 133

ProSoft Technology, Inc. Page 74 of 133

MVI56E-DNPNET

Step Description
1 The Client driver configuration data is obtained from the DNPNET configuration tags via
ladder logic. These values are used by the Client driver to determine the type of
commands to be issued to the other nodes on the DNP3 Ethernet network.
2 After configuration, the Client driver begins transmitting read and/or write commands to the
other nodes on the network. If writing data to another node, the data for the write
command is obtained from one of the module’s internal databases to build the command.
3 Presuming successful processing by the node specified in the command, a response
message is received into the Client driver for processing.
4 Data received from the node on the network is passed into the module’s appropriate
internal database, assuming a read command.
5 Status is returned to the ControlLogix processor for each command in the Client
Command List.

ProSoft Technology, Inc. Page 75 of 133

MVI56E-DNPNET

4.2.2 Function Blocks

Data contained in this database is paged through the input and output images by
coordination of the ControlLogix ladder logic and the MVI56E-DNPNET module's
program. Up to 248 words of data can be transferred from the module to the
processor at a time. Up to 247 words of data can be transferred from the
processor to the module.
Each block transferred from the module to the processor or from the processor to
the module contains a block identification code that describes the content of the
block.

Block Number Function/Description

0 or -1 Dummy Blocks: Used by module when no data is to be transferred
1 to 203 DNP and IED Data blocks
300 Error/Status, Error List Block, and slave IIN bits
1000 to 1022 DNP Output initialization blocks
1100 to 1193 IED Input initialization blocks
9000 - 9099 Configuration Data
9901 CROB Control Block for Digital Outputs
9902 Command Control Block (Add command to Command List Queue)
9903 Event Messages from Client port
9904 Places up to 24 Auxiliary Commands in the command queue.
9910 CROB Data received on DNPNET Port
9949 Server IED unit errors on Client port
9950 Command List Error data
9958 Binary Input Event data with Calendar time
9959 Analog Input Event data with Calendar time
9968 Binary Input Event data with CLX time
9969 Analog Input Event data with CLX time
9970 Set PLC time using module's DNP time
9971 Set module's time using PLC time
9998 Warm Boot Request from PLC (Block contains no data)
9999 Cold Boot Request from PLC (Block contains no data)

Blocks 0 and -1 are empty blocks used during module startup, when there is no
data to transfer.
Blocks 1 to 203 are used to transfer the various kinds of DNPNET and IED
process data. Block 300 transfers error and status data. Blocks 9901 to 9999 are
used for Special Functions.

ProSoft Technology, Inc. Page 76 of 133

MVI56E-DNPNET

in Block
0 Block ID Contains the block identification code of 9901 for the block.
1 Command Count This field defines the number of CROB blocks to generate.
The valid range for the field is 1 to 24.
2 to 11 Command #1 Data for the command relay block (CROB) to be generated.
12 to 21 Command #2 Data for the command relay block (CROB) to be generated.
22 to 31 Command #3 Data for the command relay block (CROB) to be generated.
32 to 41 Command #4 Data for the command relay block (CROB) to be generated.
… … …
232 to 241 Command #24 Data for the command relay block (CROB) to be generated.

The 10-word data area for each command is defined in the following table.

Word Offset Definitions Description

0 PortFlags Clear 3rd bit to disable. Set 5th bit to select IED DB for write
functions
1 Server Address IED node address for the server to consider on the network.
2 Object Object type always 12
3 Variation Variation always 1
4 Function Function codes 3 (select/operate), 5 (direct operate with ACK),
and 6 (direct operate no ACK) supported. Function code 4 is
automatically sent after a successful function 3.
5 Address in Server Point in IED to consider with the CROB.
6 Control Code This is a standard DNPNET protocol control code byte (see
description below).
7 Pulse Count This parameter specifies the number of pulses to generate for
pulse output control. This parameter has a range of 0 to 255
as the value is a byte parameter in the CROB. If a value of
zero is entered, the operation will not execute.
8 Pulse On Time This parameter specifies the on-time interval for pulse control.
9 Pulse Off Time This parameter specifies the off-time interval for pulse control.

ProSoft Technology, Inc. Page 81 of 133

MVI56E-DNPNET

The control code in the command is a bit-coded byte value with the following
definition:

Bits Definitions Description

0 to 3 Code These bits determine the control operation to be performed by
the command: 0=No operation, 1=Pulse on, 2=Pulse off,
3=Latch on and 4=Latch off. All other values are undefined in
the DNPNET protocol.
4 Queue 0=Normal (execute once), 1=Re-queue (place at end of queue
after operation).
5 Clear This parameter clears the queue. If the value is set to zero, the
queue is not affected. If the value is set to 1, the queue will be
cleared.
6 to 7 Trip/Close These two bits select the trip or close relay. For close relay
control, set the bits to 01. For trip relay control, set the bits to
10. A value of 00 for the bits is used for single point control of
normal digital output points.

The commands placed in the normal command list for the Client port does not
provide the means for all the possible CROB operations. It only supports the
latch on and off operations based on the status of the associated database value
specified in the command. With the use of this block, outputs can be pulsed on or
off for user specified count and time intervals. Additionally, this command
provides support for trip/close relay control.

Block 9902: Command Control

If the ControlLogix processor sends a block 9902, the module will place the
commands referenced in the block in the command queue. Commands placed in
the queue with this method need not have their enable bit set. Only valid
commands will be placed in the queue.

Word Offset Data Field(s) Description

Block Format for Read

Word Offset Stop Data Field(s) Description

Start
0 0 Reserved
1 1 Block ID This is the next block requested by the module.
2 2 CROB count This field contains the number of CROB records that are
contained in this block. The range is between 1 and 40.
3 8 CROB 1 CROB block data as defined below
9 14 CROB 2 CROB block data as defined below
15 20 CROB 3 CROB block data as defined below
21 26 CROB 4 CROB block data as defined below
27 32 CROB 5 CROB block data as defined below
33 38 CROB 6 CROB block data as defined below
39 44 CROB 7 CROB block data as defined below
45 50 CROB 8 CROB block data as defined below
51 56 CROB 9 CROB block data as defined below
57 62 CROB 10 CROB block data as defined below
63 68 CROB 11 CROB block data as defined below
69 74 CROB 12 CROB block data as defined below
75 80 CROB 13 CROB block data as defined below
81 86 CROB 14 CROB block data as defined below
87 92 CROB 15 CROB block data as defined below
93 98 CROB 16 CROB block data as defined below
99 104 CROB 17 CROB block data as defined below
105 110 CROB 18 CROB block data as defined below
111 116 CROB 19 CROB block data as defined below
117 122 CROB 20 CROB block data as defined below
123 128 CROB 21 CROB block data as defined below
129 134 CROB 22 CROB block data as defined below
135 140 CROB 23 CROB block data as defined below
141 146 CROB 24 CROB block data as defined below
147 152 CROB 25 CROB block data as defined below
153 158 CROB 26 CROB block data as defined below
159 164 CROB 27 CROB block data as defined below
165 170 CROB 28 CROB block data as defined below
171 176 CROB 29 CROB block data as defined below
177 182 CROB 30 CROB block data as defined below
183 188 CROB 31 CROB block data as defined below
189 194 CROB 32 CROB block data as defined below

ProSoft Technology, Inc. Page 86 of 133

MVI56E-DNPNET

Word Offset Stop Data Field(s) Description

Start
195 200 CROB 33 CROB block data as defined below
201 206 CROB 34 CROB block data as defined below
207 212 CROB 35 CROB block data as defined below
213 218 CROB 36 CROB block data as defined below
219 224 CROB 37 CROB block data as defined below
225 230 CROB 38 CROB block data as defined below
231 236 CROB 39 CROB block data as defined below
237 242 CROB 40 CROB block data as defined below
243 248 Spare Not Used
249 249 Block ID This field contains the block identification code of 9910 for
the block.

The format of each 6 word data region in the block is as follows:

Word Offset Definitions Description

0 Point Number This field contains the BO point number for the following
CROB command.
1 Control Code Byte value Control Code of the CROB message received.
Control code 81 = trip, 41 = close, and 1 = pulse.
Count Byte value of number of pulses
2 to 3 On Time This double-word contains the ‘on’ time interval for the CROB
block.
4 to 5 Off Time This double-word contains the ‘off’ time interval for the CROB
block.

Block 9949: Request Server Communication Error Table

If the ControlLogix processor sends a block 9949, the MVI56E-DNPNET module
responds with a server communication error listing.
These data values are updated after each command processed by the module.
The block 9949 request is structured to retrieve data for up to 30 server units
each call. The format of the block sent from the ControlLogix processor to the
module is shown in the following table.

Word Offset Data Field(s) Description

in Block
0 Block ID This field contains the value of 9949 identifying the block type to
the module.
1 Number of This field contains the number of servers to report in the response
servers message. The value has a range of 1 to 30.
2 Start Server This parameter sets the index in the server array where to start.
Index The first server in the array has a value of 0. The last index in the
array has a value of (MaxServers -1).
3 to 247 Reserved Reserved for future use

ProSoft Technology, Inc. Page 87 of 133

MVI56E-DNPNET

each block. To insure that the block reached the module and was processed, the
module will send a response read block 9958 to the ControlLogix processor. The
following table describes the format of the block.

Word Offset Data Field(s) Description

in Block
0 Reserved Reserved
1 Block ID Block identification code for request from PLC by the module.
2 Event Count This field contains the number of events processed/received
Received by the module. (1 to 24)
3 Sequence Sequence counter received for each block transfer. Used to
Counter Received synchronize and confirm receipt of the block by the module.
This field contains the sequence counter of the last successful
block 9958 received.
4 to 248 Spare Not used
249 Block ID Identification code for block set to 9958.

The sequence counter field in the returned block is set to the last successfully
processed block 9958 from the ControlLogix processor. Compare this value to
that sent by the ControlLogix processor.
If the values match, the events can be removed from the ControlLogix processor.
If the values do not match, or the ControlLogix processor does not receive a
9958 block, the ControlLogix processor must re-send the block.

ProSoft Technology, Inc. Page 91 of 133

MVI56E-DNPNET

Block 9959: Analog Input Event With Calendar Time

Block identification code 9959 sends a set of analog input events with calendar
time to the module. The following table lists the block format of Analog Input
Events sent to the module from the ControlLogix processor.

Word Offset Data Field(s) Description

in Block
0 Block ID This field contains the value of 9959 identifying the event block
to the module.
1 Event Count This field contains the number of events contained in the
block. Valid values for this field are 1 to 20.
2 Sequence This field is used to hold the sequence counter for each 9959
Counter block transfer. This is used to synchronize and confirm receipt
of the block by the module.
(Begin Event #1)
3 Point_Number This is the data point in the DNPNET analog input database
represented by the event.
4 Class_Override Regardless of the Class defined for the given point number,
this will be the Class of the event. (1, 2, or 3)
5 to 6 Value Value of the point. 16-bit integer, 32-bit integer, or 32-bit float
can be packed into this space
7 Year Year of the event timestamp
8 Month Month of the event timestamp
9 Day Day of the event timestamp
10 Hour Hour of the event timestamp
11 Minute Minute of the event timestamp
12 Seconds Seconds of the event timestamp
13 Milliseconds Milliseconds of the event timestamp
14 Reserved
(Next 19 Events)
15 to 26 Ten words of data for Event #2
… … …
231 to 242 Ten words of data for Event #20
(End of Event
data)
243 to 247 Spare Not Used

ProSoft Technology, Inc. Page 92 of 133

MVI56E-DNPNET

Up to 20 events can be passed from the ControlLogix processor to the module in

each block. To insure that the block reached the module and was processed, the
module will send a response read block 9959 to the ControlLogix processor.

Word Offset Data Field(s) Description

in Block
0 Reserved Reserved(0)
1 Block ID Block identification code for request from PLC by the module.
2 Event Count This field contains the number of events processed/received
Received by the module.
3 Sequence Sequence counter Received for each block transfer, used to
Counter Received synchronize and confirm receipt of the block by the module.
This field contains the sequence counter of the last successful
block 9959 received.
4 to 248 Spare Not used
249 Block ID Identification code for block set to 9959.

The sequence counter field in the returned block is set to the last successfully
processed block 9959 from the ControlLogix processor. Compare this value to
that sent by the ControlLogix processor.
If the values match, the events can be removed from the ControlLogix processor.
If the values do not match, or the ControlLogix processor does not receive a
9959 block, the ControlLogix processor must re-send the block.

ProSoft Technology, Inc. Page 93 of 133

MVI56E-DNPNET

Block 9968: Binary Input Event With CLX Time

Block identification code 9968 sends a set of binary input events with
ControlLogix processor time to the module.

Word Offset Data Field(s) Description

in Block
0 Block ID This field contains the value of 9968 identifying the event
block to the module.
1 Event Count This field contains the number of events contained in the
block. Valid values for this field are 1 to 30.
2 Sequence Counter This field is used to hold the sequence counter for each
9968 block transfer. This is used to synchronize and confirm
receipt of the block by the module.
(Begin Event #1)
3 Point_Number This is the data point in the DNPNET binary input database
represented by the event.
4 Class_ Override Bits 0 and 1 are used for class override values of 1, 2, or 3
5 Value Value of the point, 0 or 1, of bit 0 of this 16-bit word. All other
bits are ignored.
6 Reserved
7 to 10 CLX_Time 64-bit Time as number of microseconds since Jan 1st, 1970
(Next 29 Events)
13 to 22 Ten words of data for Event #2
… … …
233 to 242 Ten words of data for Event #30
(End of Event Data)
243 to 247 Spare Not used

Up to 30 events can be passed from the ControlLogix processor to the module in

each block. To ensure that the block reached the module and was processed,
the module will send a response read block 9968 to the ControlLogix processor.
The following table describes the format of the block.

Word Offset Data Field(s) Description

in Block
0 Reserved Reserved (0)
1 Block ID Block identification code for request from PLC by the module.
2 Event Count This field contains the number of events processed/received
Received by the module.
3 Sequence This field contains the sequence counter of the last successful
Counter Received block 9968 received. Used to synchronize and confirm receipt
of the block by the module.
4 to 248 Spare Not used
249 Block ID Identification code for block set to 9968.

The sequence counter field in the returned block is set to the last successfully
processed block 9968 from the ControlLogix processor. Compare this value to
that sent by the ControlLogix processor.

ProSoft Technology, Inc. Page 94 of 133

MVI56E-DNPNET

If the values match, the events can be removed from the ControlLogix processor.
If the values do not match, or the ControlLogix processor does not receive a
9968 block, the ControlLogix processor must re-send the block. This block is
typically used to pass SOE data from a 1756-"SOE" module to the DNP server
event buffer of the MVI56E-DNPNET module. Upon successful receipt of the
data by the module, this data can then be cleared from the event queue of the
1756-"SOE" modules.

Block 9969: Analog Input Event With CLX Processor Time

Block identification code 9969 sends a set of analog input events with the
ControlLogix processor time to the module. The following table lists the block
format of Analog Input Events Request sent to the module from the ControlLogix
processor.

0 Reserved
1 Write block ID
2 to 241 Read data
242 to 248 Spare (Not used)
249 Read block ID

The Read Block ID is an index value used to determine the location of where the
data will be placed in the ControlLogix processor read data controller tag array.
Each transfer can move up to 240 words (block offsets 2 to 241) of data. The
value of the Read Block identification code identifies the type of data contained in
the block, so the sample ladder logic can move it to the correct controller tag
array.
The Write Block ID contained in the Read Block tells the ladder logic which block
of data the module is expecting to receive from the ControlLogix processor
during the next backplane transfer. Under normal program operation, the module
sequentially sends read blocks and requests write blocks. For example, if one
block each of binary and analog output data, one block of binary input data, two
blocks of counter data and two blocks of analog input data are used with the
application, the backplane transfer sequence block numbers will be:
R4W0 R16W8 R4W9 R16W12 R4W13 R16W0 R4W8
This sequence will continue until interrupted by other write block numbers sent by
the controller or by a command request from a node on the DNPNET network or
operator control through the module’s Configuration/Debug port. This sequence
is occasionally interrupted by the read block identification code 100. This block
passes the error/status and error list information from the module to the
processor. Refer to the Error/Status section of this document for the structure
and data contained in a Status Read block.

ProSoft Technology, Inc. Page 103 of 133

MVI56E-DNPNET

Write Block
WRITE blocks transfer information from the ControlLogix processor to the
module. The following table describes the structure of a typical output image
Write Block.

Block Offset Content

0 Write block ID
1 to 240 Write data
241 to 247 Spare (Not used)

The Write Block ID is an index value used to determine the location in the
module’s database where the data will be placed as defined in the table
presented in the previous section. Each transfer can move up to 240 words
(block offsets 1 to 240) of data.
In cases where the ladder logic uses Special Function Blocks, the normal Read
Block IDs and Write Block IDs will be replaced with a Special Function Block ID.
Once the Special Function has been processed, the module will resume the
normal data Read Block ID and Write Block ID sequence, starting from where the
sequence was interrupted.

Trip/Close
The MVI56E-DNPNET module supports Trip/Close functionality for the DNP
Binary Output points when operating as a server.
This allows Trip/Close commands to be sent to the MVI56E-DNPNET module as
a server, for dual point control. Each DNPNET Trip/Close command will occupy 2
bits within the module memory.
This does overlap the regular pulse on/off and latch on/off Binary Output
database, therefore special consideration must be used to make sure that points
are not used twice.

The following table describes the address mapping for the module using Latch
and Pulse commands, and Trip/Close functionality.

DNPNET BO Database Point BO Latch/Pulse Point BO Trip/Close Point

0 BO 0 Close BO 0
1 BO 1 Trip BO 0
2 BO 2 Close BO 1
3 BO 3 Trip BO 1
4 BO 4 Close BO 2
5 BO 5 Trip BO 2
100 BO 100 Close BO 50
101 BO 101 Trip BO 50
1000 BO 1000 Close BO 500
1001 BO 1001 Trip BO 500
2000 BO 2000 Close BO 1000
2001 BO 2001 Trip BO 1001
3000 BO 3000 Close BO 1500

ProSoft Technology, Inc. Page 104 of 133

MVI56E-DNPNET

DNPNET BO Database Point BO Latch/Pulse Point BO Trip/Close Point

3001 BO 3001 Trip BO 1501
...and so on...
7998 BO 7998 Close BO 3998
7999 BO 7999 Trip BO 3999
The trip/close values require 2 points within the module’s DNPNET database. A
Trip is represented by the binary value of '10' for those 2 points, and a Close is
represented by the binary value of '01' for those same 2 points.
The module can process only 4000 trip/close dual points, as the database for the
DNPNET BO is limited to 8000 total bits.
The dual point control on trip/close operations can be overwritten by selecting the
parameter of "Use_TripClose_Single_Point" in the server configuration section of
the module. When this parameter is enabled, all trip and close operations will be
treated as pulse on commands, and only occupy a single boolean point.

4.3.2 DNPNETModuleDef Object

This object contains all the MVI56E-DNPNET module top-level data.

Name Description
CONFIG DNPNET module configuration parameters for blocks 9000 - 9099
DATA Client and server data transferred between the processor and the module
STATUS Status for various functionalities
CONTROL Governs the data movement between the PLC rack and the module
UTIL Generic tags used for internal ladder processing (DO NOT MODIFY)

4.3.3 DNPNETCONFIG Object

This object contains the data types that apply to the configuration of the module.

Name Description
DNP_Module_Name Module name description
DNP3_Server Server configuration
DNP3_WhiteList IP addresses of the Clients that the MVI56E-DNPNET Server will
respond to.
DNP3_Client Client configuration
DNP_Server_Override Assigning Class and Deadband overrides to individual point types.
DNP_Server_List List of servers the MVI56E-DNPNET Client connects to
DNP_Client_Commands List of commands the MVI56E-DNPNET Client sends to servers
IP_Settings IP Settings of module

ProSoft Technology, Inc. Page 105 of 133

MVI56E-DNPNET

4.3.4 DNPNETCONTROL Object

This object contains values that are a 'scratchpad' area of intermediate data
storage variables. They are used by the AOI to keep track of various logic
processing functions.
Name Variable Description
Events Handling the transfer of
events from the Events
Message Buffer in the Client
to the PLC.
EventMessages Events Captured by DNP
Client are moved to this
structure
CROBmsg_counter CROB message data copied
via block 9910 from DNP
Server. CROBmsg_counter
tags are status data used
when MVI56E-DNPNET is
configured as a server and
passes the CROB message
counter information to the
sub CROBmsg_counter tags
through the backplane.
CROBmsg_counter.OneShot Internally used in Add On
Instruction (not designed to
be used by the end user.
CROBmsg_counter.CountPerBlock Number of CROB command
message(s) that was (were)
contained in the last 9910
Backplane Block received in
the Add On Instruction.
CROBmsg_counter.CCC Continuous CROB message
Count. Everytime CROB
message is received by the
server, this counter will
increment by 1. This may be
reset by the user. Otherwise,
it will be reset to 0 on the
2147483646th CROB
message coming into the
server by the Add On
Instruction.
CROBmsg_counter.CBCC Continuous CROB message
Block Count. Everytime
9910 block is received by
the Add On Instruction, this
counter increments by 1.
This may be reset by the
user. Otherwise it will be
reset to 0 on the
2147483646th CROB
message coming into the
server by the Add On
Instruction.

ProSoft Technology, Inc. Page 106 of 133

MVI56E-DNPNET

CROBmsg_data CROB message data copied

via block 9910 from
DNPServer.
CROBmsg_data tags are
status data used when the
MVI56E-DNPNET is
configured as a server and
passes the CROB message
counter information to the
sub CROBmsg_counter tags
through the backplane.
CROBmsg_data.Point_Number This parameter was
specified by the DNP client
as the Control Relay Output
Block point in the MVI56E-
DNPNET (configured as a
server).
CROBmsg_data.Control_Code This is a standard DNPNET
protocol control code byte
(see description on page
98).
CROBmsg_data.count This parameter was
specified by the DNP3 client
of the number of pulses to
generate for pulse output
control in the CROB
command.
CROBmsg_data.On_Time This parameter was
specified by the DNP3 client
of the on-time interval for
pulse control in the CROB
command.
CROBmsg_data.Off_Time This parameter was
specified by the DNP3 client
of the off-time interval for
pulse control in the CROB
command.
Binary_Event_CalTime For storing block 9958
Binary Event Messages to
be sent to DNP Server.
Analog_Event_CalTime For storing block 9959
Analog Event Messages to
be sent to DNP Server.
Binary_Event_CLXTime For storing Block 9968
Binary Input Events with
CLX Time
Analog_Event_CLXTime For storing Block 9969
Binary Input Events with
CLX Time.
Get_Module_Time Reads the module time into
the PLC
Set_Module_Time Sends the PLC time to the
module.

ProSoft Technology, Inc. Page 107 of 133

MVI56E-DNPNET

CROB_Commands 9901 block of CROB

Commands
Aux_Commands 9904 block for Auxiliary
Client commands
Command_Enable 9902 block of commands to
enable
Server_Comm_Errors Count and offset of servers
to report
Command_Errors Count and offset of
commands to report
ColdBoot Cold boot the module via
block 9999
WarmBoot Warm boot the module via
block 9998

4.3.5 DNPNETDATA Object

This object stores all the process-related data for a MVI56E-DNPNET module.
This includes data for the primary DNPNET server port (DNPNET data set) and
the data received from or sent to DNP3 Ethernet server devices (IED data set) by
the secondary DNPNET port when configured as a DNP3 Ethernet Client.
Contained within this data object is an array for each possible data type. The
array sizes are set to match the maximum possible module configuration. If
multiple MVI56E-DNPNET modules are used within a rack, a copy of this
structure will have to be made to permit each module to have its own databases.
Each data type has its own set of unique block identification codes to distinguish
the data contained in the read or write block.

Name Description
DNPout Module's Server Database. Remote Clients Write into this DB.
IEDin Module's Client Database. The Client writes data into this DB that it
Reads from remote Servers
DNPin Module's Server Database. Remote Clients Read from this DB.
IEDout Module's Client Database. The Client reads data from this DB and
Writews it to remote Servers.

4.3.6 DNPNETSTATUS Object

This object stores all status information of the module including client and server
status.

Name Description
GenStat General status information
ErrList List of last 60 DNPNET module errors
IINServerBits IIN Bits received from Servers
ServerCommErrors Server communication errors list
CommandErrors Command errors list

ProSoft Technology, Inc. Page 108 of 133

MVI56E-DNPNET

4.3.7 DNPNETUTIL Object

This object contains variables for internal AOI usage and should not be accessed
by user application.

Name Description
LastRead Index of last read block
LastWrite Index of last write block
BlockIndex Computed block offset for data table
ReadData Buffer File for data Read from Module
WriteData Buffer File for data Written to Module
OffsetCounter For calculating buffer copy offset
CopyLength For calculating buffer copy length
LastService For keeping track of last special outgoing block serviced
Mutex Only one special block gets serviced every other scan
OddScan Keep track of every other scan
FirstRun Ensures database counts are correct every time the PLC restarts
DNP_List_Entry_Counts Lengths of the seven DNPNET Client List Data
IED_Database Configure the Client database sizes
DNP_Server_Database Configured Server database sizes

ProSoft Technology, Inc. Page 109 of 133

MVI56E-DNPNET

4.4 MVI56E-DNPNET User Defined Data Types

Several UDTs are defined in the MVI56E-DNPNET Add-On Instruction.
The main UDT, DNPNETMODULEDEF, contains all the data types for the
module. It is used to create the main controller tag structure, DNPNET.
There are five UDTs one level below DNPNETMODULEDEF. These lower-level
UDTs were used to create the DNPNET.CONFIG, DNPNET.DATA,
DNPNET.STATUS, DNPNET.CONTROL, and DNPNET.UTIL controller tag
structures.

Click the [+] signs to expand the UDT structures and view lower-level UDTs. For
example, when DATA is expanded, it contains four UDTs: DNPout, IEDin,
DNPin, and IEDout. They can further be expanded with the [+] sign.

Notice these UDTs are the data types used to declare the DNPNET.DATA
controller tag arrays.

ProSoft Technology, Inc. Page 110 of 133

MVI56E-DNPNET

4.4.1 DNPNET.CONFIG Controller Tags

This UDT structure contains the data types that apply to the configuration of the
module. Refer to DNPNET Controller Tags Definitions (page 22) for a complete
description of each element in this object.

Name Data Type Description

DNP_Module_Name SINT[40] Module Definition
DNP3_Server DNPNET_Server_Parameters Server configuration
DNP3_WhiteList DNPNET_Whitelist_IP_Address[10] IP addresses of clients server
will respond to
DNP3_Client DNPNET_Client_Parameters Client configuration
DNP3_Server_Override DNPNET_Override Assigning Class and Deadband
Override to individual point
types.
DNP_Server_List DNPNET_Server_List[5] List of servers the Client
connects to
DNP_Client_Commands DNPNET_Client_Commands[5] List of commands the Client
sends to servers
IP_Settings DNPNET_Module_IP_Addressing IP Settings of module

4.5.1 Ethernet Cable Specifications

The recommended cable is Category 5 or better. A Category 5 cable has four
twisted pairs of wires, which are color-coded and cannot be swapped. The
module uses only two of the four pairs.
The Ethernet port or ports on the module are Auto-Sensing. You can use either a
standard Ethernet straight-through cable or a crossover cable when connecting
the module to an Ethernet hub, a 10/100 Base-T Ethernet switch, or directly to a
PC. The module detects the cable type and uses the appropriate pins to send
and receive Ethernet signals.
Some hubs have one input that can accept either a straight-through or crossover
cable, depending on a switch position. In this case, you must ensure that the
switch position and cable type agree.
Refer to Ethernet Cable Configuration (page 116) for a diagram of how to
configure Ethernet cable.

4.5.2 Ethernet Cable Configuration

Note: The standard connector view shown is color-coded for a straight-through cable.

Crossover cable Straight- through cable

RJ-45 PIN RJ-45 PIN RJ-45 PIN RJ-45 PIN
1 Rx+ 3 Tx+ 1 Rx+ 1 Tx+
2 Rx- 6 Tx- 2 Rx- 2 Tx-
3 Tx+ 1 Rx+ 3 Tx+ 3 Rx+
6 Tx- 2 Rx- 6 Tx- 6 Rx-

4.5.3 Ethernet Performance

Ethernet performance in the MVI56E-DNPNET can be affected in the following
way:
 Accessing the web interface (refreshing the page, downloading files, and so
on) may affect performance
 Also, high Ethernet traffic may impact performance, so consider one of these
options:
o Use managed switches to reduce traffic coming to module port
o Use CIPconnect for these applications and disconnect the module
Ethernet port from the network

ProSoft Technology, Inc. Page 116 of 133

MVI56E-DNPNET

DNPNET V2.00
DEVICE PROFILE DOCUMENT
Vendor Name: ProSoft Technology, Inc.
Device Name: MVI56E-DNPNET (VERSION 2.00)
Highest DNPNET Level Supported: Device Function:
For Request: L2 Server & Client
For Responses: L2
Notable objects, functions, and/or qualifiers supported in addition to the highest DNPNET level stated above (see attached
table for complete list).

Definition of selected IIN bits:

Device Trouble - PLC data transfer operation is not taking place
Configuration Error - User specified point or event count is too high for application (can correct only by changing
configuration in PLC).

The following features are configurable on the module:

Collision avoidance, time sync before events are generated and default analog input events, Obj32V4 or O32V2, select
option. Floating-point variations are supported for analog input and output objects (both single and double floating-point
types). Support for Obj110 (octet string) available only using read function.

Cable Connections • 116 G

Clearing a Fault Condition • 38
Communication Error Codes • 61 General Command Errors • 61
Connect to the Module’s Web Page • 37, 66 General Concepts of MVI56E-DNPNET Data Transfer
Connecting Your PC to the Module • 43, 54, 66 • 70
Connecting Your PC to the Module's Ethernet Port • 54 General Specifications • 67
Contacting Technical Support • 131 H
Creating a New RSLogix 5000 Project • 9
Creating the Module • 10 Hardware Specifications • 70

D I
Data Flow Between the DNP3 Ethernet network, Importing the Add-On Instruction • 13
MVI56E-DNPNET Module, and ControlLogix Installing ProSoft Configuration Builder • 40
Processor • 72 Installing the Module in the Rack • 8
Diagnostics and Troubleshooting • 36, 37
DNP3 Ethernet Client Backplane Data Flow • 74

ProSoft Technology, Inc. Page 132 of 133

MVI56E-DNPNET

M
Main Logic Loop • 71
Module Function Blocks • 77
Monitoring MVI56E-DNPNET Class Assignments
Information • 60
Monitoring MVI56E-DNPNET Deadband Assignments
Information • 60
Monitoring Backplane Information • 57
Monitoring DNP3 Ethernet Data Values • 61
Monitoring General Information • 57
Monitoring MVI56E-DNPNET Client Information • 59
Monitoring MVI56E-DNPNET Information • 59
MVI56E-DNPNET Backplane Data Exchange • 70
MVI56E-DNPNET Configuration • 21
MVI56E-DNPNET Database Overview • 99
MVI56E-DNPNET User Defined Data Types • 110

N
Non-Scrolling LED Status Indicators • 38
Normal Data Transfer • 100

P
Package Contents • 7
Port Configuration Errors • 64
Product Specifications • 67

R
Read Block • 103
Reference • 67

S
Scrolling LED Status Indicators • 37
Setting Jumpers • 7
Setting Up ProSoft Configuration Builder • 40
Setting Up the Project • 41
Slave Port Communication Errors • 62
Special Function Blocks • 81
Start Here • 6
Support, Service & Warranty • 131
System Configuration Errors • 63
System Requirements • 6

T
The Diagnostics Menu • 57
Trip/Close • 104
Troubleshooting • 39

U
Using CIPconnect® to Connect to the Module • 43, 53,
55
Using RSWho to Connect to the Module • 53
Using the Diagnostics Menu in ProSoft Configuration
Builder • 54

W
Warranty Information • 131
Write Block • 104

ProSoft Technology, Inc. Page 133 of 133

Mvi56e Mnet Mnetxt Um
No ratings yet
Mvi56e Mnet Mnetxt Um
152 pages
Mvi56e Mnetc Mnetcxt Um
No ratings yet
Mvi56e Mnetc Mnetcxt Um
163 pages
Mvi56 Mnet User Manual1
No ratings yet
Mvi56 Mnet User Manual1
98 pages
MVI56E - MCM Manual
No ratings yet
MVI56E - MCM Manual
215 pages
Mvi56e Mnetcr Um
No ratings yet
Mvi56e Mnetcr Um
143 pages
Manual Modulo Prosoft CLGX To Modbus Mvi56
No ratings yet
Manual Modulo Prosoft CLGX To Modbus Mvi56
92 pages
MVI56E AFC Installer Certification Requirements
No ratings yet
MVI56E AFC Installer Certification Requirements
27 pages
Mvi69E-Mbs: User Manual
No ratings yet
Mvi69E-Mbs: User Manual
161 pages
Mvi56e MCM MCMXT Um001
No ratings yet
Mvi56e MCM MCMXT Um001
209 pages
Comunicacion Siemens - Allen Bradley
No ratings yet
Comunicacion Siemens - Allen Bradley
168 pages
Mvi56e Mnetr Um
No ratings yet
Mvi56e Mnetr Um
147 pages
Mvi56E-Mnetc/Mnetcxt: User Manual
No ratings yet
Mvi56E-Mnetc/Mnetcxt: User Manual
162 pages
Mvi69E-Mbtcp: User Manual
No ratings yet
Mvi69E-Mbtcp: User Manual
150 pages
Mvi56-Dnpsnet: User Manual
No ratings yet
Mvi56-Dnpsnet: User Manual
125 pages
MVI56E MCMMCMXT User Manual PDF
No ratings yet
MVI56E MCMMCMXT User Manual PDF
199 pages
Mvi56 Mnet User Manual PDF
No ratings yet
Mvi56 Mnet User Manual PDF
143 pages
Mvi56e MCMMCMXT User Manual
No ratings yet
Mvi56e MCMMCMXT User Manual
217 pages
Mvixxe Afc SCG
No ratings yet
Mvixxe Afc SCG
151 pages
Mvi56E-Gec: User Manual
No ratings yet
Mvi56E-Gec: User Manual
77 pages
Mvi56e MCM MCMXT Um PDF
No ratings yet
Mvi56e MCM MCMXT Um PDF
205 pages
Mvi56e Mnetr Setup Guide
No ratings yet
Mvi56e Mnetr Setup Guide
78 pages
PLX51 DNPS Um
No ratings yet
PLX51 DNPS Um
139 pages
Plx82 Eip PNC User Manual
No ratings yet
Plx82 Eip PNC User Manual
153 pages
PLX82 Mnet 61850 Um
No ratings yet
PLX82 Mnet 61850 Um
172 pages
Mvi56 Mnetc User Manual
No ratings yet
Mvi56 Mnetc User Manual
153 pages
PLX3x UM001
No ratings yet
PLX3x UM001
215 pages
Plx51 Dnps Um
No ratings yet
Plx51 Dnps Um
148 pages
Prolinx Modbus Ethernet Manual
No ratings yet
Prolinx Modbus Ethernet Manual
135 pages
Plx32 Eip MBTCP Ua Um
No ratings yet
Plx32 Eip MBTCP Ua Um
153 pages
Mvi56 Wa PWP User Manual
No ratings yet
Mvi56 Wa PWP User Manual
91 pages
ICX35-HWC UserManual
No ratings yet
ICX35-HWC UserManual
142 pages
Mvi46 Pdpmv1 User Manual
No ratings yet
Mvi46 Pdpmv1 User Manual
160 pages
Gateway
No ratings yet
Gateway
166 pages
Mvi56e MCMMCMXT Setup Guide
No ratings yet
Mvi56e MCMMCMXT Setup Guide
78 pages
PLX31 Manual
No ratings yet
PLX31 Manual
198 pages
PLX3x UserManual
No ratings yet
PLX3x UserManual
209 pages
PLX3x UM
No ratings yet
PLX3x UM
198 pages
PLX3x Series: User Manual
No ratings yet
PLX3x Series: User Manual
193 pages
3100 3150 MCM User Manual
No ratings yet
3100 3150 MCM User Manual
130 pages
PLX82-EIP-61850: User Manual
No ratings yet
PLX82-EIP-61850: User Manual
139 pages
Manual Mvi46 MCM
No ratings yet
Manual Mvi46 MCM
108 pages
PLX3x User Manual
No ratings yet
PLX3x User Manual
222 pages
MVI56-MCM: User Manual
No ratings yet
MVI56-MCM: User Manual
159 pages
Mvi46 Mnet User Manual
No ratings yet
Mvi46 Mnet User Manual
93 pages
MVI56E-MCMR Quickstart
No ratings yet
MVI56E-MCMR Quickstart
2 pages
PLX8x EIP 61850 User Manual
No ratings yet
PLX8x EIP 61850 User Manual
184 pages
Mvi69 DNP User Manual
No ratings yet
Mvi69 DNP User Manual
129 pages
PROSOFT PLX8x EIP 61850 User Manual
No ratings yet
PROSOFT PLX8x EIP 61850 User Manual
167 pages
Mvi56e MCMR Um
No ratings yet
Mvi56e MCMR Um
204 pages
PLX3x UserManual
No ratings yet
PLX3x UserManual
211 pages
PLX30 User Manual
No ratings yet
PLX30 User Manual
200 pages
Mvi56e GSC User Manual
No ratings yet
Mvi56e GSC User Manual
155 pages
MVI56E-61850C UserManual
No ratings yet
MVI56E-61850C UserManual
121 pages
ICX35-HWC: User Manual
No ratings yet
ICX35-HWC: User Manual
131 pages
Informe
No ratings yet
Informe
3 pages
3170 MBS User Manual PDF
No ratings yet
3170 MBS User Manual PDF
55 pages
PLX3x User Manual
No ratings yet
PLX3x User Manual
218 pages
PLX3x UM
No ratings yet
PLX3x UM
205 pages
Mvi56 MCM User Manual
No ratings yet
Mvi56 MCM User Manual
193 pages
630 Series: DNP3 Communication Protocol Manual
No ratings yet
630 Series: DNP3 Communication Protocol Manual
48 pages
KTA-282 Modbus TCP Weather Station Gateway: Quick View
No ratings yet
KTA-282 Modbus TCP Weather Station Gateway: Quick View
26 pages
AGC-4 Modbus Function Codes Guide
No ratings yet
AGC-4 Modbus Function Codes Guide
20 pages
630 Series: DNP3 Point List Manual
No ratings yet
630 Series: DNP3 Point List Manual
72 pages
Agc-4 Modbus Tables 4189341215 Uk
No ratings yet
Agc-4 Modbus Tables 4189341215 Uk
57 pages
User Manual: Optc6 Canopen Option Board For 9000X Drive
No ratings yet
User Manual: Optc6 Canopen Option Board For 9000X Drive
52 pages
User Manual: Ethernet/Ip Option Board Optck For 9000X Drives
No ratings yet
User Manual: Ethernet/Ip Option Board Optck For 9000X Drives
80 pages
Cumulative Tests A - Answer Keys Units 1-5: Grammar
100% (1)
Cumulative Tests A - Answer Keys Units 1-5: Grammar
5 pages
Square-Square-roots Text Marked
No ratings yet
Square-Square-roots Text Marked
5 pages
CS106 Week 02
No ratings yet
CS106 Week 02
55 pages
JavaScript JSON Cookbook - Sample Chapter
100% (3)
JavaScript JSON Cookbook - Sample Chapter
24 pages
ABB Smart Sensor
No ratings yet
ABB Smart Sensor
4 pages
Dsa All Notes Before Midterm
No ratings yet
Dsa All Notes Before Midterm
4 pages
CCIDF Lab Manual r22 3-2 @sri Indu College
No ratings yet
CCIDF Lab Manual r22 3-2 @sri Indu College
39 pages
Crash Report
No ratings yet
Crash Report
176 pages
Kajal Kumar I
No ratings yet
Kajal Kumar I
24 pages
Trust PW 4060T Datasheet - en
No ratings yet
Trust PW 4060T Datasheet - en
2 pages
Feasibility Study Template
No ratings yet
Feasibility Study Template
5 pages
Intec Cs4 5000 Basic Manual Uk Final
No ratings yet
Intec Cs4 5000 Basic Manual Uk Final
78 pages
Nonprofit Cloud Consultant Training Guide
No ratings yet
Nonprofit Cloud Consultant Training Guide
201 pages
DNS Free Fire Max?
No ratings yet
DNS Free Fire Max?
11 pages
Google Hacking Techniques Overview
100% (2)
Google Hacking Techniques Overview
157 pages
An Analysis Case Study On Dell Direct-To-Consumer Model
No ratings yet
An Analysis Case Study On Dell Direct-To-Consumer Model
15 pages
RFP Risl
No ratings yet
RFP Risl
146 pages
Oracle FCCM Certification Updates
No ratings yet
Oracle FCCM Certification Updates
5 pages
Dapr For .NET Developers
No ratings yet
Dapr For .NET Developers
129 pages
TikTok's Political Impact Explored
No ratings yet
TikTok's Political Impact Explored
4 pages
Cs One Mark QP Set 001
No ratings yet
Cs One Mark QP Set 001
17 pages
Internship Report
No ratings yet
Internship Report
21 pages
Emergency Services Radio Guide
No ratings yet
Emergency Services Radio Guide
3 pages
Understanding Articles and Determiners
No ratings yet
Understanding Articles and Determiners
10 pages
DS1703 CV Unit1
No ratings yet
DS1703 CV Unit1
36 pages
RecoverPoint With SRM
No ratings yet
RecoverPoint With SRM
63 pages
Industrial Training
No ratings yet
Industrial Training
12 pages
Automated Plant Watering Report
No ratings yet
Automated Plant Watering Report
41 pages
Voice Over IP First-Step - Kevin Wallace - First-Step Series, Indianapolis, Ind, c2006 - Cisco Press - 9781587201561 - Anna's Archive
100% (1)
Voice Over IP First-Step - Kevin Wallace - First-Step Series, Indianapolis, Ind, c2006 - Cisco Press - 9781587201561 - Anna's Archive
340 pages
Semester Project Requirements
No ratings yet
Semester Project Requirements
3 pages