ProSoft Technology inRAx MVI46-DFNT User manual

MVI46-DFNT
SLC Platform
EtherNet/IP Interface Module
User Manual
November 5, 2004

ProSoft Technology, Inc. Page 2 of 118
November 9, 2004
Please Read This Notice
Successful application of this module requires a reasonable working knowledge of the SLC Platform
EtherNet/IP Interface Module hardware and the application in which the combination is to be used. For
this reason, it is important that those responsible for implementation satisfy themselves that the
combination will meet the needs of the application without exposing personnel or equipment to unsafe
or inappropriate working conditions.
This manual is provided to assist the user. Every attempt has been made to assure that the information
provided is accurate and a true reflection of the product's installation requirements. In order to assure a
complete understanding of the operation of the product, the user should read all applicable Allen-
Bradley documentation on the operation of the A-B hardware.
Under no conditions will ProSoft Technology, Inc. be responsible or liable for indirect or consequential
damages resulting from the use or application of the product.
Reproduction of the contents of this manual, in whole or in part, without written permission from ProSoft
Technology, Inc. is prohibited.
Information in this manual is subject to change without notice and does not represent a commitment on
the part of ProSoft Technology, Inc. Improvements and/or changes in this manual or the product may be
made at any time. These changes will be made periodically to correct technical inaccuracies or
typographical errors.
ProSoft Technology, Inc.
1675 Chester Avenue, 2nd Floor
Bakersfield, CA 93301
[phone]
[phone] (Fax)
www.prosoft-technology.com
Copyright ©ProSoft Technology, Inc. 2000 – 2004. All Rights Reserved.
MVI46-DFNT User Manual
November 5, 2004

Table of Contents MVI46-DFNT ♦SLC Platform
EtherNet/IP Interface Module
ProSoft Technology, Inc. Page 3 of 118
November 9, 2004
Table of Contents
PLEASE READ THIS NOTICE..........................................................................................................2
1INTRODUCTION.........................................................................................................................5
1.1 Using this Manual...........................................................................................................5
1.2 Product Specifications...................................................................................................5
1.2.1 General Specifications.................................................................................................. 6
1.2.2 Hardware Specifications ............................................................................................... 7
2FUNCTIONAL OVERVIEW......................................................................................................... 9
2.1 General Concepts........................................................................................................... 9
2.1.1 Module Power Up ......................................................................................................... 9
2.1.2 Main Logic Loop............................................................................................................ 9
2.1.3 Backplane Data Transfer ............................................................................................ 10
2.2 Module Control Blocks ................................................................................................ 11
2.2.1 Status Data Request................................................................................................... 12
2.2.2 Output Data Initialization Request .............................................................................. 12
2.2.3 Command Error List Request ..................................................................................... 12
2.2.4 Command Control....................................................................................................... 13
2.2.5 Warm Boot .................................................................................................................. 13
2.2.6 Cold Boot .................................................................................................................... 14
2.3 Data Flow between MVI46-DFNT Module and SLC Processor.................................14
2.3.1 Server Driver............................................................................................................... 14
2.3.2 Client Driver ................................................................................................................ 19
3MODULE CONFIGURATION ...................................................................................................21
3.1 Setting Up the Module.................................................................................................. 21
3.2 Module Data .................................................................................................................. 22
4LADDER LOGIC.......................................................................................................................23
4.1 Main Routine (U:2)........................................................................................................23
4.2 Data Transfer (U:3).......................................................................................................23
4.3 Control Routine (U:4)...................................................................................................23
5CONFIGURATION FILE...........................................................................................................29
5.1 Command List Overview.............................................................................................. 30
5.2 Commands Supported by the Module........................................................................ 30
5.3 Command Entry Formats............................................................................................. 31
6DIAGNOSTICS AND TROUBLESHOOTING........................................................................... 35
6.1 Reading Status Data From the Module ......................................................................35
6.1.1 Required Hardware..................................................................................................... 35

MVI46-DFNT ♦SLC Platform Table of Contents
EtherNet/IP Interface Module
Page 4 of 118 ProSoft Technology, Inc.
November 9, 2004
6.1.2 Required Software.......................................................................................................36
6.1.3 Using the Port..............................................................................................................36
6.1.4 Menu Options ..............................................................................................................36
6.2 LED Status Indicators...................................................................................................44
6.2.1 Clearing a Fault Condition...........................................................................................46
6.2.2 Troubleshooting...........................................................................................................46
7CABLE CONNECTIONS...........................................................................................................49
7.1 Ethernet Connection.....................................................................................................49
7.2 Pass-Through Ports......................................................................................................49
7.3 RS-232 Configuration/Debug Port...............................................................................50
8ETHERNET PORT CONFIGURATION: WATTCP.CFG...........................................................51
APPENDIX A - MVI46-DFNT STATUS DATA DEFINITION............................................................53
APPENDIX B - MVI46-DFNT CONFIGURATION DATA DEFINITION............................................67
APPENDIX C - EXAMPLE DFNT.CFG FILE ...................................................................................73
APPENDIX D: COMMAND FUNCTION CODES.............................................................................75
APPENDIX E: CLIENT CONFIGURATIONS FOR SERVER...........................................................87
RSLinx Software..........................................................................................................................87
DDE Connection ........................................................................................................................89
OPC Connection ........................................................................................................................93
ControlLogix (CLX) Processor...................................................................................................95
Encapsulated PCCC Messages ................................................................................................95
CIP Data Table Operations........................................................................................................98
PLC5 Processor.........................................................................................................................101
PLC5 Write Commands ...........................................................................................................101
PLC5 Read Commands...........................................................................................................102
SLC 5/05 Processor...................................................................................................................104
SLC5/05 Write Commands ......................................................................................................104
SLC5/05 Read Commands......................................................................................................105
RSView Software.......................................................................................................................106
APPENDIX F – ACCESSING AN SLC 5/03 PROCESSOR VIA ETHERNET USING MVI46-DFNT109
Troubleshooting........................................................................................................................112
APPENDIX G - FREQUENTLY ASKED QUESTIONS ..................................................................115
APPENDIX H - SUPPORT, SERVICE, AND WARRANTY............................................................117

Introduction MVI46-DFNT ♦SLC Platform
EtherNet/IP Interface Module
ProSoft Technology, Inc. Page 5 of 118
November 9, 2004
1 Introduction
This manual provides information on the MVI46-DFNT (EtherNet/IP Communication
Module) module.
1.1 Using this Manual
This manual contains the following sections:
Product Specifications
This section provides an overview of the MVI46-DFNT features. These features are
explained later in the following sections.
Functional Overview
This section provides details about how the module functions including how data is
transferred between the module and the SLC. This section also explains the module
control blocks and the supported commands. Finally it describes the server and
client drivers.
Module Configuration
This section describes the MVI46-DFNT configuration file in the RSLogix.
Ladder Logic
This section explains the sample ladder logic. ProSoft Technology, Inc. strongly
suggests that you use the sample ladder logic as a starting point to build your
application.
Configuration File
This section describes the configuration file. It also discusses the command list in
detail. Additional parameters are explained in Appendix B. Appendix C contains a
configuration file example.
Diagnostics and Troubleshooting
The section describes the debug port menu.
Cable Connections
The required cabling is discussed in detail in this section.
Wattcp.cfg
This section presents the Ethernet configuration file, used to set up the module IP
address and other TCP/IP network configurations.
1.2 Product Specifications
The MVI46-DFNT (“EtherNet/IP Communication Module”) product allows Allen-
Bradley SLC I/O compatible processors to easily interface with other EtherNet/IP
protocol compatible devices. Compatible devices include not only Allen-Bradley
controllers but also a wide assortment of other client and server devices. The
following is a list of
Ethernet/IP (Explicit Messaging) Compatible Devices:

MVI46-DFNT ♦SLC Platform Introduction
EtherNet/IP Interface Module
Page 6 of 118 ProSoft Technology, Inc.
November 9, 2004
List of A-B 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
•ControlLogix 1756-ENET
•RSLinx Gateway V1.7
1.2.1 General Specifications
The MVI46-DFNT module acts as a gateway between the EtherNet/IP, TCP/IP
network, and the Allen-Bradley backplane. The data transfer from the SLC processor
is asynchronous from the actions on the EtherNet/IP network. A 4000-word register
space in the module is used to exchange data between the processor and the
EtherNet/IP network.
Some of the general specifications include:
•Support for the storage and transfer of up to 4000 registers to/from the SLC
processor’s user data files
•Module memory usage that is completely user-definable
•10/100 MB Ethernet compatible interface
•Configurable parameters for the client include:
Minimum Response Delay: 0 to 65535 milliseconds
Response Timeout : 1 to 65535 milliseconds
Retry Count: 0 to 20
•The module permits programming of the SLC processor over Ethernet using
a TCP/IP service and a serial port on the module connected to Channel 0 of
the processor. In this configuration, the module’s third port emulates the
Channel 0 of the processor to pass-through messages from the port to the
processor.
1.2.1.1 Server Functional Specifications
The MVI46-DFNT module supports EtherNet/IP explicit, connected and unconnected
class messaging. The 20 servers permit remote clients to interact with all data
contained in the module. This data can be derived from other clients on the network,
through the client on the module, or from the SLC processor.
1.2.1.2 Client Specifications
A client configured as a EtherNet/IP device on the MVI46-DFNT module will actively
issue connected, explicit messages to other nodes on the network. One hundred
(100) user-defined commands are supported for the single client.
1.2.1.3 Pass-Through Services
The module permits remote programming of the SLC processor on the Ethernet
network using the built-in pass-through TCP service and a serial communication port
(pass-through port) on the module. DF1 messages passed from the RSLogix 500
software and RSLinx (using the DF1 serial driver and port redirection software) are

Introduction MVI46-DFNT ♦SLC Platform
EtherNet/IP Interface Module
ProSoft Technology, Inc. Page 7 of 118
November 9, 2004
placed on the Ethernet network. The module receives these messages and passes
them on to the SLC processor. This permits any node on the network to remotely
program the SLC processor. Only one connection is permitted to prevent confusion
during programming. When this feature is used, the third port on the module can
emulate the Channel 0 port on the SLC. A DF1 master device can be attached to this
port to monitor and control data in the SLC using the serial interface.
1.2.1.4 Physical
This module is designed by ProSoft Technology and incorporates licensed
technology from Allen-Bradley (SLC backplane technology).
•SLC Form Factor - Single Slot
•Connections:
o1 – RJ45 connector for Ethernet interface
o1 – RJ45 RS-232 Configuration Tool Connector
o2 – RJ45 RS-232/485/422 Serial ports for pass-through operations
1.2.1.5 SLC Interface
•Operation via simple ladder logic
•Complete set up and monitoring of module through RSLogix 500 software
and user constructed configuration file (DFNT.CFG)
•SLC backplane interface via M1 file
•All data related to the module is contained in user-defined files and a user
configuration file
1.2.2 Hardware Specifications
The MVI46-DFNT module is designed by ProSoft Technology and incorporates
licensed technology from Allen-Bradley (PLC backplane technology).
•Current Loads: 800 ma @ 5V (from backplane)
•Operating Temperature: 0 to 60 Deg C (32 to 140 Deg F)
•Storage Temperature: -40 to 85 Deg C (-40 to 185 Def F)
•Relative Humidity: 5-95% (w/o condensation)
•Ethernet Connector: One RJ45 Connector
•Configuration Connector: RJ45 RS-232 Connector (RJ45 to DB9 cable
shipped with unit)
•Pass-Through ports (2): RJ45 RS-232/485/422 Connector (RJ45 to DB9
cable shipped with unit)

MVI46-DFNT ♦SLC Platform Introduction
EtherNet/IP Interface Module
Page 8 of 118 ProSoft Technology, Inc.
November 9, 2004

Functional Overview MVI46-DFNT ♦SLC Platform
EtherNet/IP Interface Module
ProSoft Technology, Inc. Page 9 of 118
November 9, 2004
2 Functional Overview
This section gives the reader a functional overview of the MVI46-DFNT module.
A thorough understanding of the information contained in this document is required
for successful implementation of the module in a user application. If you already
understand the content of this section, refer to the Module Configuration section to
get the module up and running. If you are not familiar with the data transfer method
used by the module, read this section before setting up the module.
2.1 General Concepts
The following discussion covers several concepts that are key to understanding the
operation of the MVI46-DFNT module.
2.1.1 Module Power Up
On power up the module begins performing the following logical functions:
1. Initialize hardware components
a. Initialize SLC backplane driver
b. Test and clear all RAM
c. Initialize the serial communication ports
2. Read configuration for module from DFNT.CFG file on Compact Flash Disk
3. Initialize Module Register space
4. Enable Server Drivers
5. Enable Client Driver
6. Initialize all serial communication ports
Once the module receives the configuration, the module begins communicating with
other nodes on the network, depending on the configuration.
2.1.2 Main Logic Loop
Upon completing the power up configuration process, the module enters an infinite
loop that performs the functions shown in the following diagram.

MVI46-DFNT ♦SLC Platform Functional Overview
EtherNet/IP Interface Module
Page 10 of 118 ProSoft Technology, Inc.
November 9, 2004
2.1.3 Backplane Data Transfer
The MVI46-DFNT module is unique in the way that the SLC backplane is used. 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 diagram displays the data transfer method used to move data between
the SLC processor, the MVI46-DFNT module, and the TCP/IP Network.

Functional Overview MVI46-DFNT ♦SLC Platform
EtherNet/IP Interface Module
ProSoft Technology, Inc. Page 11 of 118
November 9, 2004
TCP/IP
Stack
And
Ethernet
Interface
Client
Driver
Logic
Client
Driver
Logic
Module’s
Internal
Database
MVI46-DFNT Module
To
EtherNet/IP
Network
Ladder
Logic
Transfers
Data from
module’s M1
File to data
areas in the
processor
User Data Files
SLC Processor
Ladder
Logic
Transfers
Data from
Processor
data areas
to M1 File
M1 File
Backplane Driver
Status
Read Data
Write Data
Special Control
Blocks
Server
Driver
Logic
Server
Driver
Logic
Command Control
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 diagram shows
the layout of the database:
4000 registers for user data
M1 File
Module’s Internal Database Structure
0
3999
4999
1000 registers for command
control
Data registers in the module above 3999 are used for command control. When
special values are written in this register set, the module performs specific functions.
The following sections define the special functions handled by the module.
2.2 Module Control Blocks
As discussed in the previous section, range 4000 to 4999 in the M1 file is used to
control the module in order to perform specific tasks. These tasks are described in
the following sections. 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 sections.

MVI46-DFNT ♦SLC Platform Functional Overview
EtherNet/IP Interface Module
Page 12 of 118 ProSoft Technology, Inc.
November 9, 2004
2.2.1 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
Appendix A of this document contains a complete listing of the data returned for the
two status blocks.
2.2.2 Output Data Initialization Request
When the module performs a restart operation, it requests output data from the
processor to initialize the module’s output data. This mode of operation 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
2.2.3 Command Error List Request
This command control request (control code of 2000) is used to request a set of data
from the command list error data set. The error codes returned in the block are
DFNT error codes noted in Appendix A. 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.

Functional Overview MVI46-DFNT ♦SLC Platform
EtherNet/IP Interface Module
ProSoft Technology, Inc. Page 13 of 118
November 9, 2004
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.
2.2.4 Command Control
Blocks 3000 to 3002 are used to alter the command type field for a set of commands
in the client command lists. Block 3000 is used to disable commands by setting the
enable type field to value of 0. Block 3001 is used to enable 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
is used to set 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.
2.2.5 Warm Boot
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 forces the module to read the new configuration
information and to restart. The structure of the control block is shown in the following
table:

MVI46-DFNT ♦SLC Platform Functional Overview
EtherNet/IP Interface Module
Page 14 of 118 ProSoft Technology, Inc.
November 9, 2004
Offset Description / Value Length
4000 9998 1
2.2.6 Cold Boot
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 structure of the control block is shown in the following table:
Offset Description / Value Length
4000 9999 1
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 are used to accept TCP/IP connections on service
port AF12. The client establishes connections to service port AF12 (hexadecimal) on
other EtherNet/IP servers.
The following sections discuss the operation of the server and client drivers.
2.3.1 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.
0
4999
Database
Addresses
Server
Driver
Register
Data
storage M1 File
Processor Memory DFNT ModuleBackplane Interface
Configuration
Status
4
2
3
5
1
3999
Step Description
1 The server driver receives the configuration information from the configuration file on the Compact
Flash Disk, and the module initializes the servers.

Functional Overview MVI46-DFNT ♦SLC Platform
EtherNet/IP Interface Module
ProSoft Technology, Inc. Page 15 of 118
November 9, 2004
Step Description
2 A Host device, such as a ControlLogix processor, RSLinx or an MMI package issues a read or write
command to the module. The server driver qualifies the message before accepting it into the module.
3 Once the module accepts the command, the data is immediately transferred to or from 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.
4 Once the data processing has been completed in Step 3, the response is issued to the originating
master node.
5 Status data for the servers is passed to the processor under ladder logic control using the command
control data area in the M1 file.
The DFNT module supports server functionality using the reserved ControlNet
service port 0xAF12. Services supported in the module permit client applications
(i.e., RSView, ControlLogix processors, and RSLinx) to read from and write to the
module’s database. This section discusses the requirements for attaching to the
module using several client applications.
The following diagram displays the relationship of the DFNT module’s functionality to
devices on an Ethernet network:
ClientServer
RSSql
RSLinx ControlLogix
Processor
PLC5
Processor
SLC5/05
Processor
DDE/OP C
Apps
RSView
SoftLogix
DFNT MODULE
DB
Server functionality is used to place 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 user configuration file. Ladder logic in attached
processors use MSG instructions to perform read and write operations on the
module’s internal database. When RSLinx is used to link 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

MVI46-DFNT ♦SLC Platform Functional Overview
EtherNet/IP Interface Module
Page 16 of 118 ProSoft Technology, Inc.
November 9, 2004
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 is dependent 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:
MSG INSTRUCTION TYPE
DATABASE PLC2 PLC5 OR CONTROLLOGIX
ADDRESS SLC PCCC CIP Integer
0 0 N10:0 N10:0 Int_data[0]
999 999 N10:999 N10:999 Int_data[999]
1000 1000 N11:0 N11:0 Int_data[1000]
1999 1999 N11:999 N11:999 Int_data[1999]
2000 2000 N12:0 N12:0 Int_data[2000]
2999 2999 N12:999 N12:999 Int_data[2999]
3000 3000 N13:0 N13:0 Int_data[3000]
4000 4000 N14:0 N14:0 Int_data[4000]
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
N13:12. The module simulates N-files in the internal database. The following table
lists the relationship between the N-files and the module’s internal database
registers:
Internal Simulated
Database N-File
Register
0 N10:0
1 N10:1
---
999 N10:999
1000 N11:0
1001 N11:1
---
1999 N11:999
2000 N12:0
2001 N12:1
---
2999 N12:999
3000 N13:0
3001 N13:1
---
3999 N13:999

Functional Overview MVI46-DFNT ♦SLC Platform
EtherNet/IP Interface Module
ProSoft Technology, Inc. Page 17 of 118
November 9, 2004
Note: The way the data files are used will depend on the DFNT Server File Size
value (100 or 1000). The previous example shows an example where this parameter
is set with a value of 1000.The following table lists the PCCC functions supported by
the module:
Basic Command Set Functions
Command Function Definition
0x00 N/A Protected Write
0x01 N/A Unprotected Read
0x02 N/A Protected Bit Write
0x05 N/A Unprotected Bit Write
0x08 N/A Unprotected Write
PLC-5 Command Set Functions
Command Function Definition
0x0F 0x00 Word Range Write (Binary Address)
0x0F 0x01 Word Range Read (Binary Address)
0x0F 0x00 Word Range Write (ASCII Address)
0x0F 0x01 Word Range Read (ASCII Address)
SLC-500 Command Set Functions
Command Function Definition
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
Additionally, the module supports CIP data table read and write functions. These
functions use controller tags to access data in the module’s database. This is the
preferred data access method as it directly specifies the data type used with the
command. The following table lists the data access methods:

MVI46-DFNT ♦SLC Platform Functional Overview
EtherNet/IP Interface Module
Page 18 of 118 ProSoft Technology, Inc.
November 9, 2004
SERVER DATABASE ACCESS
DATABASE PLC2 PLC5 OR
ADDRESS SLC PCCC CIP CIP CIP CIP CIP CIP
Boolean Bit Arra
y
Byte Integer Double Int Real
0 0 N10:0 N10:0 BoolData[0] BitAData[0] SintData[0] Int_Data[0] DIntData[0] RealData[0]
999 999 N10:999 N10:999 BoolData[15984] SintData[1998] Int_Data[999]
1000 1000 N11:0 N11:0 BoolData[16000] BitAData[500] SintData[2000] Int_Data[1000] DIntData[500] RealData[500]
1999 1999 N11:999 N11:999 BoolData[31984] SintData[3998] Int_Data[1999]
2000 2000 N12:0 N12:0 BoolData[32000] BitAData[1000] SintData[4000] Int_Data[2000] DIntData[1000] RealData[1000]
2999 2999 N12:999 N12:999 BoolData[47984] SintData[5998] Int_Data[2999]
3000 3000 N13:0 N13:0 BoolData[48000] BitAData[1500] SintData[6000] Int_Data[3000] DIntData[1500] RealData[1500]
3998 3998 N13:998 N13:998 BoolData[63968] BitAData[1999] SintData[7996] Int_Data[3998] DIntData[1999] RealData[1999]
3999 3999 N13:998 N13:999 BoolData[63984] SintData[7998] Int_Data[3999]
MSG INSTRUCTION TYPE
CONTROLLOGIX
If the CIP data table read and write functions are utilized, the controller tag array
names defined in the module must be used. The following table lists the controller
tag names recognized by the module and the associated data types:
Tag Array Data Type Data Size
BoolData[] Bit 1-bit
BitAData[] Bit Array 32-bits
SintData[] Byte 8-bits
Int_Data[] Word 16-bits
DIntData[] Double Word 32-bits
RealData[] Floating-point 32-bits
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)

Functional Overview MVI46-DFNT ♦SLC Platform
EtherNet/IP Interface Module
ProSoft Technology, Inc. Page 19 of 118
November 9, 2004
SLC-500 Command Set Functions
Command Function Definition Supported
in Slave
0x0F 0xA1 Protected Typed Logical Read With Two Address Fields X
0x0F 0XA2
Protected Typed Logical Read With Three Address
Fields
X
0x0F 0XA9 Protected Typed Logical Write With Two Address Fields X
0x0F 0XAA
Protected Typed Logical Write With Three Address
Fields
X
0x0F 0XAB
Protected Typed Logical Write With Mask (Three
Address Fields)
2.3.2 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.
Client
Driver
DFNT Module
Configuration Client
Command List
Status
3
1
2
4
5
0
3999
Database
Addresses
Register
Data
storage
M1 File
Processor Memory Backplane Interface
Command
Control
Command
Control
4
4999

MVI46-DFNT ♦SLC Platform Functional Overview
EtherNet/IP Interface Module
Page 20 of 118 ProSoft Technology, Inc.
November 9, 2004
Step Description
1 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).
2 Once configured, the client driver begins transmitting read and/or write commands to the
other nodes on the network. If writing data to another node, the data for the write command
is obtained from the module's internal database to build the command.
3 Presuming successful processing by the node specified in the command, a response
message is received into the client driver for processing.
4 Data received from the node on the network is passed into the module's internal database,
assuming a read command.
5 Status data is returned to the SLC processor for the client and a Command List error 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.
2.3.2.1 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 ControlLogix procssor
•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/10th seconds)
Refer to Section 5.3 for more information on the Command List.