MVI46-DFNT
SLC Platform
EtherNet/IP Client/Server
Communication Module
October 12, 2010
USER MANUAL
Your Feedback Please
We always want you to feel that you made the right decision to use our products. If you have suggestions, comments,
compliments or complaints about our products, documentation, or support, please write or call us.
How to Contact Us
ProSoft Technology
5201 Truxtun Ave., 3rd Floor
Bakersfield, CA 93309
+1 (661) 716-5100
+1 (661) 716-5101 (Fax)
www.prosoft-technology.com
support@prosoft-technology.com
Copyright © 2010 ProSoft Technology, Inc., all rights reserved.
MVI46-DFNT User Manual
October 12, 2010
ProSoft Technology
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.
®
, ProLinx ®, inRAx ®, ProTalk ®, and RadioLinx ® are Registered Trademarks of ProSoft
ProSoft Technology® Product Documentation
In an effort to conserve paper, ProSoft Technology no longer includes printed manuals with our product shipments.
User Manuals, Datasheets, Sample Ladder Files, and Configuration Files are provided on the enclosed CD-ROM,
and are available at no charge from our web site: www.prosoft-technology.com
Printed documentation is available for purchase. Contact ProSoft Technology for pricing and availability.
North America: +1.661.716.5100
Asia Pacific: +603.7724.2080
Europe, Middle East, Africa: +33 (0) 5.3436.87.20
Latin America: +1.281.298.9109
Important Installation Instructions
Power, Input, and Output (I/O) wiring must be in accordance with Class I, Division 2 wiring methods, Article 501-4 (b)
of the National Electrical Code, NFPA 70 for installation in the U.S., or as specified in Section 18-1J2 of the Canadian
Electrical Code for installations in Canada, and in accordance with the authority having jurisdiction. The following
warnings must be heeded:
A WARNING - EXPLOSION HAZARD - SUBSTITUTION OF COMPONENTS MAY IMPAIR SUITABILITY FOR
CLASS I, DIV. 2;
B WARNING - EXPLOSION HAZARD - WHEN IN HAZARDOUS LOCATIONS, TURN OFF POWER BEFORE
REPLACING OR WIRING MODULES
C WARNING - EXPLOSION HAZARD - DO NOT DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN
SWITCHED OFF OR THE AREA IS KNOWN TO BE NON-HAZARDOUS.
D THIS DEVICE SHALL BE POWERED BY CLASS 2 OUTPUTS ONLY.
MVI (Multi Vendor Interface) Modules
WARNING - EXPLOSION HAZARD - DO NOT DISCONNECT EQUIPMENT UNLESS POWER HAS BEEN
SWITCHED OFF OR THE AREA IS KNOWN TO BE NON-HAZARDOUS.
AVERTISSEMENT - RISQUE D'EXPLOSION - AVANT DE DÉCONNECTER L'ÉQUIPEMENT, COUPER LE
COURANT OU S'ASSURER QUE L'EMPLACEMENT EST DÉSIGNÉ NON DANGEREUX.
Warnings
North America Warnings
A Warning - Explosion Hazard - Substitution of components may impair suitability for Class I, Division 2.
B Warning - Explosion Hazard - When in Hazardous Locations, turn off power before replacing or rewiring
modules.
Warning - Explosion Hazard - Do not disconnect equipment unless power has been switched off or the area is
known to be nonhazardous.
C Suitable for use in Class I, division 2 Groups A, B, C and D Hazardous Locations or Non-Hazardous Locations.
ATEX Warnings and Conditions of Safe Usage:
Power, Input, and Output (I/O) wiring must be in accordance with the authority having jurisdiction
A Warning - Explosion Hazard - When in hazardous locations, turn off power before replacing or wiring modules.
B Warning - Explosion Hazard - Do not disconnect equipment unless power has been switched off or the area is
known to be non-hazardous.
C These products are intended to be mounted in an IP54 enclosure. The devices shall provide external means to
prevent the rated voltage being exceeded by transient disturbances of more than 40%. This device must be used
only with ATEX certified backplanes.
D DO NOT OPEN WHEN ENERGIZED.
Warning: This module is not hot-swappable! Always remove power from the rack before inserting or removing this
module, or damage may result to the module, the processor, or other connected devices.
Battery Life Advisory
The MVI46, MVI56, MVI56E, MVI69, and MVI71 modules use a rechargeable Lithium Vanadium Pentoxide battery to
backup the real-time clock and CMOS. The battery should last for the life of the module. The module must be
powered for approximately twenty hours before the battery becomes fully charged. After it is fully charged, the battery
provides backup power for the CMOS setup and the real-time clock for approximately 21 days. When the battery is
fully discharged, the module will revert to the default BIOS and clock settings.
Note: The battery is not user replaceable.
Markings
Electrical Ratings
Backplane Current Load: 800 mA @ 5 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: 30g Operational; 50g non-operational; Vibration: 5 g from 10 Hz to 150 Hz
Relative Humidity 5% to 95% (without condensation)
All phase conductor sizes must be at least 1.3 mm(squared) and all earth ground conductors must be at least
4mm(squared).
Label Markings
Agency Approvals and
CertificationsANSI / ISA
CSA/cUL C22.2 No. 213-1987
CSA CB Certified IEC61010
ATEX EN60079-0 Category 3, Zone 2
ISA 12.12.01 Class I Division 2, GPs A, B, C, D
EN60079-15
243333
MVI46-DFNT ♦ SLC Platform Contents
EtherNet/IP Client/Server Communication Module User Manual
Contents
Your Feedback Please ........................................................................................................................ 2
How to Contact Us .............................................................................................................................. 2
ProSoft Technology® Product Documentation .................................................................................... 2
Important Installation Instructions ....................................................................................................... 3
MVI (Multi Vendor Interface) Modules ................................................................................................ 3
Warnings ............................................................................................................................................. 3
Battery Life Advisory ........................................................................................................................... 3
Markings .............................................................................................................................................. 4
Guide to the MVI46-DFNT User Manual 9
1 Start Here 11
1.1 System Requirements ............................................................................................. 12
1.2 Package Contents ................................................................................................... 13
1.3 Installing ProSoft Configuration Builder Software ................................................... 14
1.4 Setting Jumpers ...................................................................................................... 15
1.5 Installing the Module in the Rack ............................................................................ 16
1.6 Connecting your PC to the Processor ..................................................................... 17
1.7 Downloading the Sample Program to the Processor .............................................. 18
1.7.1 Configuring the RSLinx Driver for the PC COM Port .............................................. 19
1.8 Connecting Your PC to the Module ......................................................................... 21
2 Configuring the MVI46-DFNT Module 23
2.1 Using ProSoft Configuration Builder ....................................................................... 24
2.1.1 Setting Up the Project ............................................................................................. 24
2.1.2 Renaming PCB Objects .......................................................................................... 26
2.2 [Module] ................................................................................................................... 27
2.2.1 Module Name .......................................................................................................... 27
2.2.2 M1 Write Size .......................................................................................................... 27
2.2.3 Failure Flag Count ................................................................................................... 27
2.2.4 Initialize Output Data ............................................................................................... 27
2.2.5 DFNT Server File Size ............................................................................................ 27
2.2.6 Float Write Start ...................................................................................................... 28
2.2.7 Float Write Count .................................................................................................... 28
2.3 [DFNT Client x] ........................................................................................................ 29
2.3.1 Minimum Command Delay ...................................................................................... 29
2.3.2 Response Timeout .................................................................................................. 29
2.3.3 Retry Count ............................................................................................................. 29
2.4 [DFNT Client x Commands] .................................................................................... 30
2.4.1 Command List ......................................................................................................... 30
2.4.2 Command Entry Formats ........................................................................................ 33
2.5 [DF1 Pass-Through Server Port 1] .......................................................................... 37
2.5.1 Enabled ................................................................................................................... 37
2.5.2 Service Port Number ............................................................................................... 37
2.5.3 Busy Timeout .......................................................................................................... 37
2.5.4 Baud Rate ............................................................................................................... 37
ProSoft Technology, Inc. Page 5 of 177
October 12, 2010
Contents MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
2.5.5 Parity ....................................................................................................................... 38
2.5.6 Data Bits ................................................................................................................. 38
2.5.7 Stop Bits .................................................................................................................. 38
2.5.8 RTS On ................................................................................................................... 38
2.5.9 RTS Off ................................................................................................................... 38
2.5.10 Use CTS Line.......................................................................................................... 38
2.6 [DF1 Pass-Through Port] ........................................................................................ 39
2.6.1 Enabled ................................................................................................................... 39
2.6.2 Local Station ID....................................................................................................... 39
2.6.3 Protocol ................................................................................................................... 39
2.6.4 Termination Type .................................................................................................... 39
2.6.5 Baud Rate - 1200 to 38400 ..................................................................................... 40
2.6.6 Parity ....................................................................................................................... 40
2.6.7 Data Bits ................................................................................................................. 40
2.6.8 Stop Bits .................................................................................................................. 40
2.6.9 RTS On ................................................................................................................... 40
2.6.10 RTS Off ................................................................................................................... 40
2.6.11 Use CTS Line.......................................................................................................... 41
2.6.12 Retry Count ............................................................................................................. 41
2.6.13 Request Timeout .................................................................................................... 41
2.6.14 Busy Timeout .......................................................................................................... 41
2.6.15 ACK Timeout........................................................................................................... 41
2.7 Ethernet Configuration ............................................................................................ 42
2.8 Downloading the Project to the Module Using a Serial COM port .......................... 43
2.9 Ladder Logic ........................................................................................................... 44
2.9.1 Module Data............................................................................................................ 44
2.9.2 Adding the Module to an Existing Project ............................................................... 44
3 Diagnostics and Troubleshooting 47
3.1 LED Status Indicators ............................................................................................. 48
3.1.1 Ethernet LED Indicators .......................................................................................... 51
3.1.2 Clearing a Fault Condition ...................................................................................... 52
3.1.3 Troubleshooting ...................................................................................................... 52
3.2 Using ProSoft Configuration Builder (PCB) for Diagnostics ................................... 53
3.2.1 Using the Diagnostic Window in ProSoft Configuration Builder ............................. 53
3.2.2 Navigation ............................................................................................................... 55
3.2.3 Main Menu .............................................................................................................. 56
3.2.4 Database View Menu .............................................................................................. 60
3.2.5 Master Command Error List Menu.......................................................................... 62
3.2.6 Master Command List Menu ................................................................................... 63
3.2.7 Network Menu ......................................................................................................... 64
3.3 Reading Status Data from the Module ................................................................... 66
4 Reference 67
4.1 Product Specifications ............................................................................................ 68
4.1.1 EtherNet/IP (Explicit Messaging) Compatible Devices ........................................... 68
4.1.2 General Specifications ............................................................................................ 68
4.1.3 Hardware Specifications ......................................................................................... 69
4.1.4 Functional Specifications ........................................................................................ 70
4.2 Functional Overview ............................................................................................... 71
4.2.1 General Concepts ................................................................................................... 71
Page 6 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Contents
EtherNet/IP Client/Server Communication Module User Manual
4.2.2 Module Control Blocks (4000 to 4999) .................................................................... 72
4.2.3 Data Flow between MVI46-DFNT Module and SLC Processor .............................. 75
4.3 Cable Connections .................................................................................................. 81
4.3.1 Ethernet Connection ................................................................................................ 81
4.3.2 RS-232 Configuration/Debug Port .......................................................................... 82
4.3.3 DB9 to RJ45 Adaptor (Cable 14) ............................................................................ 84
4.4 Pass-Through Ports ................................................................................................ 85
4.5 MVI46-DFNT Status Data Definition ....................................................................... 86
4.5.1 HTTP Port 80 Status ............................................................................................... 86
4.5.2 DFNT Client 0 Status .............................................................................................. 87
4.5.3 Block Status ............................................................................................................ 87
4.5.4 Pass-Through Server Status ................................................................................... 88
4.5.5 DFNT Server 0 Status ............................................................................................. 90
4.5.6 DFNT Server 1 Status ............................................................................................. 91
4.5.7 DFNT Server 2 Status ............................................................................................. 91
4.5.8 DFNT Server 3 Status ............................................................................................. 92
4.5.9 DFNT Server 4 Status ............................................................................................. 92
4.5.10 DFNT Server 5 Status ............................................................................................. 93
4.5.11 DFNT Server 6 Status ............................................................................................. 93
4.5.12 DFNT Server 7 Status ............................................................................................. 94
4.5.13 DFNT Server 8 Status ............................................................................................. 94
4.5.14 DFNT Server 9 Status ............................................................................................. 95
4.5.15 DFNT Server 10 Status ........................................................................................... 95
4.5.16 DFNT Server 11 Status ........................................................................................... 96
4.5.17 DFNT Server 12 Status ........................................................................................... 96
4.5.18 DFNT Server 13 Status ........................................................................................... 97
4.5.19 DFNT Server 14 Status ........................................................................................... 97
4.5.20 DFNT Server 15 Status ........................................................................................... 98
4.5.21 DFNT Server 16 Status ........................................................................................... 98
4.5.22 DFNT Server 17 Status ........................................................................................... 99
4.5.23 DFNT Server 18 Status ........................................................................................... 99
4.5.24 DFNT Server 19 Status ......................................................................................... 100
4.6 Error Codes ........................................................................................................... 101
4.6.1 Local STS Error Codes ......................................................................................... 101
4.6.2 Remote STS Error Codes ..................................................................................... 102
4.6.3 Errors When EXT STS Is Present ......................................................................... 103
4.6.4 Module Specific Error (not DFNT Compliant)........................................................ 104
4.7 TCP/IP Interface Errors ......................................................................................... 105
4.7.1 Timeout Errors ....................................................................................................... 105
4.7.2 Register Session Response Errors ....................................................................... 105
4.7.3 Forward Open Response Errors ........................................................................... 105
4.7.4 PCCC Response Errors ........................................................................................ 106
4.8 Configuration Data ................................................................................................ 107
4.9 DFNT Command Entry Form ................................................................................ 110
4.10 Command Function Codes.................................................................................... 112
4.11 General Command Structure ................................................................................ 113
4.11.1 Function Code #1 - Protected Write (Basic Command Set) ................................. 114
4.11.2 Function Code #2 - Unprotected Read (Basic Command Set) ............................. 114
4.11.3 Function Code #3 - Protected Bit Write (Basic Command Set) ............................ 115
4.11.4 Function Code #4 - Unprotected Bit Write (Basic Command Set) ........................ 115
4.11.5 Function Code #5 - Unprotected Write (Basic Command Set) ............................. 116
4.11.6 Function Code #100 - Word Range Write (PLC-5 Command) (Binary Address) .. 117
4.11.7 Function Code #101 - Word Range Read (PLC-5 Command) (Binary Address) . 118
4.11.8 Function Code #102 - Read-Modify-Write (PLC-5 Command) (Binary Address) . 119
ProSoft Technology, Inc. Page 7 of 177
October 12, 2010
Contents MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
4.11.9 Function Code #150 - Word Range Write (PLC-5 Command) (ASCII Address) .. 120
4.11.10 Function Code #151 - Word Range Read (PLC-5 Command) (ASCII Address) .. 121
4.11.11 Function Code #152 - Read-Modify-Write (PLC-5 Command) (ASCII Address) . 122
4.11.12 Function Code #501 - Protected Typed Logical Read (Two Address Fields) ...... 123
4.11.13 Function Code #502 - Protected Typed Logical Read (Three Address Fields) .... 124
4.11.14 Function Code #509 - Protected Typed Logical Write (Two Address Fields) ...... 125
4.11.15 Function Code #510 - Protected Typed Logical Write (Three Address Fields) .... 126
4.11.16 Function Code #511 - Protected Typed Logical Write with Mask (Three Address
Fields) 127
4.12 PLC-5 Processor Specifics ................................................................................... 128
4.12.1 PLC-5 Sub-Element Codes .................................................................................. 128
4.13 SLC Processor Specifics ...................................................................................... 130
4.13.1 SLC File Types ..................................................................................................... 130
4.14 MicroLogix Processor Specifics ............................................................................ 131
4.14.1 SLC File Types ..................................................................................................... 131
4.15 ControlLogix Processor Specifics ......................................................................... 132
4.16 Server Driver ......................................................................................................... 133
4.16.1 RSLinx Software ................................................................................................... 133
4.16.2 ControlLogix (CLX) Processor .............................................................................. 142
4.16.3 PLC5 Processor .................................................................................................... 149
4.16.4 SLC 5/05 Processor .............................................................................................. 152
4.16.5 RSView Software .................................................................................................. 155
4.17 Accessing an SLC 5 Processor via Ethernet Using MVI46-DFNT ....................... 158
4.17.1 Troubleshooting .................................................................................................... 161
4.18 Frequently Asked Questions ................................................................................. 162
5 Support, Service & Warranty 165
Contacting Technical Support ........................................................................................................ 165
5.1 Return Material Authorization (RMA) Policies and Conditions ............................. 167
5.1.1 Returning Any Product .......................................................................................... 167
5.1.2 Returning Units Under Warranty ........................................................................... 168
5.1.3 Returning Units Out of Warranty ........................................................................... 168
5.2 LIMITED WARRANTY .......................................................................................... 169
5.2.1 What Is Covered By This Warranty ...................................................................... 169
5.2.2 What Is Not Covered By This Warranty ................................................................ 170
5.2.3 Disclaimer Regarding High Risk Activities ............................................................ 170
5.2.4 Intellectual Property Indemnity ............................................................................. 171
5.2.5 Disclaimer of all Other Warranties ........................................................................ 171
5.2.6 Limitation of Remedies ** ..................................................................................... 172
5.2.7 Time Limit for Bringing Suit ................................................................................... 172
5.2.8 No Other Warranties ............................................................................................. 172
5.2.9 Allocation of Risks ................................................................................................ 172
5.2.10 Controlling Law and Severability .......................................................................... 173
Index 175
Page 8 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Guide to the MVI46-DFNT User Manual
EtherNet/IP Client/Server Communication Module User Manual
Guide to the MVI46-DFNT User Manual
Function
Introduction
(Must Do)
Diagnostic and
Troubleshooting
Reference
Product Specifications
Functional Overview
Support, Service, and
Warranty
Index
Section to Read Details
Start Here (page 11) This section introduces the customer to the
→
Diagnostics and
→
Troubleshooting
(page 47)
Reference (page 67)
→
Product
Specifications (page
68)
Functional Overview
(page 71, page 61)
Support, Service
→
and Warranty (page
165)
Index
module. Included are: package contents,
system requirements, hardware installation, and
basic configuration.
This section describes Diagnostic and
Troubleshooting procedures.
These sections contain general references
associated with this product, Specifications, and
the Functional Overview.
This section contains Support, Service and
Warranty information.
Index of chapters.
ProSoft Technology, Inc. Page 9 of 177
October 12, 2010
Guide to the MVI46-DFNT User Manual MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
Page 10 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Start Here
EtherNet/IP Client/Server Communication Module User Manual
1 Start Here
In This Chapter
System Requirements ........................................................................... 12
Package Contents ................................................................................. 13
Installing ProSoft Configuration Builder Software .................................. 14
Setting Jumpers .................................................................................... 15
Installing the Module in the Rack ........................................................... 16
Connecting your PC to the Processor ................................................... 17
Downloading the Sample Program to the Processor ............................. 18
Connecting Your PC to the Module ....................................................... 21
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
Ethernet/IP and SLC devices to a power source and to the MVI46-DFNT
module’s application port(s)
ProSoft Technology, Inc. Page 11 of 177
October 12, 2010
Start Here MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
1.1 System Requirements
The MVI46-DFNT module requires the following minimum hardware and software
components:
Rockwell Automation SLC 5/02 M0/M1 capable processors (or newer), with
compatible power supply and one free slot in the rack, for the MVI46-DFNT
module. The module requires 800mA of available power.
Rockwell Automation RSLogix 500 programming software.
Rockwell Automation RSLinx communication software
Pentium
recommended
Supported operating systems:
o Microsoft
o Windows NT
o Windows 2000
o Windows XP
32 Mbytes of RAM minimum, 64 Mbytes of RAM recommended
50 Mbytes of free hard disk space (or more based on application
requirements)
16-color VGA graphics adapter, 640 x 480 minimum resolution (256 Color
800 × 600 recommended)
CD-ROM drive
®
II 500 MHz minimum. Pentium III 733 MHz (or better)
®
Windows 98
®
(version 4 with SP4 or higher)
Page 12 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Start Here
EtherNet/IP Client/Server Communication Module User Manual
1.2 Package Contents
The following components are included with your MVI46-DFNT module, and are
all required for installation and configuration.
Important: Before beginning the installation, please verify that all of the following items are
present.
Qty. Part Name Part Number Part Description
1 MVI46-DFNT Module MVI46-DFNT EtherNet/IP Client/Server Communication
1 Cable Cable #15 - RS232
1 Cable Cable #14 - RJ45
1 inRAx Solutions CD Contains sample programs, utilities and
If any of these components are missing, please contact ProSoft Technology
Support for replacement parts.
Null Modem
to DB9 Male
Adapter
Module
For RS232 between a Personal Computer
(PC) and the CFG port of the module
For connecting the module’s port to Cable
#15 for RS-232 connections
documentation for the MVI46-DFNT
module.
ProSoft Technology, Inc. Page 13 of 177
October 12, 2010
Start Here MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
1.3 Installing ProSoft Configuration Builder Software
You must install the ProSoft Configuration Builder (PCB) software to configure
the module. You can always get the newest version of ProSoft Configuration
Builder from the ProSoft Technology website.
Installing ProSoft Configuration Builder from the ProSoft website
1 Open your web browser and navigate to http://www.prosoft-
technology.com/pcb
2 Click the DOWNLOAD HERE link to download the latest version of ProSoft
Configuration Builder.
3 Choose SAVE or SAVE FILE when prompted.
4 Save the file to your Windows Desktop, so that you can find it easily when
you have finished downloading.
5 When the download is complete, locate and open the file, and then follow the
instructions on your screen to install the program.
If you do not have access to the Internet, you can install ProSoft Configuration
Builder from the ProSoft Solutions Product CD-ROM, included in the package
with your module.
Installing ProSoft Configuration Builder from the Product CD-ROM
1 Insert the ProSoft Solutions Product CD-ROM into the CD-ROM drive of your
PC. Wait for the startup screen to appear.
2 On the startup screen, click PRODUCT DOCUMENTATION. This action opens a
Windows Explorer file tree window.
3 Click to open the U
and files you will need to set up and configure your module.
4 Double-click the SETUP CONFIGURATION TOOL folder, double-click the
PCB_*.EXE file and follow the instructions on your screen to install the
software on your PC. The information represented by the "*" character in the
file name is the PCB version number and, therefore, subject to change as
new versions of PCB are released.
TILITIES folder. This folder contains all of the applications
Note: Many of the configuration and maintenance procedures use files and other utilities on the
CD-ROM. You may wish to copy the files from the Utilities folder on the CD-ROM to a convenient
location on your hard drive.
Page 14 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Start Here
EtherNet/IP Client/Server Communication Module User Manual
1.4 Setting Jumpers
The Setup Jumper acts as "write protection" for the module’s flash memory. In
"write protected" mode, the Setup pins are not connected, and the module’s
firmware cannot be overwritten. Do not jumper the Setup pins together unless
you are directed to do so by ProSoft Technical Support.
The following illustration shows the MVI46-DFNT jumper configuration.
Note: If you are installing the module in a remote rack, you may prefer to leave the Setup pins
jumpered. That way, you can update the module’s firmware without requiring physical access to
the module.
ProSoft Technology, Inc. Page 15 of 177
October 12, 2010
Start Here MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
1.5 Installing the Module in the Rack
If you have not already installed and configured your SLC processor and power
supply, please do so before installing the MVI46-DFNT module. Refer to your
Rockwell Automation product documentation for installation instructions.
Warning: You must follow all safety instructions when installing this or any other electronic
devices. Failure to follow safety procedures could result in damage to hardware or data, or even
serious injury or death to personnel. Refer to the documentation for each device you plan to
connect to verify that suitable safety procedures are in place before installing or servicing the
device.
After you have checked the placement of the jumpers, insert MVI46-DFNT into
the SLC™ chassis. Use the same technique recommended by Rockwell
Automation to remove and install SLC™ modules.
Warning: This module is not hot-swappable! Always remove power from the rack before
inserting or removing this module, or damage may result to the module, the processor, or other
connected devices.
1 Turn power OFF.
2 Align the module with the top and bottom guides, and slide it into the rack
until the module is firmly against the backplane connector.
3 With a firm but steady push, snap the module into place.
4 Check that the holding clips on the top and bottom of the module are securely
in the locking holes of the rack.
5 Make a note of the slot location. You will need to identify the slot in which the
module is installed in order for the sample program to work correctly. Slot
numbers are identified on the green circuit board (backplane) of the SLC
rack.
6 Turn power ON.
Note: If you insert the module improperly, the system may stop working, or may behave
unpredictably.
Page 16 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Start Here
EtherNet/IP Client/Server Communication Module User Manual
1.6 Connecting your PC to the Processor
1 Connect the right-angle connector end of the cable to your controller at the
communications port.
2 Connect the straight connector end of the cable to the serial port on your
computer.
ProSoft Technology, Inc. Page 17 of 177
October 12, 2010
Start Here MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
1.7 Downloading the Sample Program to the Processor
To download the sample program from RSLogix 500 to the SLC processor
Note: The key switch on the front of the SLC processor must be in the REM position.
1 If you are not already online to the processor, open the Communications
menu, and then choose Download. RSLogix will establish communication
with the processor.
2 Click the Download button to transfer the sample program to the processor.
3 RSLogix will compile the program and transfer it to the processor. This
process may take a few minutes.
4 When the download is complete, RSLogix will open another confirmation
dialog box. Click Yes 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.
Page 18 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Start Here
EtherNet/IP Client/Server Communication Module User Manual
1.7.1 Configuring the RSLinx Driver for the PC COM Port
If RSLogix is unable to establish communication with the processor, follow these
steps.
1 Open RSLinx.
2 Open the COMMUNICATIONS menu, and choose CONFIGURE DRIVERS.
This action opens the Configure Drivers dialog box.
Note: If the list of configured drivers is blank, you must first choose and configure a driver from the
Available Driver Types list. The recommended driver type to choose for serial communication with
the processor is RS-232 DF1 Devices.
ProSoft Technology, Inc. Page 19 of 177
October 12, 2010
Start Here MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
1 Click to select the driver, and then click C
ONFIGURE. This action opens the
Configure RS-232 DF1 Devices dialog box.
2 Click the AUTO-CONFIGURE button. RSLinx will attempt to configure your
serial port to work with the selected driver.
3 When you see the message Auto Configuration Successful, click the OK
button to dismiss the dialog box.
Note: If the auto-configuration procedure fails, verify that the cables are connected correctly
between the processor and the serial port on your computer, and then try again. If you are still
unable to auto-configure the port, refer to your RSLinx documentation for further troubleshooting
steps.
Page 20 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Start Here
EtherNet/IP Client/Server Communication Module User Manual
1.8 Connecting Your PC to the Module
With the module securely mounted, connect your PC to the Configuration/Debug
port using an RJ45-DB-9 Serial Adapter Cable and a Null Modem Cable.
1 Attach both cables as shown.
2 Insert the RJ45 cable connector into the Configuration/Debug port of the
module.
3 Attach the other end to the serial port on your PC.
ProSoft Technology, Inc. Page 21 of 177
October 12, 2010
Start Here MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
Page 22 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Configuring the MVI46-DFNT Module
EtherNet/IP Client/Server Communication Module User Manual
2 Configuring the MVI46-DFNT Module
In This Chapter
Using ProSoft Configuration Builder ...................................................... 24
[Module]................................................................................................. 27
[DFNT Client x] ...................................................................................... 29
[DFNT Client x Commands] ................................................................... 30
[DF1 Pass-Through Server Port 1] ........................................................ 37
[DF1 Pass-Through Port]....................................................................... 39
Ethernet Configuration .......................................................................... 42
Downloading the Project to the Module Using a Serial COM port ......... 43
Ladder Logic .......................................................................................... 44
ProSoft Technology, Inc. Page 23 of 177
October 12, 2010
Configuring the MVI46-DFNT Module MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
2.1 Using ProSoft Configuration Builder
ProSoft Configuration Builder (PCB) provides a quick and easy way to manage
module configuration files customized to meet your application needs. PCB is not
only a powerful solution for new configuration files, but also allows you to import
information from previously installed (known working) configurations to new
projects.
2.1.1 Setting Up the Project
To begin, start 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 D
EFAULT PROJECT and
DEFAULT LOCATION, with a DEFAULT MODULE in the Default Location folder. The
following illustration shows the PCB window with a new project.
Page 24 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Configuring the MVI46-DFNT Module
EtherNet/IP Client/Server Communication Module User Manual
Your first task is to add the MVI46-DFNT module to the project.
1 Use the mouse to select "Default Module" in the tree view, and then click the
right mouse button to open a shortcut menu.
2 On the shortcut menu, choose "Choose Module Type". This action opens the
Choose Module Type dialog box.
3 In the PRODUCT LINE FILTER area of the dialog box, select MVI46.
4 In the SELECT MODULE TYPE dropdown list, select MVI46-DFNT, and then
click OK to save your settings and return to the ProSoft Configuration Builder
window.
The next task is to set the module parameters.
ProSoft Technology, Inc. Page 25 of 177
October 12, 2010
Configuring the MVI46-DFNT Module MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
2.1.2 Renaming PCB Objects
Notice that the contents of the information pane and the configuration pane
changed when you added the module to the project.
At this time, you may wish to rename the Default Project and Default Location
folders in the tree view.
1 Select the object, and then click the right mouse button to open a shortcut
menu. From the shortcut menu, choose RENAME.
2 Type the name to assign to the object.
3 Click away from the object to save the new name.
Configuring Module Parameters
1 Click on the [+] sign next to the module icon to expand module information.
2 Click on the [+] sign next to any icon to view module information and
configuration options.
3 Double-click any icon to open an Edit dialog box.
4 To edit a parameter, select the parameter in the left pane and make your
changes in the right pane.
5 Click OK to save your changes.
Printing a Configuration File
1 Select the module icon, and then click the right mouse button to open a
shortcut menu.
2 On the shortcut menu, choose VIEW CONFIGURATION. This action opens the
View Configuration window.
3 In the View Configuration window, open the FILE menu, and choose PRINT.
This action opens the Print dialog box.
4 In the Print dialog box, choose the printer to use from the drop-down list,
select printing options, and then click OK.
Page 26 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Configuring the MVI46-DFNT Module
EtherNet/IP Client/Server Communication Module User Manual
2.2 [Module]
This section provides the module with a unique name, identifies the method of
failure for the communications for the module if the processor is not in run, and
describes how to initialize the module upon startup.
2.2.1 Module Name
0 to 80 characters
This parameter assigns a name to the module that can be viewed using the
configuration/debug port. Use this parameter to identify the module and the
configuration file.
2.2.2 M1 Write Size
0 to 4000
This parameter limits the M1 data transferred from the processor to the module.
The module application automatically adjusts the size to an even 50-word
boundary as this is the minimum data transfer size for the application. For
example, a value of 199 would automatically be adjusted to 200. This feature
improves the transfer of data from the processor to the module.
2.2.3 Failure Flag Count
0 through 65535
This parameter specifies the number of successive transfer errors that must
occur before halting communication on the application port(s). If the parameter is
set to 0, the application port(s) will continue to operate under all conditions. If the
value is set larger than 0 (1 to 65535), communications will cease if the specified
number of failures occur.
2.2.4 Initialize Output Data
0 = No, 1 = Yes
This parameter is used to determine if the output data for the module should be
initialized with values from the processor. If the value is set to 0, the output data
will be initialized to 0. If the value is set to 1, the data will be initialized with data
from the processor. Use of this option requires associated ladder logic to pass
the data from the processor to the module.
2.2.5 DFNT Server File Size
100 or 1000
Sets the maximum file size (100 or 1000) for the servers
ProSoft Technology, Inc. Page 27 of 177
October 12, 2010
Configuring the MVI46-DFNT Module MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
2.2.6 Float Write Start
0 to 3950 (multiple of 50)
Starting address within the database of the MVI46-DFNT module where floating
point data will be stored. The module will then automatically swap the byte order
of this data, so that it is displayed correctly within the SLC data tables. This is
necessary as the MVI46-DFNT module and the SLC processor use different
floating point data formats.
2.2.7 Float Write Count
0 to 4000 (multiple of 50)
Sets the size (words) of the float area defined in Float Write Start parameter.
Page 28 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Configuring the MVI46-DFNT Module
EtherNet/IP Client/Server Communication Module User Manual
2.3 [DFNT Client x]
This section defines the configuration for the DFNT Client (master) device
simulated on network port
2.3.1 Minimum Command Delay
0 to 65535 milliseconds
This parameter specifies the number of milliseconds to wait between the initial
issuances of a command. This parameter can be used to delay all commands
sent to servers to avoid "flooding" commands on the network. This parameter
does not affect retries of a command as they will be issued when failure is
recognized.
2.3.2 Response Timeout
0 to 65535 milliseconds
This is the time in milliseconds that a Client will wait before re-transmitting a
command if no response is received from the addressed server. The value to use
depends on the type of communication network used, and the expected
response time of the slowest device on the network.
2.3.3 Retry Count
0 to 10
This parameter specifies the number of times a command will be retried if it fails.
ProSoft Technology, Inc. Page 29 of 177
October 12, 2010
Configuring the MVI46-DFNT Module MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
2.4 [DFNT Client x Commands]
This section defines the EtherNet/IP commands to be issued from the module to
server devices on the network. These commands can be used for data collection
and/or control of devices on the TCP/IP network.
2.4.1 Command List
In order to interface the virtual database with DF1 slave devices, you must
construct a command list. The commands in the list specify the DF1 slave device
to be utilized, the function to be performed (read or write), the data area in the
device to interface with and the position in the virtual database to be associated
with the device data. There is a separate command list for each DF1 master
device emulated. The list is processed from top (command #0) to bottom. A poll
interval parameter is associated with each command to specify a minimum delay
time between the issuance of a command. If the user specifies a value of 10 for
the parameter, the command will be executed no more frequently than every 10
seconds for the serial implementation and 1 second for the network
implementation.
Write commands have a special feature, as they can be set to execute only if the
data in the write command changes. If the data in the command has not changed
since the command was last issued, the command will not be executed. If the
data in the command has changed since the command was last issued, the
command will be executed. Use of this feature can lighten the load on the DF1
network. In order to implement this feature; set the enable code for the command
to a value of 2.
Page 30 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Configuring the MVI46-DFNT Module
EtherNet/IP Client/Server Communication Module User Manual
If the module is configured for the serial DF1 half-duplex protocol, the module
can act as a master device routing messages between attached slave devices.
This peer-to-peer communication is defined in the DF1 protocol specification.
The master polls each DF1 slave device until no more data is available from the
device. Response messages from the slaves that have a destination address that
do not match the module are routed with a request message header back out
onto the network. This facility offers communication between the slave devices
for control and data monitoring. This feature is not available if the module is
configured for DF1 full-duplex mode (point-to-point).
The module supports numerous commands. This permits the module to interface
with a wide variety of DF1 protocol devices. This includes PLC2, PLC5, SLC-500
series, MicroLogix and ControlLogix processors. Additionally, other devices
supplied by Rockwell Automation that use the DF1 protocol are supported.
The format of each command in the list depends on the function being executed.
To simplify command construction, the module uses its own set of function codes
to associate a command with a DF1 command/function type. The tables below
list the functions supported by the module:
Basic Command Set Functions
Function
Code
1 0x00 N/A Protected Write X
2 0x01 N/A Unprotected Read X X
3 0x02 N/A Protected Bit Write X
4 0x05 N/A Unprotected Bit Write X
5 0x08 N/A Unprotected Write X X
Command Function Definition PLC5 SLC500 &
MicroLogix
Powermonitor II
ControlLogix
X
X
X
X
X
PLC-5 Command Set Functions
Function
Code
100 0x0F 0x00 Word Range Write
Command Function Definition PLC5 SLC500 &
MicroLogix
X
Powermonitor II
X
ControlLogix
(Binary Address)
101 0x0F 0x01 Word Range Read
X
X
(Binary Address)
102 0x0F 0x26 Read-Modify-Write
X
X
(Binary Address)
150 0x0F 0x00 Word Range Write
X
X
(ASCII Address)
151 0x0F 0x01 Word Range Read
X
X
(ASCII Address)
152 0x0F 0x26 Read-Modify-Write
(ASCII Address)
X
X
ProSoft Technology, Inc. Page 31 of 177
October 12, 2010
Configuring the MVI46-DFNT Module MVI46-DFNT ♦ SLC Platform
X
X
X
User Manual EtherNet/IP Client/Server Communication Module
SLC-500 Command Set Functions
Function
Code
501 0x0F 0xA1 Protected Typed
502 0x0F 0XA2 Protected Typed
509 0x0F 0XA9 Protected Typed
510 0x0F 0XAA Protected Typed
511 0x0F 0XAB Protected Typed
Command Function Definition PLC5 SLC500 &
Logical Read With
Two Address Fields
Logical Read With
Three Address Fields
Logical Write With
Two Address Fields
Logical Write With
Three Address Fields
Logical Write With
Mask (Three Address
Fields)
Power-
MicroLogix
X X X
X X X
monitor II
ControlLogix
X
X
X
Each command list record has the same general format. The first part of the
record contains the information relating to the communication module and the
second part contains information required to interface to the DF1 or EtherNet/IP
slave device.
Page 32 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Configuring the MVI46-DFNT Module
EtherNet/IP Client/Server Communication Module User Manual
2.4.2 Command Entry Formats
The format of each command in the list depends on the function being executed.
Refer to Command Function Codes (page 33) for a complete discussion of the
commands supported by the module and of the structure and content of each
command.
The following table shows the structure of the configuration data necessary for
each of the supported commands.
Module Information Data Device Information Data
Column # 1 2 3 4 5 6 7 8 9 10 11 12
Functio
n Code
FC 1 Code Register Seconds Count Code Node Slot 1 Word
FC 2 Code Register Seconds Count Code Node
FC 3 Code Register Seconds Count Code Node
FC 4 Code Register Seconds Count Code Node
FC 5 Code Register Seconds Count Code Node
FC 100 Code Register Seconds Count Code Node
FC 101 Code Register Seconds Count Code Node
FC 102 Code Register Seconds Count Code Node
FC 150 Code Register Seconds Count Code Node
FC 151 Code Register Seconds Count Code Node
FC 152 Code Register Seconds Count Code Node
FC 501 Code Register Seconds Count Code Node
FC 502 Code Register Seconds Count Code Node
FC 509 Code Register Seconds Count Code Node
Enabl
e
Code
Internal
Addres
s
Poll
Interval
Time
Count Swap
Code
IP
Address
Slot
Numbe
r
Funct
Function Parameters
ion
Code
Address
2 Word
Address
3 Word
Address
4 Word
Address
5 Word
Address
100 File
Number
101 File
Number
102 File
Number
150 File
String
151 File
String
152 File
String
501 File
Type
502 File
Type
509 File
Type
Element Sub-
Elemen
t
Element Sub-
Elemen
t
Element Sub-
Elemen
t
File
Numbe
r
File
Numbe
r
File
Numbe
r
Element
Element Sub-
Element
Elemen
t
ProSoft Technology, Inc. Page 33 of 177
October 12, 2010
Configuring the MVI46-DFNT Module MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
Module Information Data Device Information Data
Column # 1 2 3 4 5 6 7 8 9 10 11 12
Functio
n Code
FC 510 Code Register Seconds Count Code Node
FC 511 Code Register Seconds Count Code Node
IP Address = IP address of processor to reach
Slot Number = -1 for PLC5 & SLC, processor slot number of ControlLogix
Enabl
e
Code
Internal
Addres
s
Poll
Interval
Time
Count Swap
Code
IP
Address
Slot
Numbe
r
Funct
Function Parameters
ion
Code
510 File
Type
511 File
Type
File
Numbe
r
File
Numbe
r
Element Sub-
Elemen
t
Element Sub-
Elemen
t
The first part of the record is the Module Information, which relates to the
module. The second part contains information required to interface to the Server
device. An example of a command list section of the configuration file is shown in
the following illustration.
[DFNT Client 0 Commands]
#
# The file contains examples for a ControlLogix processor with the N7 file
# configured. This example uses SLC and PLC5 commands.
#
# LOCATION :
# DATE : 04/05/2000
# CONFIGURED BY: RAR
# MODIFIED :
#
# 1 2 3 4 5 6 7 8 9 10 11 12
# DB Poll Swap Func File File Elm Sub
Page 34 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Configuring the MVI46-DFNT Module
EtherNet/IP Client/Server Communication Module User Manual
#Enab Addr Delay Count Code Node IP Address Slot Code Type # # Elm
START
# 1 2000 0 10 0 192.168.0.100 0 501 N 11 0
# 1 2000 0 10 0 192.168.0.100 0 509 N 12 0
#
# DB Poll Swap Func File Elm Sub
#Enab Addr Delay Count Code Node IP Address Slot Code # # Elm
END
The following table describes each parameter
Parameter Range Description
Enable 0, 1, 2 This field defines whether the command is to be executed and under what
conditions.
Value Description
0 The command is disabled and will not be executed in the normal
polling sequence.
1 The command is executed each scan of the command list if the
Poll Interval Time is set to zero. If the Poll Interval time is set, the
command is executed when the interval timer expires.
2 The command executes only if the internal data associated with
the command changes. This value is valid for write commands
only.
Internal
Address
Poll Delay 0 to 1000 This parameter specifies the minimum interval to execute continuous
Count Command dependent. This parameter specifies the number of registers or digital points to be
Swap Code 0, 1, 2, 3 This parameter defines if the data received from the Server is to be ordered
0 to 3999 This field specifies the database address in the module's internal database to
be associated with the command. If the command is a read function, the data
received in the response message is placed at the specified location. If the
command is write function, data used in the command is sourced from the
specified data area.
commands (Enable code of 1). The parameter is entered in 1/10th of a
second. Therefore, if a value of 100 is entered for a command, the command
executes no more frequently than every 10 seconds.
associated with the command. See Command Function Codes (page 33) for
information
differently than that received from the Server device. This parameter is helpful
when dealing with floating-point or other multi-register values, as there is no
standard method of storage of these data types in Server devices. This
parameter can be set to order the register data received in an order useful by
other applications. The following table defines the values and their associated
operations:
Swap Code Description
0 None - No Change is made in the byte ordering (1234 =
1234)
1 Words - The words are swapped (1234=3412)
2 Words & Bytes - The words are swapped then the bytes in
each word are swapped (1234=4321)
3 Bytes - The bytes in each word are swapped (1234=2143)
The words should be swapped only when using an even number of words.
ProSoft Technology, Inc. Page 35 of 177
October 12, 2010
Configuring the MVI46-DFNT Module MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
Parameter Range Description
Node IP
Address
Slot
Function Code See Command
Function
Parameters
xxx.xxx.xxx.xxx The IP address of the device being addressed by the command.
When addressing a ControlLogix processor, the slot number corresponds to
the slot in the rack containing the controller being addressed. In the
ControlLogix platform, the controller can be placed in any slot and the rack
may contain multiple processors. This parameter uniquely selects a controller
in the rack.
Use a value of -1 when interfacing to an SLC 5/05 or a
PLC5. These devices do not have a slot number.
These parameters specify the function to be executed by the command. The
Function Codes (page
33)
Reference chapter in this manual describes the meaning of these values for
each of the available supported commands. Following is a complete list of the
command supported by the Client driver.
Function Code Listing
Basic Command Set
1 Protected Write
2 Unprotected Read
3 Protected Bit Write
4 Unprotected Bit Write
5 Unprotected Write
PLC-5 Command Set (0x0F)
100 Word Range Write (Binary Address)
101 Word Range Read (Binary Address)
102 Read-Modify-Write (Binary Address)
150 Word Range Write (ASCII Address)
151 Word Range Read (ASCII Address)
152 Read-Modify-Write (ASCII Address)
SLC Command Set (0x0F)
501 Prot Typed Read with 2 addr fields
502 Prot Typed Read with 3 addr fields
509 Prot Typed Write with 2 addr fields
510 Prot Typed Write with 3 addr fields
511 Prot Type Write with Mask 3 addr field
See Command
Function Codes (page
The number of auxiliary parameters required depends on the function code
selected for the command.
33)
Page 36 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Configuring the MVI46-DFNT Module
EtherNet/IP Client/Server Communication Module User Manual
2.5 [DF1 Pass-Through Server Port 1]
This section defines the DF1 pass-through server on Port 1 (the second port).
2.5.1 Enabled
Yes or No
This parameter determines if the server will be utilized by the module. If a value
of "Yes" is entered, the server will be used. Any other value will disable the
server.
2.5.2 Service Port Number
1 to 65535
This parameter sets the TCP/IP service port for this server. Each server can
have its own unique service port or can share the same number with other
servers.
2.5.3 Busy Timeout
100 to 65535 milliseconds
This parameter sets the number of milliseconds the server will wait for the serial
pass-through port to become available. Valid data range for this parameter is 100
to 65535.
2.5.4 Baud Rate
Range 1200 to 19200
This is the baud rate to use for the DFNT network. Select one of the listed baud
rates.
ProSoft Technology, Inc. Page 37 of 177
October 12, 2010
Configuring the MVI46-DFNT Module MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
2.5.5 Parity
None, Odd, Even
Parity is a simple error checking algorithm used in serial communication. This
parameter specifies the type of parity checking to use.
All devices communicating through this port must use the same parity setting.
2.5.6 Data Bits
5, 6, 7 or 8
This parameter sets the number of data bits for each word used by the protocol.
All devices communicating through this port must use the same number of data
bits.
2.5.7 Stop Bits
1 or 2
Stop bits signal the end of a character in the data stream. For most applications,
use one stop bit. For slower devices that require more time to re-synchronize,
use two stop bits.
All devices communicating through this port must use the same number of stop
bits.
2.5.8 RTS On
0 to 65535 milliseconds
This parameter sets the number of milliseconds to delay after Ready To Send
(RTS) is asserted before data will be transmitted.
2.5.9 RTS Off
0 to 65535 milliseconds
This parameter sets the number of milliseconds to delay after the last byte of
data is sent before the RTS modem signal will be set low.
2.5.10 Use CTS Line
YES or NO
This parameter specifies if the Clear To Send (CTS) modem control line is to be
used or not. If the parameter is set to NO, the CTS line will not be monitored. If
the parameter is set to YES, the CTS line will be monitored and must be high
before the module will send data. Normally, this parameter is required when halfduplex modems are used for communication (2-wire). This procedure is
commonly referred to as hardware handshaking.
Page 38 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Configuring the MVI46-DFNT Module
EtherNet/IP Client/Server Communication Module User Manual
2.6 [DF1 Pass-Through Port]
This section defines the configuration for the DF1 pass-through port on Port 2
(the third port).
2.6.1 Enabled
Yes or No
This parameter determines if the server will be utilized by the module. If a value
of "Yes" is entered, the server will be used. Any other value will disable the
server.
2.6.2 Local Station ID
0 to 254
This parameter specifies the local station ID for all DF1 messages sent to this
port. A value of 255 is not permitted as this is the broadcast address. The
application will only accept messages with this node address.
2.6.3 Protocol
F (Full duplex) or H (Half duplex)
The value selected should match that set for the SLC processor.
2.6.4 Termination Type
BCC or CRC
This parameter specifies the error checking for all DF1 messages. Enter BCC or
CRC.
ProSoft Technology, Inc. Page 39 of 177
October 12, 2010
Configuring the MVI46-DFNT Module MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
2.6.5 Baud Rate - 1200 to 38400
1200 to 38400
This is the baud rate to be used for the port. Enter the baud rate as a value. Baud
rate entries are 1200, 2400, 4800, 9600, 19200, 28800 or 38400.
2.6.6 Parity
None, Odd, Even, Mark, Space
Parity is a simple error checking algorithm used in serial communication. This
parameter specifies the type of parity checking to use.
All devices communicating through this port must use the same parity setting.
2.6.7 Data Bits
5, 6, 7 or 8
This parameter sets the number of data bits for each word used by the protocol.
All devices communicating through this port must use the same number of data
bits.
2.6.8 Stop Bits
1 or 2
Stop bits signal the end of a character in the data stream. For most applications,
use one stop bit. For slower devices that require more time to re-synchronize,
use two stop bits.
All devices communicating through this port must use the same number of stop
bits.
2.6.9 RTS On
0 to 65535 milliseconds
This parameter sets the number of milliseconds to delay after Ready To Send
(RTS) is asserted before data will be transmitted.
2.6.10 RTS Off
0 to 65535 milliseconds
This parameter sets the number of milliseconds to delay after the last byte of
data is sent before the RTS modem signal will be set low.
Page 40 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Configuring the MVI46-DFNT Module
EtherNet/IP Client/Server Communication Module User Manual
2.6.11 Use CTS Line
YES or NO
This parameter specifies if the Clear To Send (CTS) modem control line is to be
used or not. If the parameter is set to NO, the CTS line will not be monitored. If
the parameter is set to YES, the CTS line will be monitored and must be high
before the module will send data. Normally, this parameter is required when halfduplex modems are used for communication (2-wire). This procedure is
commonly referred to as hardware handshaking.
2.6.12 Retry Count
0 to 10
This parameter specifies the number of times a command will be retried if it fails.
2.6.13 Request Timeout
0 to 10000 milliseconds
This parameter specifies the number of milliseconds to wait for a complete
request message. The timer is started after the DLE-STX character sequence is
received for the full-duplex protocol or the DLE-SOH sequence for the halfduplex protocol. If the timer expires, the current request message will be aborted.
2.6.14 Busy Timeout
0 to 10000 milliseconds
This parameter specifies the number of milliseconds to wait for the pass-through
port to become available.
2.6.15 ACK Timeout
0 to 10000 milliseconds
This parameter specifies the number of milliseconds to wait for a DLE-ACK
character sequence after a response is issued.
ProSoft Technology, Inc. Page 41 of 177
October 12, 2010
Configuring the MVI46-DFNT Module MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
2.7 Ethernet Configuration
Use this procedure to configure the Ethernet settings for your module. You must
assign an IP address, subnet mask and gateway address. After you complete
this step, you can connect to the module with an Ethernet cable.
1 Determine the network settings for your module, with the help of your network
administrator if necessary. You will need the following information:
o IP address (fixed IP required) _____ . _____ . _____ . _____
o Subnet mask _____ . _____ . _____ . _____
o Gateway address _____ . _____ . _____ . _____
Note: The gateway address is optional, and is not required for networks that do not use a default
gateway.
2 Double-click the ETHERNET CONFIGURATION icon. This action opens the Edit
dialog box.
3 Edit the values for my_ip, netmask (subnet mask) and gateway (default
gateway).
4 When you are finished editing, click OK to save your changes and return to
the ProSoft Configuration Builder window.
Page 42 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Configuring the MVI46-DFNT Module
EtherNet/IP Client/Server Communication Module User Manual
2.8 Downloading the Project to the Module Using a Serial COM port
For the module to use the settings you configured, you must download (copy) the
updated Project file from your PC to the module.
1 In the tree view in ProSoft Configuration Builder, click once to select the
module.
2 Open the Project
will scan your PC for a valid com port (this may take a few seconds). When
PCB has found a valid COM port, the Download dialog box will open.
menu, and then choose MODULE/DOWNLOAD. The program
3 Choose the COM port to use from the dropdown list, and then click the
OWNLOAD button.
D
The module will perform a platform check to read and load its new settings.
When the platform check is complete, the status bar in the Download dialog
box will display the message Module Running.
ProSoft Technology, Inc. Page 43 of 177
October 12, 2010
Configuring the MVI46-DFNT Module MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
2.9 Ladder Logic
Ladder logic is required for application of the MVI46-DFNT module. Tasks that
must be handled by the ladder logic are module data transfer, special block
handling, and status data receipt. Additionally, a power-up handler may be
needed to handle the initialization of the module’s data and to clear any
processor fault conditions.
The sample ladder logic, on the ProSoft Solutions CD-ROM, is extensively
commented, to provide information on the purpose and function of each rung. For
most applications, the sample ladder will work without modification.
2.9.1 Module Data
All data related to the MVI46-DFNT module is stored in user defined data files
and the module’s M1 file. Files should be defined for each data type for the
module. Additionally, a file should be defined to hold the module status data. The
status data should be copied from the M1 file and placed in the assigned status
file. Input (monitor) data should be copied from the user file to the M1 file and
output (command) data should be copied from the user files to the M1 file.
2.9.2 Adding the Module to an Existing Project
1 Add the MVI46-DFNT module to the project. Double-click on the I/O
Configuration option in the Controller Organization window.
Page 44 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Configuring the MVI46-DFNT Module
EtherNet/IP Client/Server Communication Module User Manual
2 This action opens the I/O Configuration dialog box. Select an empty slot in
the left pane, and then scroll to the bottom of the right pane.
3 In the right pane, double-click Other -- Requires I/O Card Type ID. This
action opens the "Other" type IO card dialog box.
4 The module's I/O card ID number is 12835. Enter that value in the ID number
field, and then click OK to dismiss the dialog box.
5 Observe that the module you selected is now in the list in the left pane of the
I/O Configuration dialog box.
ProSoft Technology, Inc. Page 45 of 177
October 12, 2010
Configuring the MVI46-DFNT Module MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
6 Select and double-click the new module in the left pane. This action opens
the Advanced I/O Configuration dialog box. Fill in the dialog box with the
values shown in the following illustration.
Field Value
Scanned Input Words 2
Scanned Output Words 2
Interrupt Service Routine (ISR)# 0
M0 Length 0
M1 Length 5000
G File Length 0
7 Click OK to save your configuration.
8 Copy the Ladder Logic and data files from the sample program and paste
them into your existing program.
Important: Take care not to overwrite existing data files in your application with data files in the
sample application. Rename either the source or the destination data files, and then search and
replace references in the ladder for instances of any renamed files.
9 Save and Download (page 18) the new application to the controller and place
the processor in run mode.
Page 46 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Diagnostics and Troubleshooting
EtherNet/IP Client/Server Communication Module User Manual
3 Diagnostics and Troubleshooting
In This Chapter
LED Status Indicators ............................................................................ 48
Using ProSoft Configuration Builder (PCB) for Diagnostics................... 53
Reading Status Data from the Module .................................................. 66
The module provides information on diagnostics and troubleshooting in the
following forms:
LED status indicators on the front of the module provide general information
on the module's status.
Status data contained in the module can be viewed through the
Configuration/Debug port, using the troubleshooting and diagnostic
capabilities of ProSoft Configuration Builder (PCB).
Status data values can be transferred from the module to processor memory
and can be monitored there manually or by customer-created logic.
ProSoft Technology, Inc. Page 47 of 177
October 12, 2010
Diagnostics and Troubleshooting MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
3.1 LED Status Indicators
The LEDs indicate the module’s operating status as follows:
LED Color Status Indication
CFG Green On Data is being transferred between the module and a remote
Off No data is being transferred on the Configuration/Debug
P1 Green On Data is being transferred between the module and the
Off No data is being transferred on this port
P2 Green On Data is being transferred on this port and the remote device
Off No data is being transferred on this port
APP Amber Off The MVI46-DFNT is working normally.
On The MVI46-DFNT module program has recognized an error.
BP ACT Amber On The LED is on when the module is performing a write
Off The LED is off when the module is performing a read
OK Red/
Green
BAT Red Off The battery voltage is OK and functioning.
Off The card is not receiving any power and is not securely
Green The module is operating normally.
Red The program has detected an error or is being configured. If
On The battery voltage is low or battery is not present. Allow
terminal using the Configuration/Debug port.
port.
processors Channel 0 port.
connected to the port
operation on the backplane.
operation on the backplane. Under normal operation, the
LED should blink rapidly on and off.
plugged into the rack.
the LED remains red for over 10 seconds, the program has
probably halted. Remove the card from the rack and re-insert
the card to restart the module’s program.
battery to charge by keeping module plugged into rack for 24
hours. If BAT LED still does not go off, contact ProSoft
Technology, as this is not a user serviceable item.
Page 48 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Diagnostics and Troubleshooting
EtherNet/IP Client/Server Communication Module User Manual
If a configuration error is found for the client, the client configuration error word
will have a value other than zero. The configuration error word bits have the
following definitions:
Bit Description Value
0 0x0001
1 0x0002
2 0x0004
3 0x0008
4 Invalid retry count (0 to 10) 0x0010
5 0x0020
6 0x0040
7 0x0080
8 0x0100
9 0x0200
10 0x0400
11 0x0800
12 0x1000
13 0x2000
14 0x4000
15 0x8000
ProSoft Technology, Inc. Page 49 of 177
October 12, 2010
Diagnostics and Troubleshooting MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
If a configuration error is present for the pass-through server, the configuration
error word contains a value other than zero. The configuration error word bits
have the following definitions:
Bit Description Value
0 Invalid enable code 0x0001
1 Invalid busytimeout setting (< 100 milliseconds) 0x0002
2 0x0004
3 0x0008
4 0x0010
5 Invalid baud rate 0x0020
6 Invalid parity 0x0040
7 Invalid data bits 0x0080
8 Invalid stop bits 0x0100
9 0x0200
10 0x0400
11 0x0800
12 0x1000
13 0x2000
14 0x4000
15 0x8000
Page 50 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Diagnostics and Troubleshooting
EtherNet/IP Client/Server Communication Module User Manual
If a configuration error is present for the pass-through port, the configuration error
word contains a value other than zero. The configuration error word bits have the
following definitions:
Bit Description Value
0 Invalid enable code 0x0001
1 Invalid local station ID 0x0002
2 Invalid protocol or termination type 0x0004
3 Invalid baud rate 0x0008
4 Invalid parity 0x0010
5 Invalid data bits 0x0020
6 Invalid stop bits 0x0040
7 0x0080
8 Invalid Use CTS Line selection 0x0100
9 Invalid retry count 0x0200
10 0x0400
11 0x0800
12 0x1000
13 0x2000
14 0x4000
15 0x8000
Correct any invalid data in the configuration for proper module operation. When
the configuration contains a valid parameter set, all the bits in the configuration
words are clear. This does not indicate that the configuration is valid for the user
application. Make sure each parameter is set correctly for the specific
application.
If the APP, BP ACT and OK LEDs blink at a rate of every one-second, this
indicates a serious problem with the module. Call ProSoft Technology support to
arrange for repairs.
3.1.1 Ethernet LED Indicators
LED State Description
Data OFF No activity on the Ethernet port.
GREEN Flash The Ethernet port is actively transmitting or receiving data.
Link OFF No physical network connection is detected. No Ethernet
communication is possible. Check wiring and cables.
GREEN Solid Physical network connection detected. This LED must be ON
solid for Ethernet communication to be possible.
ProSoft Technology, Inc. Page 51 of 177
October 12, 2010
Diagnostics and Troubleshooting MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
3.1.2 Clearing a Fault Condition
Typically, if the OK LED on the front of the module turns RED for more than ten
seconds, a hardware problem has been detected in the module or the program
has exited.
To clear the condition, follow these steps:
1 Turn off power to the rack.
2 Remove the card from the rack.
3 Verify that all jumpers are set correctly.
4 If the module requires a Compact Flash card, verify that the card is installed
correctly.
5 Re-insert the card in the rack and turn the power back on.
6 Verify correct configuration data is being transferred to the module from the
SLC 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.
3.1.3 Troubleshooting
Use the following troubleshooting steps if you encounter problems when the
module is powered up. If these steps do not resolve your problem, please contact
ProSoft Technology Technical Support.
Processor Errors
Problem description Steps to take
Processor fault Verify that the module is plugged into the slot that has been configured
for the module in the I/O Configuration of RSLogix.
Verify that the slot location in the rack has been configured correctly in
the ladder logic.
Processor I/O LED
flashes
This indicates a problem with backplane communications. A problem
could exist between the processor and any installed I/O module, not just
the MVI46-DFNT. Verify that all modules in the rack are correctly
configured in the ladder logic.
Module Errors
Problem description Steps to take
BP ACT LED (not
present on MVI56E
modules) remains OFF
or blinks slowly
MVI56E modules with
scrolling LED display:
<Backplane Status>
condition reads ERR
OK LED remains RED The program has halted or a critical error has occurred. Connect to the
This indicates that backplane transfer operations are failing. Connect to
the module’s Configuration/Debug port to check this.
To establish backplane communications, verify the following items:
The processor is in RUN or REM RUN mode.
The backplane driver is loaded in the module.
The module is configured for read and write data block transfer.
The ladder logic handles all read and write block situations.
The module is properly configured in the processor I/O configuration
and ladder logic.
Configuration/Debug port to see if the module is running. If the program
has halted, turn off power to the rack, remove the card from the rack and
re-insert it, and then restore power to the rack.
Page 52 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Diagnostics and Troubleshooting
EtherNet/IP Client/Server Communication Module User Manual
3.2 Using ProSoft Configuration Builder (PCB) for Diagnostics
The Configuration and Debug menu for this module is arranged as a tree
structure, with the Main menu at the top of the tree, and one or more submenus
for each menu command. The first menu you see when you connect to the
module is the Main menu.
Because this is a text-based menu system, you enter commands by typing the
[command letter] from your computer keyboard in the Diagnostic window in
ProSoft Configuration Builder (PCB). The module does not respond to mouse
movements or clicks. The command executes as soon as you press the
[COMMAND LETTER] — you do not need to press [ENTER]. When you type a
[COMMAND LETTER], a new screen will be displayed in your terminal application.
3.2.1 Using the Diagnostic Window in ProSoft Configuration Builder
To connect to the module’s Configuration/Debug serial port
1 Start PCB, and then select the module to test. Click the right mouse button to
open a shortcut menu.
2 On the shortcut menu, choose DIAGNOSTICS.
This action opens the Diagnostics
dialog box.
ProSoft Technology, Inc. Page 53 of 177
October 12, 2010
Diagnostics and Troubleshooting MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
3 Press [?]
to open the Main menu.
If there is no response from the module, follow these steps:
1 Click to configure the connection. On the Connection Setup dialog box, select
a valid com port or other connection type supported by the module.
2 Verify that the null modem cable is connected properly between your
computer’s serial port and the module. A regular serial cable will not work.
3 On computers with more than one serial port, verify that your communication
program is connected to the same port that is connected to the module.
If you are still not able to establish a connection, contact ProSoft Technology for
assistance.
Page 54 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Diagnostics and Troubleshooting
EtherNet/IP Client/Server Communication Module User Manual
3.2.2 Navigation
All of the submenus for this module contain commands to redisplay the menu or
return to the previous menu. You can always return from a submenu to the next
higher menu by pressing [M] on your keyboard.
The organization of the menu structure is represented in simplified form in the
following illustration:
The remainder of this section shows the menus available for this module, and
briefly discusses the commands available to you.
Keystrokes
The keyboard commands on these menus are usually not case sensitive. You
can enter most commands in lowercase or uppercase letters.
The menus use a few special characters (?, -, +, @) that must be entered exactly
as shown. Some of these characters will require you to use the SHIFT, CTRL, or
ALT keys to enter them correctly. For example, on US English keyboards, enter
the ? command as SHIFT and /.
Also, take care to distinguish the different uses for uppercase letter "eye" (I),
lowercase letter "el" (L), and the number one (1). Likewise, uppercase letter "oh"
(O) and the number zero (0) are not interchangeable. Although these characters
look alike on the screen, they perform different actions on the module and may
not be used interchangeably.
ProSoft Technology, Inc. Page 55 of 177
October 12, 2010
Diagnostics and Troubleshooting MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
3.2.3 Main Menu
Features available through the use of the configuration/debug port on the MVI46DFNT module are all accessed using single keystrokes on your computer. There
is a single main menu and several sub-menus presented on the port. To view the
current selections available, press the [?] key on your computer. If you are at the
main menu, the following menu appears:
If this menu is not shown, press the [M] key to display the main menu. All
facilities offered by the configuration/debugger are shown on the main menu.
Each option is discussed in the following topics.
Viewing Block Transfer Statistics
Press [B] from the Main menu to view the Block Transfer Statistics screen.
Use this command to display the configuration and statistics of the backplane
data transfer operations between the module and the processor. The information
on this screen can help determine if there are communication problems between
the processor and the module.
Tip: To determine the number of blocks transferred each second, mark the numbers displayed at a
specific time. Then some seconds later activate the command again. Subtract the previous
numbers from the current numbers and divide by the quantity of seconds passed between the two
readings.
Viewing Module Configuration
Press [C] to view the Module Configuration screen.
Use this command to display the current configuration and statistics for the
module.
Opening the Database View Menu
Press [D] to open the Database View menu.
Use this menu command to view the current contents of the module’s database.
For more information about this submenu, see Database View Menu (page 60).
Page 56 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Diagnostics and Troubleshooting
EtherNet/IP Client/Server Communication Module User Manual
Opening the Client Command Error List Menu
Press [E] to open the Client Command Error List. This list consists of multiple
pages of command list error/status data. Press [?] to view a list of commands
available on this menu.
Opening the Client Command List Menu
Press [I]
configured command list for the module.
to open the Client Command List menu. Use this command to view the
Transferring the Configuration File from the PC to the Module
On the Diagnostics Menu this is referred to as Receive Module Configuration.
Press [R] to receive (download) the configuration file from your PC to the module
and store the file on the module’s Compact Flash Card (Personality Module) or
Flash RAM.
Press [Y] to confirm the file transfer, and then follow the instructions on the
terminal screen to complete the file transfer process.
After the file has been successfully downloaded, the module will restart the
program and load the new configuration information. Review the new
configuration using menu commands [6] and [0] to verify that the module is
configured correctly.
Transferring the Configuration File from The Module to the PC
On the Diagnostics Menu this is referred to as Send Module Configuration.
Press [S] to send (upload) the configuration file from the module to your PC.
Press [Y]
to confirm the file transfer, and then follow the instructions on the
terminal screen to complete the file transfer process.
After the file has been successfully uploaded, you can open and edit the file to
change the module’s configuration.
Resetting Diagnostic Data
Press [U] to reset the status counters for the Client and/or servers in the module.
Viewing Version Information
Press [V] to view version information for the module.
Use this command to view the current version of the software for the module, as
well as other important values. You may be asked to provide this information
when calling for technical support on the product.
Values at the bottom of the display are important in determining module
operation. The Program Scan Counter value is incremented each time a
module’s program cycle is complete.
Tip: Repeat this command at one-second intervals to determine the frequency of program
execution.
ProSoft Technology, Inc. Page 57 of 177
October 12, 2010
Diagnostics and Troubleshooting MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
Warm Booting the Module
Press [W] from the Main menu to warm boot (restart) the module.
This command will cause the program to exit and reload, refreshing configuration
parameters that must be set on program initialization. Only use this command if
you must force the module to reboot.
Viewing Client Communication Status
Press [1] to view client communication status. Use this command to view the
statistics of the DFNT client commands sent by the MVI46-DFNT. The following
illustration shows an example of the information on this screen.
Viewing Server Status Data
Press [2], [3], [4] or [5] to view status data for the DFNT servers. The following
illustration shows an example of the status screen for the selected servers:
2 = Display servers 0 to 4
3 = Display servers 5 to 9
4 = Display servers 10 to 14
5 = Display servers 15 to 19
Note: Some implementations of the DFNT protocol support fewer DFNT servers (for example,
5201-DFNT-BACNET, which supports only five servers, rather than the twenty shown in this
illustration)
Page 58 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Diagnostics and Troubleshooting
EtherNet/IP Client/Server Communication Module User Manual
Viewing DF1 Server Status Data
Press [7] to view communication status for the DF1 pass through server.
Viewing Client Configuration
Press [8] to display the configuration information for the client.
Viewing DF1 Pass-Through Server Configuration
Press [9] to view configuration information for the DF1 pass-through server.
Viewing DF1 Pass Through Port Configuration
Press [0] (zero) to view configuration information for the DF1 pass-through port.
Opening the Network Menu
Press [@] to open the Network menu.
The Network menu allows you to send, receive and view the WATTCP.CFG file
that contains the IP, gateway and other network specification information. For
more information about this submenu, see Network Menu (page 64).
Exiting the Program
Press [ESC] to restart the module and force all drivers to be loaded. The module
will use the configuration stored in the module's Flash memory to configure the
module.
ProSoft Technology, Inc. Page 59 of 177
October 12, 2010
Diagnostics and Troubleshooting MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
3.2.4 Database View Menu
Press [D] from the Main menu to open the Database View menu. Use this menu
command to view the current contents of the module database. Press [?] to view
a list of commands available on this menu.
Viewing Register Pages
To view sets of register pages, use the keys described below:
Command Description
[0]
[1]
[2]
Display registers 0 to 99
Display registers 1000 to 1099
Display registers 2000 to 2099
And so on. The total number of register pages available to view depends on your
module’s configuration.
Displaying the Current Page of Registers Again
Press [S] from the Database View menu to show the current page of registers
again.
This screen displays the current page of 100 registers in the database.
Page 60 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Diagnostics and Troubleshooting
EtherNet/IP Client/Server Communication Module User Manual
Moving Back Through 5 Pages of Registers
Press [-] from the Database View menu to skip five pages back in the database
to see the 100 registers of data starting 500 registers before the currently
displayed page.
Moving Forward (Skipping) Through 5 Pages of Registers
Press [+]
from the Database View menu to skip five pages ahead in the database
to see the 100 registers of data starting 500 registers after the currently displayed
page.
Viewing the Previous Page of Registers
Press [P] from the Database View menu to display the previous page of data.
Viewing the Next Page of Registers
Press [N] from the Database View menu to display the next page of data.
Viewing Data in Decimal Format
Press [D] from the Database View menu to display the data on the current page
in decimal format.
Viewing Data in Hexadecimal Format
Press [H] from the Database View menu to display the data on the current page
in hexadecimal format.
Viewing Data in Floating-Point Format
Press [F] from the Database View menu to display the data on the current page
in floating-point format. The program assumes that the values are aligned on
even register boundaries. If floating-point values are not aligned as such, they
are not displayed properly.
Viewing Data in ASCII (Text) Format
Press [A] from the Database View menu to display the data on the current page
in ASCII format. This is useful for regions of the database that contain ASCII
data.
Returning to the Main Menu
Press [M] to return to the Main menu.
ProSoft Technology, Inc. Page 61 of 177
October 12, 2010
Diagnostics and Troubleshooting MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
3.2.5 Master Command Error List Menu
Use this menu to view the command error list for the module. Press [?] to view a
list of commands available on this menu.
Redisplaying the Current Page
Press [S] to display the current page of data.
Moving Back Through 5 Pages of Commands
Press [-] to display data for last 5 page commands.
Viewing the Previous Page of Commands
Press [P] to display the previous page of commands.
Moving Forward (Skipping) Through 5 Pages of Commands
Press [+] to display data for the next page of commands.
Viewing the Next Page of Commands
Press [N] to display the next page of commands.
Returning to the Main Menu
Press [M] to return to the Main menu.
Page 62 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Diagnostics and Troubleshooting
EtherNet/IP Client/Server Communication Module User Manual
3.2.6 Master Command List Menu
Use this menu to view the command list for the module. Press [?] to view a list of
commands available on this menu.
Redisplaying the Current Page
Press [S] to display the current page of data.
Viewing the Previous 50 Commands
Press [-] to view the previous 50 commands.
Viewing the Previous Page of Commands
Press [P] to display the previous page of commands.
Viewing the Next 50 Commands
Press [+] to view the next 50 commands from the master command list.
Viewing the Next Page of Commands
Press [N] to display the next page of commands.
Returning to the Main Menu
Press [M] to return to the Main menu.
ProSoft Technology, Inc. Page 63 of 177
October 12, 2010
Diagnostics and Troubleshooting MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
3.2.7 Network Menu
From the IEC-870-5-104 Server menu press [@] to display the IEC-870-5-104
Network menu screen. The Network menu allows you to send, receive, and view
the WATTCP.CFG file that contains the IP and module addresses, and other
network information.
Transferring WATTCP.CFG to the Module
Press [R] to transfer a new WATTCP.CFG file from the PC to the module. Use
this command to change the network configuration for the module (for example,
the module’s IP address).
Press [Y] to confirm the file transfer, and then follow the instructions on the
terminal screen to complete the file transfer process.
Transferring WATTCP.CFG to the PC
Press [S] to transfer the WATTCP.CFG file from the module to your PC.
Press [Y] to confirm the file transfer, and then follow the instructions on the
terminal screen to complete the file transfer process.
After the file has been successfully transferred, you can open and edit the file to
change the module’s network configuration.
Page 64 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Diagnostics and Troubleshooting
EtherNet/IP Client/Server Communication Module User Manual
Viewing the WATTCP.CFG File on the module
Press [V] to view the module’s WATTCP.CFG file. Use this command to confirm
the module’s current network settings.
Returning to the Main Menu
Press [M] to return to the Main menu.
ProSoft Technology, Inc. Page 65 of 177
October 12, 2010
Diagnostics and Troubleshooting MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
3.3 Reading Status Data from the Module
The MVI46-DFNT module returns two status data blocks that can be used to
determine the module’s operating status. This data is requested by the ladder
logic and returned in the module’s M1 file. This data can also be viewed using
the Configuration/Debug port with a terminal emulation program. The
Configuration/Debug port provides the following functionality:
Full view of the module’s configuration data
View of the module’s status data
Complete display of the module’s internal database (registers 0 to 3999)
Version Information
Control over the module (warm boot, cold boot)
Facility to upload and download the module’s configuration file
Page 66 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
4 Reference
In This Chapter
Product Specifications ........................................................................... 68
Functional Overview .............................................................................. 71
Cable Connections ................................................................................ 81
Pass-Through Ports .............................................................................. 85
MVI46-DFNT Status Data Definition ...................................................... 86
Error Codes ......................................................................................... 101
TCP/IP Interface Errors ....................................................................... 105
Configuration Data .............................................................................. 107
DFNT Command Entry Form ............................................................... 110
Command Function Codes .................................................................. 112
General Command Structure ............................................................... 113
PLC-5 Processor Specifics .................................................................. 128
SLC Processor Specifics ..................................................................... 130
MicroLogix Processor Specifics ........................................................... 131
ControlLogix Processor Specifics ........................................................ 132
Server Driver ....................................................................................... 133
Accessing an SLC 5 Processor via Ethernet Using MVI46-DFNT ....... 158
Frequently Asked Questions ............................................................... 162
ProSoft Technology, Inc. Page 67 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
4.1 Product Specifications
The MVI46 EtherNet/IP (DF1 for Ethernet) Client/Server Communication Module
is a Rockwell Automation SLC backplane compatible module that allows SLC
processors to interface easily with EtherNet/IP protocol (Explicit Messaging)
compatible devices and hosts. Devices commonly supporting the protocol include
Rockwell Automation PLCs, and host HMI systems.
The MVI46-DFNT module is a single slot solution that provides a powerful
connection between Rockwell Automation’s SLC processor and EtherNet/IP
(DF1 for Ethernet) network applications.
The module can send read or write commands to remote devices on the
EtherNet/IP network. The MVI46-DFNT also has 20 servers that allow the
module to receive commands from remote devices. The MVI46-DFNT PassThrough server allows the user to edit and transfer the SLC ladder logic using an
Ethernet connection. Up to 100 commands can be configured by the user.
4.1.1 EtherNet/IP (Explicit Messaging) Compatible Devices
List of Rockwell Automation material that support EPIC:
PLC5/E rev C/N, D/E, E/D
SLC5/05 series A, OS503 frn4
1785-ENET Series A, rev D
Interchange V6.2
MicroLogix 1100/1400/ANY via 1761-NET-ENI
CompactLogix 1768-L43/L45 via 1768-ENBT
CompactLogix 1769-L32E/L35E/ANY via 1761-NET-ENI
CompactLogix L23E
RSLinx Gateway V1.7+
ControlLogix 1756-ENET/ENBT/EN2T
4.1.2 General Specifications
Single Slot - 1746 backplane compatible (Local or extended I/O rack only.
Remote rack not supported)
The module is recognized as an Input/Output module and has access to
processor memory for data transfer between processor and module using
M0/M1 files
Ladder Logic is used for data transfer between module and processor.
Sample ladder file included
Configuration data obtained from configuration text file downloaded to
module. Sample configuration file included
Page 68 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
4.1.3 Hardware Specifications
Specification Description
Backplane Current Load 800 ma @ 5V (from backplane)
Operating Temperature 0 to 60°C (32 to 140°F)
Storage Temperature -40 to 85°C (-40 to 185°F)
Relative Humidity 5% to 95% (non-condensing)
Shock 30g operational, 50g non-operational
Vibration 5 g from 10150 Hz
Processor Compatible with Rockwell Automation SLC 5/02
M0/M1 capable processors or newer
LED indicators Module status, Backplane transfer status,
Application status, Serial activity (debug port),
Ethernet link and activity, and error LED status
Debug/Configuration port (CFG)
CFG Port (CFG) RJ45 (DB-9M with supplied cable)
RS-232 only
No hardware handshaking
Configuration Connector RJ45 RS-232 Connector (RJ45 to DB-9 cable
shipped with unit)
Application Ports
Ethernet Port (Ethernet Modules) RJ45 Connector
Link and activity LED indicators
Electrical Isolation 1500 V rms at 50 Hz to 60 Hz
for 60 s, applied as specified in section 5.3.2 of
IEC 60950: 1991
Ethernet Broadcast Storm Resiliency = less than
or equal to 5000 [ARP] frames-per-second and
less than or equal to 5 minutes duration
ProSoft Technology, Inc. Page 69 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
4.1.4 Functional Specifications
Rockwell Automation 5/02/03/04 processors with DH-485 or DH+ network
connections to co-exist with EtherNet/IP network
SLC 5/05 in-chassis EtherNet/IP bridge to optimize data throughput while
communicating with HMI or SCADA and other control platforms without losing
valuable process control bandwidth
Support of up to 4000 SLC registers user data files
User-definable module memory usage
10/100 Base-T Ethernet compatible interface
Functions as a server or a client
Configurable parameters for the client include:
o A minimum response delay of 0 to 65535 milliseconds
o A response timeout of 1 to 65535 milliseconds
o A retry count of 0 to 20
Status data available in ladder logic
Support for SLC processor programming over Ethernet using a TCP/IP service
and a serial port on the module connected to channel 0 of the processor (3rd
party driver required, not included). The module’s third port emulates Channel 0
of the processor to pass through messages from the port to the processor
Server Specifications
Supports EtherNet/IP explicit, connected, and unconnected class messaging
Twenty independent server connections permit remote clients to interact with
all data contained in the module
Data can be derived from other clients on the network, through the client on
the module, or from the SLC processor
Client Specifications
Actively issues connected, explicit messages to other nodes on the network
Supports 100 user-defined commands from a single client
Allows command control from ladder logic
Pass-through services
Permits remote programming of the SLC processor on the Ethernet network
via a pass-through (3rd party driver required, not included)
TCP/IP service and a serial communication port (pass-through port) on the
module (3rd party driver required, not included)
A PC with RSLogix 500, RSLinx, and a TCP/IP service on the network can
remotely program the SLC (3rd party driver required, not included)
The third port on the module can emulate the Channel 0 port on the SLC.
This allows a DF1 master device attached to the emulated (Channel 0) port to
monitor and control data in the SLC
Page 70 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
4.2 Functional Overview
4.2.1 General Concepts
The following discussion explains several concepts that are important for
understanding module operation.
Backplane Data Transfer
The MVI46-DFNT module communicates directly over the SLC backplane. All
data for the module is contained in the module's M1 file. Data is moved between
the module and the SLC processor across the backplane using the module's M1
file. The SLC scan rate and the communication load on the module determine the
update frequency of the M1 file. The COP instruction can be used to move data
between user data files and the module's M1 file.
The following illustration shows the data transfer method used to move data
between the SLC processor, the MVI46-DFNT module, and the TCP/IP Network.
As shown in the diagram, all data transferred between the module and the
processor over the backplane is through the M1 file. Ladder logic must be written
in the SLC processor to interface the M1 file data in the module's internal
database. All data used by the module is stored in its internal database. The
following illustration shows the layout of the database:
Module’s Internal Database Structure
4000 registers for user data
0
3999
1000 registers for command control 4000
M1 File
4999
Data registers in the module above 4000 are used for command control. When
special values are written in this register set, the module performs specific
functions. The following topics define the special functions handled by the
module.
ProSoft Technology, Inc. Page 71 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
4.2.2 Module Control Blocks (4000 to 4999)
As discussed in the previous section, range 4000 to 4999 in the M1 file controls
the module in order to perform specific tasks. These tasks are described in the
following topics. Word 4000 contains the block ID that identifies the block to the
MVI46-DFNT module. The block structure, which is different for each block, is
shown in the following topics.
Status Data Request
When the user wants to read the module’s general error and status data to the
SLC, it must make a special request using the command control area. The
following tables lists the two values recognized by the module in register 4000 to
request the data:
Control Code Content Description
250 General Status data for the module, client and pass-through server
251 DFNT Servers Status data for each of the 5 DFNT servers
Refer to MVI46-DFNT Status Data Definition (page 86) for a complete listing of
the data returned for the two status blocks.
Initialize Output Data
When the module performs a restart operation, it requests output data from the
processor to initialize the module’s output data. This mode is selected using the
Initialize Output Data parameter in the configuration file. This facility can be
used to bring the module to a known state after the restart operation. The
structure of the block used to request the data is shown in the following table.
Offset Description / Value Length
4000 1000 1
The command control value of 1000 is placed in register 4000 of the M1 file to
indicate that the module is requesting initialization of the M1 data file. Ladder
logic in the processor must recognize this command and place the correct
information in the M1file. After the data transfer is complete, the ladder logic
should place a value of 1001 in register 4000 of the module’s M1 file. The format
of the returned write block is shown in the following table.
Offset Description / Value Length
4000 1001 1
Page 72 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
Command Error List Request
This command control request (control code of 2000) requests a set of data from
the command list error data set. The error codes returned in the block are DFNT
error codes noted in Status Data Definition. The format of the request block from
the ladder logic has the following format:
M1-File Offset Description
4000 This field contains the command code value of 2000
4001 This field contains the starting command index for the first error to
report. This field has a range of 0 to 99.
4002 This field contains the number of command error list values to report
in the response block. This register has a range from 1 to 60.
After the module processes the block, it supplies the following values in the
control register area:
M1-File Offset Description
4000 This field will be set to a value of 0 to indicate the function is complete.
4001 This field contains the command code value of 2000 requested
4002 This field contains the starting command index reported in the
response block.
4003 This field contains the number of command error list values in the
response block.
4004 to 4063 This data area contains the error codes for each of the command in
the module.
ProSoft Technology, Inc. Page 73 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
Command Control
Use Blocks 3000 to 3002 to alter the command type field for a set of commands
in the client command lists. Block 3000 disables commands by setting the enable
type field to value of 0. Block 3001 enables commands by setting the enable type
field to a value of 1. The commands will be issued at the time interval no more
frequent than set in the poll interval parameter for the command. Block 3002 sets
the enable type field to a value of 2. This operation should only be used for write
functions as the command is only executed when the data referenced by the
command changes. The general format for the blocks is as follows:
M1-File Offset Description
4000 This field contains the command code value of 3000 to 3002
4001 This field contains the number of commands from the first command
defined in the 4001 register to apply the new code. The register has a
range of 1 to 60.
4002 This field contains the starting command index to apply the new
enable type code to. This field has a range of 0 to 99.
After the module processes the block, it supplies the following values in the
control register area:
M1-File Offset Description
4000 This field will be set to a value of 0 to indicate the function is complete.
4001 This field contains the command code value of 3000 to 3002
requested
4002 This field contains the number of commands processed by the
module.
Warm Boot Block (9998)
This block is sent from the SLC processor to the module when the module is
required to perform a warm-boot (software reset) operation. This block is
commonly sent to the module any time configuration data modifications are made
in the controller tags data area. This causes the module to read the new
configuration information and to restart. The following table describes the format
of the control block.
Offset Description / Value Length
4000 9998 1
Cold Boot Block (9999)
This block is sent from the SLC processor to the module when the module is
required to perform the cold boot (hardware reset) operation. This block is sent to
the module when a hardware problem is detected by the ladder logic that
requires a hardware reset. The following table describes the format of the control
block.
Offset Description / Value Length
4000 9999 1
Page 74 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
4.2.3 Data Flow between MVI46-DFNT Module and SLC Processor
The following discussion outlines the flow of data between the two pieces of
hardware (SLC processor and MVI46-DFNT module) and other nodes on the
TCP/IP network under the module’s different operating modes. The module
contains both servers and a client. The servers accept TCP/IP connections on
service port AF12. The client establishes connections to service port AF12
(hexadecimal) on other EtherNet/IP servers.
The following topics discuss the operation of the server and client drivers.
Server Driver
The Server Driver allows the MVI46-DFNT module to respond to data read and
write commands issued by clients on the EtherNet/IP network using explicit
messaging. The following flow chart and associated table describe the flow of
data into and out of the module.
Step Description
1
2 A Host device, such as a SLC processor, RSLinx or an HMI application issues a read or
3 After the module accepts the command, the data is immediately transferred to or from
4 After the data processing has been completed in Step 3, the response is issued to the
5 Status data for the servers is passed to the processor under ladder logic control using
The server driver receives the configuration information from the configuration file on the
Compact Flash Disk, and the module initializes the servers.
write command to the module. The server driver qualifies the message before accepting
it into the module.
the internal database in the module. If the command is a read command, the data is
read out of the database and a response message is built. If the command is a write
command, the data is written directly into the database and the M1 file and a response
message is built.
originating master node.
the command control data area in the M1 file.
ProSoft Technology, Inc. Page 75 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
The DFNT module supports server functionality using the reserved ControlNet
service port 0xAF12. Services supported in the module permit client applications
(that is, RSView, ControlLogix processors and RSLinx) to read from and write to
the module’s database. This document discusses the requirements for attaching
to the module using several client applications.
The following illustration shows the relationship of the DFNT module’s
functionality to devices on an Ethernet network:
Server functionality places all data transfer operations outside the module. There
is no configuration required in the module other than setting up the network and
database parameters in the configuration file. Ladder logic in attached
processors use MSG instructions to perform read and write operations on the
module’s internal database.
When RSLinx links a user application to the module, the module’s server
functionality must be used. RSLinx exists on an Ethernet network only as a client
application. It cannot act as a server. User applications can use the DDE/OPC
capabilities built into RSLinx to interface with the data in the DFNT module.
RSView can link directly to the module using drivers supplied by RSLinx.
The internal database of the DFNT module is used as the source (read requests)
and destination (write requests) for requests from remote clients. Access to the
database depends on the MSG command type executed to interface with the
database. The following table defines the relationship of the module’s internal
database to the addresses required in the MSG instructions:
Page 76 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
MSG Instruction Type
Database Address PLC2 PLC5 or SLC ControlLogix
PCCC CIP Integer
0 0 N10:0 N10:0 Int_data[0]
999 999 N19:99 N19:99 Int_data[999]
1000 1000 N20:0 N20:0 Int_data[1000]
1999 1999 N29:99 N29:99 Int_data[1999]
2000 2000 N30:0 N30:0 Int_data[2000]
2999 2999 N39:99 N39:99 Int_data[2999]
3000 3000 N40:0 N40:0 Int_data[3000]
3999 4000 N49:99 N49:99 Int_data[3999]
MSG Instruction Type
Database
Address
0 BoolData[0] BitAData[0] SIntData[0] DIntData[0] RealData[0]
999 BoolData[15984] SIntData[1998]
1000 BoolData[16000] BitAData[500] SIntData[2000] DIntData[500] RealData[500]
1999 BoolData[31984] SIntData[3998]
2000 BoolData[32000] BitAData[1000] SIntData[4000] DIntData[1000] RealData[1000]
2999 BoolData[47984] SIntData[5998]
3000 BoolData[48000] BitAData[1500] SIntData[6000] DIntData[1500] RealData[1500]
3999 BoolData[63999] SIntData[9998]
CIP Boolean ControlLogix
CIP Bit Array CIP Byte CIP Double
CIP Real
Int
When using PLC5 or SLC commands, access to the database is through
simulated "N" files. For example, to access database element 3012, use the file
address of N40:12. When using CIP Data Table Read or Write commands, use
the various data[ ] tag arrays described in the following table. For example, use
int_data[3012] to access database register 3012 as an integer value.
Data Type Tag Name Length of Each Element in
CIP message
BOOL BOOLData[ ] 1 0 to 63999
Bit Array BITAData[ ] 4 0 to 1999
SINT SINTData[ ] 1 0 to 7999
INT INT_Data[ ] 2 0 to 3999
DINT DINTData[ ] 4 0 to 1999
REAL REALData[ ] 4 0 to 1999
Array Range for 4000
Element Database
ProSoft Technology, Inc. Page 77 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
Before attempting to use the module on a network, verify that the DFNT module
is correctly configured and connected to the network. A network program such as
PING can be utilized to make certain the module can be seen on the network.
Use ProSoft Configuration Builder to verify correct operation, and to transfer
configuration files to and from the module.
The following table shows the supported commands when the module acts as a
slave (server):
Basic Command Set Functions
Command Function Definition Supported in Slave
0x00 N/A Protected Write X
0x01 N/A Unprotected Read X
0x02 N/A Protected Bit Write X
0x05 N/A Unprotected Bit Write X
0x08 N/A Unprotected Write X
PLC-5 Command Set Functions
Command Function Definition Supported in Slave
0x0F 0x00 Word Range Write (Binary Address) X
0x0F 0x01 Word Range Read (Binary Address) X
0x0F Typed Range Read (Binary Address) X
0x0F Typed Range Write (Binary Address) X
0x0F 0x26 Read-Modify-Write (Binary Address)
0x0F 0x00 Word Range Write (ASCII Address) X
0x0F 0x01 Word Range Read (ASCII Address) X
0x0F 0x26 Read-Modify-Write (ASCII Address)
SLC-500 Command Set Functions
Command Function Definition Supported in Slave
0x0F 0xA1 Protected Typed Logical Read With Two Address
Fields
0x0F 0XA2 Protected Typed Logical Read With Three Address
Fields
0x0F 0XA9 Protected Typed Logical Write With Two Address
Fields
0x0F 0XAA Protected Typed Logical Write With Three Address
Fields
0x0F 0XAB Protected Typed Logical Write With Mask (Three
Address Fields)
X
X
X
X
Page 78 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
Client Driver
In the client driver, the MVI46-DFNT module is responsible for issuing read or
write commands to servers on the EtherNet/IP network using explicit, connected
messaging. These commands are user configured in the module via the Client
Command List received from the module's configuration file (DFNT.CFG).
Command status is returned to the processor for each individual command in the
command list status block in the command control data area. Ladder logic is
responsible for acquiring this data from the module. The following flow chart and
associated table show the flow of data into and out of the module.
Step Description
1
2 After configuration, the client driver begins transmitting read and/or write commands to
3 Presuming successful processing by the node specified in the command, a response
4 Data received from the node on the network is passed into the module's internal
5 Status data is returned to the SLC processor for the client and a Command List error
The client driver obtains configuration data from the DFNT.CFG file when the module
restarts. The configuration data obtained includes the timeout parameters and the
Command List. These values are used by the driver to determine the type of commands
to be issued to the other nodes on the EtherNet/IP (see Module Configuration).
the other nodes on the network. If writing data to another node, the data for the write
command is obtained from the module's internal database to build the command.
message is received into the client driver for processing.
database, assuming a read command.
table can be established in the module's internal database. This data is requested using
the command control data area and is a responsibility of the ladder logic.
The Module Setup section provides a complete description of the parameters
required to define the client.
ProSoft Technology, Inc. Page 79 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
Client Command List
In order for the client to function, the module's Client Command List must be
defined. This list contains up to 100 individual entries, with each entry containing
the information required to construct a valid command. This includes the
following:
Command enable mode ((0) disabled, (1) continuous or (2) conditional)
IP address of the remote server
Slot number for processor when interfacing with a SLC processor
Command Type - Read or Write command
Database Source and Destination Register Address - Determines where data
will be placed and/or obtained
Address information to access data in remote unit
Count - Select the number of words to be transferred
Poll Delay - (1/10
th
seconds)
Page 80 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
4.3 Cable Connections
The MVI46-DFNT module has the following functional communication
connections installed:
One Ethernet port (RJ45 connector)
One RS-232 Configuration/Debug port (RJ45 connector)
4.3.1 Ethernet Connection
The MVI46-DFNT module has an RJ45 port located on the front of the module,
labeled Ethernet, for use with the TCP/IP network. The module is connected to
the Ethernet network using an Ethernet cable between the module’s Ethernet
port and an Ethernet switch or hub.
Note: Depending on hardware configuration, you may see more than one RJ45 port on the
module. The Ethernet port is labeled Ethernet.
Warning: The MVI46-DFNT module is NOT compatible with Power Over Ethernet (IEEE802.3af /
IEEE802.3at) networks. Do NOT connect the module to Ethernet devices, hubs, switches or
networks that supply AC or DC power over the Ethernet cable. Failure to observe this precaution
may result in damage to hardware, or injury to personnel.
Important: The module requires a static (fixed) IP address that is not shared with any other device
on the Ethernet network. Obtain a list of suitable IP addresses from your network administrator
BEFORE configuring the Ethernet port on this module.
ProSoft Technology, Inc. Page 81 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
Ethernet Port Configuration - wattcp.cfg
The wattcp.cfg file must be set up properly in order to use a TCP/IP network
connection. You can view the current network configuration in ProSoft
Configuration Builder (PCB), as shown:
You may also view the network configuration using a PC serial port connection
and an ASCII terminal program (like Windows HyperTerminal) by selecting [@]
(Network Menu) and [V] (View) options when connected to the Debug port. For
more information on serial port access, see the chapter on Diagnostics and
Troubleshooting (page 47).
4.3.2 RS-232 Configuration/Debug Port
This port is physically an RJ45 connection. An RJ45 to DB-9 adapter cable is
included with the module. This port permits a PC based terminal emulation
program to view configuration and status data in the module and to control the
module. The cable for communications on this port is shown in the following
diagram:
Page 82 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
Disabling the RSLinx Driver for the Com Port on the PC
The communication port driver in RSLinx can occasionally prevent other
applications from using the PC’s COM port. If you are not able to connect to the
module’s configuration/debug port using ProSoft Configuration Builder (PCB),
HyperTerminal or another terminal emulator, follow these steps to disable the
RSLinx Driver.
1 Open RSLinx and go to C
OMMUNICATIONS>RSWHO
2 Make sure that you are not actively browsing using the driver that you wish to
stop. The following shows an actively browsed network:
3 Notice how the DF1 driver is opened, and the driver is looking for a processor
on node 1. If the network is being browsed, then you will not be able to stop
this driver. To stop the driver your RSWho screen should look like this:
Branches are displayed or hidden by clicking on the or the icons.
4 When you have verified that the driver is not being browsed, go to
COMMUNICATIONS>CONFIGURE DRIVERS
You may see something like this:
ProSoft Technology, Inc. Page 83 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
If you see the status as running, you will not be able to use this com port for
anything other than communication to the processor. To stop the driver press
the S
TOP button on the side of the window:
5 After you have stopped the driver you will see the following:
6 You may now use the com port to connect to the debug port of the module.
Note: You may need to shut down and restart your PC before it will allow you to stop the driver
(usually only on Windows NT machines). If you have followed all of the above steps, and it will not
stop the driver, then make sure you do not have RSLogix open. If RSLogix is not open, and you
still cannot stop the driver, then reboot your PC.
4.3.3 DB9 to RJ45 Adaptor (Cable 14)
Page 84 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
4.4 Pass-Through Ports
Two pass-through ports are provided on the module. Port 2 can be connected to
the processor’s Channel 0 port and Port 3 can be connected to a remote DF1
master device. The cable configuration used on the ports depends on the RSinterface selected for the port using the jumpers located on the MVI circuit board.
The following are port pin-outs for several configurations of the ports:
ProSoft Technology, Inc. Page 85 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
4.5 MVI46-DFNT Status Data Definition
This section contains a description of the members present in the status data
blocks returned to the SLC processor under ladder logic control. The two blocks,
250 and 251, are requested and returned in the module's M1 file in the command
control data area under ladder logic control.
The data set returned to the processor in the M1 file for a 250 request has the
following definition:
Offset Content Description
4000 Done Flag This word contains a value of 0 to indicate the status block
is completely built
4001 Status Code This word contains the value 250
4002 Program Scan
Count
4003 to 4004 Product Product Name (ASCII)
4005 to 4006 Rev Revision (ASCII)
4007 to 4008 Op Sys Operating System (ASCII)
4009 to 4010 Run Production Run Number (ASCII)
This value is incremented each time a complete program
cycle occurs in the module.
4.5.1 HTTP Port 80 Status
Offset Content Description
4011 Not Used Reserved
4012 Not Used Reserved
4013 Not Used Reserved
4014 Number of Requests Total number of http requests for the module
4015 Number of Responses Total number of http response messages generated.
4016 Not Used Reserved
4017 Not Used Reserved
4018 Not Used Reserved
4019 Not Used Reserved
4020 Not Used Reserved
Page 86 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
4.5.2 DFNT Client 0 Status
Offset Content Description
4021 Client Cmd Request This value is incremented each time a command request is
issued.
4022 Client Cmd Response This value is incremented each time a command response
is received.
4023 Client Cmd Error This value is incremented each time an error message is
received from a remote unit or a local error is generated for
a command.
4024 Client Request Count This value is incremented each time a request message is
issued.
4025 Client Response
Count
4026 Client Error Sent
Count
4027 Client Error Received
Count
4028 Client Cfg Error Word This word contains a bit map that defines configuration
4029 Client Current Error
Code
4030 Client Last Error Code This value corresponds to the last error code recorded for
This value is incremented each time a response message is
received.
This value is incremented each time an error is sent from
the client.
This value is incremented each time an error is received
from a remote unit.
errors in the configuration file for the client.
This value corresponds to the current error code for the
client.
the client.
4.5.3 Block Status
Offset Content Description
4031 Read Block Count This field contains the total number of read blocks
transferred from the module to the processor.
4032 Write Block Count This field contains the total number of write blocks
transferred from the processor to the module.
4033 Parse Block Count This field contains the total number of blocks successfully
parsed that were received from the processor.
4034 Command Event Block
Count
4035 Command Block
Count
4036 Error Block Count This field contains the total number of block errors
This field contains the total number of command event
blocks received from the processor.
This field contains the total number of command blocks
received from the processor.
recognized by the module.
ProSoft Technology, Inc. Page 87 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
4.5.4 Pass-Through Server Status
Offset Content Description
4037 Socket State
4038 Connection State
4039 Open Count Total number of times the server has performed an open
operation.
4040 Establish Count Total number of times a connection has been established on
the server.
4041 Close Count Total number of times the server has performed a close
operation.
4042 Read Total number of packets received by the server.
4043 Message Total number of message receive by the server.
4044 Write Total number of packets sent from the server to the client.
4045 Timeout Total number of times the server as reached a connection
timeout condition.
4046 Host Port Service port on client connected to the server.
4047 to
4048
4049 PTP Cfg Error Word Pass-through port configuration error word.
4050 PTS Cfg Error Word Pass-through server configuration error word.
Host IP Address IP address of the client connected to the server.
The format of the client configuration error word is as follows:
Bit Description Value
0 0x0001
1 0x0002
2 0x0004
3 0x0008
4 Invalid retry count (0 to 10) 0x0010
5 0x0020
6 0x0040
7 0x0080
8 0x0100
9 0x0200
10 0x0400
11 0x0800
12 0x1000
13 0x2000
14 0x4000
15 0x8000
Page 88 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
The format of the pass-through port configuration error word is as follows:
Bit Description Value
0 Invalid enable code 0x0001
1 Invalid local station ID 0x0002
2 Invalid protocol or termination type 0x0004
3 Invalid baud rate 0x0008
4 Invalid parity 0x0010
5 Invalid data bits 0x0020
6 Invalid stop bits 0x0040
7 0x0080
8 Invalid Use CTS Line selection 0x0100
9 Invalid retry count 0x0200
10 0x0400
11 0x0800
12 0x1000
13 0x2000
14 0x4000
15 0x8000
The format of the pass-through server configuration error word is as follows:
Bit Description Value
0 Invalid enable code 0x0001
1 Invalid busytimeout setting (< 100 milliseconds) 0x0002
2 0x0004
3 0x0008
4 0x0010
5 Invalid baud rate 0x0020
6 Invalid parity 0x0040
7 Invalid data bits 0x0080
8 Invalid stop bits 0x0100
9 0x0200
10 0x0400
11 0x0800
12 0x1000
13 0x2000
14 0x4000
15 0x8000
ProSoft Technology, Inc. Page 89 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
The values for the pass-through server state parameter have the following
definition:
State Definition
-1 Listen function called to set up server
0 Waiting for connection to be established on server
1 Waiting and processing data received
2 Waiting for pass-through port to be free
3 Pass-through server owns port and processes all data
received and written.
100 Closing server on program termination
1000 Initiate a close on the server
1001 Waiting for server to successfully close
The connection state for the pass-through server is not used at this time.
The data set returned to the processor in the M1 file for a 251 request has the
following definition:
Offset Content Description
4000 Done Flag This word contains a value of 0 to indicate the status block
is completely built
4001 Status Code This word contains the value 251
4.5.5 DFNT Server 0 Status
Offset Content Description
4002 Socket State
4003 Connection State
4004 Open Count Total number of times the server has performed an open
operation.
4005 Establish Count Total number of times a connection has been established on
the server.
4006 Close Count Total number of times the server has performed a close
operation.
4007 Read Total number of packets received by the server.
4008 Message Total number of message receive by the server.
4009 Write Total number of packets sent from the server to the client.
4010 Timeout Total number of times the server as reached a connection
timeout condition.
4011 Host Port Service port on client connected to the server.
4012 to
4013
Page 90 of 177 ProSoft Technology, Inc.
October 12, 2010
Host IP Address IP address of the client connected to the server.
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
4.5.6 DFNT Server 1 Status
Offset Content Description
4014 Socket State
4015 Connection State
4016 Open Count Total number of times the server has performed an open
operation.
4017 Establish Count Total number of times a connection has been established on
the server.
4018 Close Count Total number of times the server has performed a close
operation.
4019 Read Total number of packets received by the server.
4020 Message Total number of message receive by the server.
4021 Write Total number of packets sent from the server to the client.
4022 Timeout Total number of times the server as reached a connection
timeout condition.
4023 Host Port Service port on client connected to the server.
4024 to
4025
Host IP Address IP address of the client connected to the server.
4.5.7 DFNT Server 2 Status
Offset Content Description
4026 Socket State
4027 Connection State
4028 Open Count Total number of times the server has performed an open
operation.
4029 Establish Count Total number of times a connection has been established on
the server.
4030 Close Count Total number of times the server has performed a close
operation.
4031 Read Total number of packets received by the server.
4032 Message Total number of message receive by the server.
4033 Write Total number of packets sent from the server to the client.
4034 Timeout Total number of times the server as reached a connection
timeout condition.
4035 Host Port Service port on client connected to the server.
4036 to
4037
Host IP Address IP address of the client connected to the server.
ProSoft Technology, Inc. Page 91 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
4.5.8 DFNT Server 3 Status
Offset Content Description
4038 Socket State
4039 Connection State
4040 Open Count Total number of times the server has performed an open
operation.
4041 Establish Count Total number of times a connection has been established on
the server.
4042 Close Count Total number of times the server has performed a close
operation.
4043 Read Total number of packets received by the server.
4044 Message Total number of message receive by the server.
4045 Write Total number of packets sent from the server to the client.
4046 Timeout Total number of times the server as reached a connection
timeout condition.
4047 Host Port Service port on client connected to the server.
4048 to
4049
Host IP Address IP address of the client connected to the server.
4.5.9 DFNT Server 4 Status
Offset Content Description
4050 Socket State
4051 Connection State
4052 Open Count Total number of times the server has performed an open
operation.
4053 Establish Count Total number of times a connection has been established on
the server.
4054 Close Count Total number of times the server has performed a close
operation.
4055 Read Total number of packets received by the server.
4056 Message Total number of message receive by the server.
4057 Write Total number of packets sent from the server to the client.
4058 Timeout Total number of times the server as reached a connection
timeout condition.
4059 Host Port Service port on client connected to the server.
4060 to
4061
Host IP Address IP address of the client connected to the server.
Page 92 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
4.5.10 DFNT Server 5 Status
Offset Content Description
4062 Socket State
4063 Connection State
4064 Open Count Total number of times the server has performed an open
operation.
4065 Establish Count Total number of times a connection has been established on
the server.
4066 Close Count Total number of times the server has performed a close
operation.
4067 Read Total number of packets received by the server.
4068 Message Total number of message receive by the server.
4069 Write Total number of packets sent from the server to the client.
4070 Timeout Total number of times the server as reached a connection
timeout condition.
4071 Host Port Service port on client connected to the server.
4072 to
4073
Host IP Address IP address of the client connected to the server.
4.5.11 DFNT Server 6 Status
Offset Content Description
4074 Socket State
4075 Connection State
4076 Open Count Total number of times the server has performed an open
operation.
4077 Establish Count Total number of times a connection has been established on
the server.
4078 Close Count Total number of times the server has performed a close
operation.
4079 Read Total number of packets received by the server.
4080 Message Total number of message receive by the server.
4081 Write Total number of packets sent from the server to the client.
4082 Timeout Total number of times the server as reached a connection
timeout condition.
4083 Host Port Service port on client connected to the server.
4084 to
4085
Host IP Address IP address of the client connected to the server.
ProSoft Technology, Inc. Page 93 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
4.5.12 DFNT Server 7 Status
Offset Content Description
4086 Socket State
4087 Connection State
4088 Open Count Total number of times the server has performed an open
operation.
4089 Establish Count Total number of times a connection has been established on
the server.
4090 Close Count Total number of times the server has performed a close
operation.
4091 Read Total number of packets received by the server.
4092 Message Total number of message receive by the server.
4093 Write Total number of packets sent from the server to the client.
4094 Timeout Total number of times the server as reached a connection
timeout condition.
4095 Host Port Service port on client connected to the server.
4096 to
4097
Host IP Address IP address of the client connected to the server.
4.5.13 DFNT Server 8 Status
Offset Content Description
4098 Socket State
4099 Connection State
4100 Open Count Total number of times the server has performed an open
operation.
4101 Establish Count Total number of times a connection has been established on
the server.
4102 Close Count Total number of times the server has performed a close
operation.
4103 Read Total number of packets received by the server.
4104 Message Total number of message receive by the server.
4105 Write Total number of packets sent from the server to the client.
4106 Timeout Total number of times the server as reached a connection
timeout condition.
4107 Host Port Service port on client connected to the server.
4108 to
4109
Host IP Address IP address of the client connected to the server.
Page 94 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
4.5.14 DFNT Server 9 Status
Offset Content Description
4110 Socket State
4111 Connection State
4112 Open Count Total number of times the server has performed an open
operation.
4113 Establish Count Total number of times a connection has been established on
the server.
4114 Close Count Total number of times the server has performed a close
operation.
4115 Read Total number of packets received by the server.
4116 Message Total number of message receive by the server.
4117 Write Total number of packets sent from the server to the client.
4118 Timeout Total number of times the server as reached a connection
timeout condition.
4119 Host Port Service port on client connected to the server.
4120 to
4121
Host IP Address IP address of the client connected to the server.
4.5.15 DFNT Server 10 Status
Offset Content Description
4122 Socket State
4123 Connection State
4124 Open Count Total number of times the server has performed an open
operation.
4125 Establish Count Total number of times a connection has been established on
the server.
4126 Close Count Total number of times the server has performed a close
operation.
4127 Read Total number of packets received by the server.
4128 Message Total number of message receive by the server.
4129 Write Total number of packets sent from the server to the client.
4130 Timeout Total number of times the server as reached a connection
timeout condition.
4131 Host Port Service port on client connected to the server.
4132 to
4133
Host IP Address IP address of the client connected to the server.
ProSoft Technology, Inc. Page 95 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
4.5.16 DFNT Server 11 Status
Offset Content Description
4134 Socket State
4135 Connection State
4136 Open Count Total number of times the server has performed an open
operation.
4137 Establish Count Total number of times a connection has been established on
the server.
4138 Close Count Total number of times the server has performed a close
operation.
4139 Read Total number of packets received by the server.
4140 Message Total number of message receive by the server.
4141 Write Total number of packets sent from the server to the client.
4142 Timeout Total number of times the server as reached a connection
timeout condition.
4143 Host Port Service port on client connected to the server.
4144 to
4145
Host IP Address IP address of the client connected to the server.
4.5.17 DFNT Server 12 Status
Offset Content Description
4146 Socket State
4147 Connection State
4148 Open Count Total number of times the server has performed an open
operation.
4149 Establish Count Total number of times a connection has been established on
the server.
4150 Close Count Total number of times the server has performed a close
operation.
4151 Read Total number of packets received by the server.
4152 Message Total number of message receive by the server.
4153 Write Total number of packets sent from the server to the client.
4154 Timeout Total number of times the server as reached a connection
timeout condition.
4155 Host Port Service port on client connected to the server.
4156 to
4157
Host IP Address IP address of the client connected to the server.
Page 96 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
4.5.18 DFNT Server 13 Status
Offset Content Description
4158 Socket State
4159 Connection State
4160 Open Count Total number of times the server has performed an open
operation.
4161 Establish Count Total number of times a connection has been established on
the server.
4162 Close Count Total number of times the server has performed a close
operation.
4163 Read Total number of packets received by the server.
4164 Message Total number of message receive by the server.
4165 Write Total number of packets sent from the server to the client.
4166 Timeout Total number of times the server as reached a connection
timeout condition.
4167 Host Port Service port on client connected to the server.
4168 to
4169
Host IP Address IP address of the client connected to the server.
4.5.19 DFNT Server 14 Status
Offset Content Description
4170 Socket State
4171 Connection State
4172 Open Count Total number of times the server has performed an open
operation.
4173 Establish Count Total number of times a connection has been established on
the server.
4174 Close Count Total number of times the server has performed a close
operation.
4175 Read Total number of packets received by the server.
4176 Message Total number of message receive by the server.
4177 Write Total number of packets sent from the server to the client.
4178 Timeout Total number of times the server as reached a connection
timeout condition.
4179 Host Port Service port on client connected to the server.
4180 to
4181
Host IP Address IP address of the client connected to the server.
ProSoft Technology, Inc. Page 97 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
4.5.20 DFNT Server 15 Status
Offset Content Description
4182 Socket State
4183 Connection State
4184 Open Count Total number of times the server has performed an open
operation.
4185 Establish Count Total number of times a connection has been established on
the server.
4186 Close Count Total number of times the server has performed a close
operation.
4187 Read Total number of packets received by the server.
4188 Message Total number of message receive by the server.
4189 Write Total number of packets sent from the server to the client.
4190 Timeout Total number of times the server as reached a connection
timeout condition.
4191 Host Port Service port on client connected to the server.
4192 to
4193
Host IP Address IP address of the client connected to the server.
4.5.21 DFNT Server 16 Status
Offset Content Description
4194 Socket State
4195 Connection State
4196 Open Count Total number of times the server has performed an open
operation.
4197 Establish Count Total number of times a connection has been established on
the server.
4198 Close Count Total number of times the server has performed a close
operation.
4199 Read Total number of packets received by the server.
4200 Message Total number of message receive by the server.
4201 Write Total number of packets sent from the server to the client.
4202 Timeout Total number of times the server as reached a connection
timeout condition.
4203 Host Port Service port on client connected to the server.
4204 to
4205
Host IP Address IP address of the client connected to the server.
Page 98 of 177 ProSoft Technology, Inc.
October 12, 2010
MVI46-DFNT ♦ SLC Platform Reference
EtherNet/IP Client/Server Communication Module User Manual
4.5.22 DFNT Server 17 Status
Offset Content Description
4206 Socket State
4207 Connection State
4208 Open Count Total number of times the server has performed an open
operation.
4209 Establish Count Total number of times a connection has been established on
the server.
4210 Close Count Total number of times the server has performed a close
operation.
4211 Read Total number of packets received by the server.
4212 Message Total number of message receive by the server.
4213 Write Total number of packets sent from the server to the client.
4214 Timeout Total number of times the server as reached a connection
timeout condition.
4215 Host Port Service port on client connected to the server.
4216 to
4217
Host IP Address IP address of the client connected to the server.
4.5.23 DFNT Server 18 Status
Offset Content Description
4218 Socket State
4219 Connection State
4220 Open Count Total number of times the server has performed an open
operation.
4221 Establish Count Total number of times a connection has been established on
the server.
4222 Close Count Total number of times the server has performed a close
operation.
4223 Read Total number of packets received by the server.
4224 Message Total number of message receive by the server.
4225 Write Total number of packets sent from the server to the client.
4226 Timeout Total number of times the server as reached a connection
timeout condition.
4227 Host Port Service port on client connected to the server.
4228 to
4229
Host IP Address IP address of the client connected to the server.
ProSoft Technology, Inc. Page 99 of 177
October 12, 2010
Reference MVI46-DFNT ♦ SLC Platform
User Manual EtherNet/IP Client/Server Communication Module
4.5.24 DFNT Server 19 Status
Offset Content Description
4230 Socket State
4231 Connection State
4232 Open Count Total number of times the server has performed an open
operation.
4233 Establish Count Total number of times a connection has been established on
the server.
4234 Close Count Total number of times the server has performed a close
operation.
4235 Read Total number of packets received by the server.
4236 Message Total number of message receive by the server.
4237 Write Total number of packets sent from the server to the client.
4238 Timeout Total number of times the server as reached a connection
timeout condition.
4239 Host Port Service port on client connected to the server.
4240 to
4241
The following table defines the values represented in the Socket State
parameter:
State Definition
-1 Listen function called to set up server
0 Waiting for connection to be established on server
1 Handle first request and build response for first part of multi-request message.
2 Handle more requests in packet received.
100 Closing server on program termination
1000 Initiate a close on the server
1001 Waiting for server to successfully close
Host IP Address IP address of the client connected to the server.
The following table defines the values represented in the Connection State
parameter:
State Definition
0 No session exists on socket
1 Session established but no connections
2 Session established and connected
Page 100 of 177 ProSoft Technology, Inc.
October 12, 2010
Loading...