MVI46-DFNT
SLC Platform
EtherNet/IP Interface Module
User Manual
November 5, 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 AllenBradley 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, 2
Bakersfield, CA 93301
(661) 716-5100
(661) 716-5101 (Fax)
www.prosoft-technology.com
Copyright © ProSoft Technology, Inc. 2000 – 2004. All Rights Reserved.
MVI46-DFNT User Manual
November 5, 2004
nd
Floor
ProSoft Technology, Inc. Page 2 of 118
November 9, 2004
Table of Contents MVI46-DFNT ♦ SLC Platform
EtherNet/IP Interface Module
Table of Contents
PLEASE READ THIS NOTICE..........................................................................................................2
1 INTRODUCTION......................................................................................................................... 5
1.1 Using this Manual........................................................................................................... 5
1.2 Product Specifications...................................................................................................5
1.2.1 General Specifications .................................................................................................. 6
1.2.2 Hardware Specifications ............................................................................................... 7
2 FUNCTIONAL 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
3 MODULE CONFIGURATION ................................................................................................... 21
3.1 Setting Up the Module.................................................................................................. 21
3.2 Module Data..................................................................................................................22
4 LADDER LOGIC.......................................................................................................................23
4.1 Main Routine (U:2)........................................................................................................23
4.2 Data Transfer (U:3).......................................................................................................23
4.3 Control Routine (U:4)...................................................................................................23
5 CONFIGURATION FILE...........................................................................................................29
5.1 Command List Overview..............................................................................................30
5.2 Commands Supported by the Module........................................................................ 30
5.3 Command Entry Formats.............................................................................................31
6 DIAGNOSTICS AND TROUBLESHOOTING........................................................................... 35
6.1 Reading Status Data From the Module ...................................................................... 35
6.1.1 Required Hardware..................................................................................................... 35
ProSoft Technology, Inc. Page 3 of 118
November 9, 2004
MVI46-DFNT ♦ SLC Platform Table of Contents
EtherNet/IP Interface Module
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
7 CABLE CONNECTIONS...........................................................................................................49
7.1 Ethernet Connection.....................................................................................................49
7.2 Pass-Through Ports......................................................................................................49
7.3 RS-232 Configuration/Debug Port...............................................................................50
8 ETHERNET 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
Page 4 of 118 ProSoft Technology, Inc.
November 9, 2004
Introduction MVI46-DFNT ♦ SLC Platform
EtherNet/IP Interface Module
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 AllenBradley 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:
ProSoft Technology, Inc. Page 5 of 118
November 9, 2004
MVI46-DFNT ♦ SLC Platform Introduction
EtherNet/IP Interface Module
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
Page 6 of 118 ProSoft Technology, Inc.
November 9, 2004
Introduction MVI46-DFNT ♦ SLC Platform
EtherNet/IP Interface Module
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:
o 1 – RJ45 connector for Ethernet interface
o 1 – RJ45 RS-232 Configuration Tool Connector
o 2 – 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
• Pass-Through ports (2): RJ45 RS-232/485/422 Connector (RJ45 to DB9
shipped with unit)
cable shipped with unit)
ProSoft Technology, Inc. Page 7 of 118
November 9, 2004
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
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.
ProSoft Technology, Inc. Page 9 of 118
November 9, 2004
MVI46-DFNT ♦ SLC Platform Functional Overview
EtherNet/IP Interface Module
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.
Page 10 of 118 ProSoft Technology, Inc.
November 9, 2004
Functional Overview MVI46-DFNT ♦ SLC Platform
EtherNet/IP Interface Module
User Data Files
Status
Read Data
Write Data
Special Control
Blocks
SLC Processor
Ladder
Logic
Transfers
Data from
module’s M1
File to data
areas in the
processor
Ladder
Logic
Transfers
Data from
Processor
data areas
to M1 File
MVI46-DFNT Mo d ul e
Module’s
Internal
Database
Server
Server
Driver
Driver
Logic
M1 File
Backplane Driver
Command Control
Logic
Client
Client
Driver
Driver
Logic
Logic
TCP/IP
Stack
And
Ethernet
Interface
To
EtherNet/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 diagram shows
the layout of the database:
Module’s Internal Database Structure
4000 registers for user data
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.
M1 File
0
3999
4999
ProSoft Technology, Inc. Page 11 of 118
November 9, 2004
MVI46-DFNT ♦ SLC Platform Functional Overview
EtherNet/IP Interface Module
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
251 DFNT Servers
Status data for the module, client
and pass-through server
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
4002
This field contains the starting command index for the first error to report.
This field has a range of 0 to 99.
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.
Page 12 of 118 ProSoft Technology, Inc.
November 9, 2004
Functional Overview MVI46-DFNT ♦ SLC Platform
EtherNet/IP Interface Module
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
4003
4004 to 4063
This field contains the starting command index reported in the response
block.
This field contains the number of command error list values in the
response block.
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
4002
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:
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..
This field contains the starting command index to apply the new enable
type code to. This field has a range of 0 to 99.
ProSoft Technology, Inc. Page 13 of 118
November 9, 2004
MVI46-DFNT ♦ SLC Platform Functional Overview
EtherNet/IP Interface Module
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.
Processor Memory DFNT ModuleBackplane Interf ace
Database
Addresses
0
Register
Data
storage
3999
4999
M1 File
Status
Configuration
2
3
Server
Driver
5
1
4
Step
1 The server driver receives the configuration information from the configuration file on the Compact
Description
Flash Disk, and the module initializes the servers.
Page 14 of 118 ProSoft Technology, Inc.
November 9, 2004
Functional Overview MVI46-DFNT ♦ SLC Platform
EtherNet/IP Interface Module
Step
2 A Host device, such as a ControlLogix processor, RSLinx or an MMI package issues a read or write
3 Once the module accepts the command, the data is immediately transferred to or from the internal
4 Once the data processing has been completed in Step 3, the response is issued to the originating
5 Status data for the servers is passed to the processor under ladder logic control using the command
Description
command to the module. The server driver qualifies the message before accepting it into the module.
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.
master node.
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:
DDE/ OP C
RSS ql
Apps
SoftLogix
RSV iew
RSLinx
ControlLogix
Process or
PLC5
Process or
ClientServer
DB
DFNT MODULE
SLC5/05
Processor
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
ProSoft Technology, Inc. Page 15 of 118
November 9, 2004
MVI46-DFNT ♦ SLC Platform Functional Overview
EtherNet/IP Interface Module
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
Page 16 of 118 ProSoft Technology, Inc.
November 9, 2004
Functional Overview MVI46-DFNT ♦ SLC Platform
EtherNet/IP Interface Module
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
0x0F 0XA2
0x0F 0XA9
0x0F 0XAA
Protected Typed Logical Read With
Two Address Fields
Protected Typed Logical Read With
Three Address Fields
Protected Typed Logical Write With
Two Address Fields
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:
ProSoft Technology, Inc. Page 17 of 118
November 9, 2004
MVI46-DFNT ♦ SLC Platform Functional Overview
y
EtherNet/IP Interface Module
SERVER DATABASE ACCESS
DATABASE PLC2 PLC5 OR
ADDRESS SLC PCCC CIP CIP CIP CIP CIP CIP
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]
Boolean Bit Arra
MSG INSTRUCTION TYPE
CONTROLLOGIX
Byte Integer Double Int Real
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
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)
Supported
in Slave
Page 18 of 118 ProSoft Technology, Inc.
November 9, 2004
Functional Overview MVI46-DFNT ♦ SLC Platform
EtherNet/IP Interface Module
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
X
Fields
0x0F 0XA9 Protected Typed Logical Write With Two Address Fields X
0x0F 0XAA
Protected Typed Logical Write With Three Address
X
Fields
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.
Processor Memory Backplane In terface
Database
Addresses
0
Register
Data
storage
3999
Command
Control
4999
M1 File
4
Status
Configuration
Command
Control
DFNT Module
5
4
Command List
Client
Client
Driver
1
3
2
ProSoft Technology, Inc. Page 19 of 118
November 9, 2004
MVI46-DFNT ♦ SLC Platform Functional Overview
EtherNet/IP Interface Module
Step Description
1
2
3
4
5
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).
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.
Presuming successful processing by the node specified in the command, a response
message is received into the client driver for processing.
Data received from the node on the network is passed into the module's internal database,
assuming a read command.
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/10
th
seconds)
Refer to Section 5.3 for more information on the Command List.
Page 20 of 118 ProSoft Technology, Inc.
November 9, 2004
Module Configuration MVI46-DFNT ♦ SLC Platform
EtherNet/IP Interface Module
3 Module Configuration
This section contains the setup procedure, data, and ladder logic for successful
application of the MVI46-DFNT module. Each step in the setup procedure is defined
in order to simplify the use of the module.
3.1 Setting Up the Module
MVI46-DFNT module setup only requires software configuration using the RSLogix
500 program and the DFNT.CFG file on the Compact Flash Disk in the module. The
easiest method to implement the module is to start with the example provided with
the module MVI46-DFNT.RSS and the default configuration file. If you are installing
this module in an existing application, you can simply copy the elements required
from the example ladder logic to your application.
Note: This module can only be added to a project using the software in offline mode.
The first step in setting up the module is to define the module to the system. Select
the I/O Configuration option from the program screen. The system displays the
following window:
Select the “Other” module from the list. This causes the system to display the
following dialog box:
ProSoft Technology, Inc. Page 21 of 118
November 9, 2004
MVI46-DFNT ♦ SLC Platform Module Configuration
EtherNet/IP Interface Module
Enter the module I/O card ID number as 12835, then click OK. Double-click the
mouse on the module just added to the rack. Fill in the dialog box as shown:
The next step in the module’s setup is to define the user-defined data areas to hold
the status and read and write database areas. Edit the DFNT.CFG file now. Use any
text editor to set the values in the file. Be certain to retain the file name DFNT.CFG.
The last step in the module setup is to add the ladder logic. If the example ladder
logic is used, adjust the ladder to fit the application. When the ladder example is not
used, copy the example ladder logic to your application and alter as necessary.
The module is now ready to be used with your application. Insert the module in the
rack (with the power turned off) and attach the serial communication and network
cables. Download the new DFNT.CFG file to the module using a terminal emulation
program. Download the new application to the controller and place the processor in
run mode. If all the configuration parameters are set correctly and the module is
attached to a network, the module’s Application LED (APP LED) should remain off
and the backplane activity LED (BP ACT) should blink very rapidly. Refer to the
Diagnostics and Troubleshooting section if you encounter errors. Attach a
terminal to the Debug/Configuration port on the module and check the status of the
module using the resident debugger in the module.
3.2 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 to be used with 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.
Page 22 of 118 ProSoft Technology, Inc.
November 9, 2004
Ladder Logic MVI46-DFNT ♦ SLC Platform
EtherNet/IP Interface Module
4 Ladder Logic
Ladder logic is required for application of the MVI46-DFNT module. Tasks that must
be handled by the ladder logic are data transfer, special block handling, and status
data request and receipt. This section discusses each aspect of the ladder logic as
required by the module. Additionally, a power-up handler should be written to handle
the initialization of the module’s data and to clear any processor fault conditions.
Note: The sample ladder logic periodically copies the status data from the MVI46DFNT to the SLC memory. If you don’t need to copy status data in this manner, you
might consider not using specific rungs in the sample ladder.
4.1 Main Routine (U:2)
The Main program file is used to call the data transfer and control subroutines. The
following example shows the main routine.
4.2 Data Transfer (U:3)
The data transfer routine is responsible for placing all the input data into the M1 file
and for retrieving all the output data from the M1 file. The rung shown in the following
diagram transfers the data between the M1 file and the user data files. The first
branch is used to transfer input data from the user file to the M1 file. The second
branch is used to transfer the output from the M1 file into the user data file.
4.3 Control Routine (U:4)
The control routine is responsible for controlling the module or handling requests
from the module using the control register (M1:1.4000).
ProSoft Technology, Inc. Page 23 of 118
November 9, 2004
MVI46-DFNT ♦ SLC Platform Ladder Logic
EtherNet/IP Interface Module
The following rung is used to request the cold boot operation for the module. Placing
the value 9999 in the control register makes this request. When the module
recognizes this value in the control register, it performs the cold boot operation. The
B9 bits are unlatched as part of the logic to keep reading status data periodically.
You don’t need this bit if you don’t intend to read status data from the module.
The next rung is used to periodically request the error/status data and command
error list data from the module. Timer T4:0 is used to trigger the requests. The
following rung is used to drive the timer:
When the timer expires, the following rung is executed:
Page 24 of 118 ProSoft Technology, Inc.
November 9, 2004
Ladder Logic MVI46-DFNT ♦ SLC Platform
EtherNet/IP Interface Module
This rung is used to request a status block 250 from the module. When the module
finishes building the response block, the following rung is executed:
This rung copies the received status data into the user file and requests a status 251
block. After the module builds the response block, the following rung executes:
This rung copies the received status data into the user file and requests command
error list data for the first 60 commands in the command list. After the module builds
the data area, the following rung executes:
ProSoft Technology, Inc. Page 25 of 118
November 9, 2004
MVI46-DFNT ♦ SLC Platform Ladder Logic
EtherNet/IP Interface Module
This rung copies the 60 error status values into a user file and resets the request
timer so it can trigger again.
The following rung shows how to disable commands that are enabled in the
command list using Block 3000. In this example, we use N40:0 to fill the block
structure where:
N40:0 = 1 (number of commands to be disabled)
N40:1 = 0 (start command index)
The same logic can be used for Block 3001 (enable continuous commands) and
3002 (enable conditional commands).
If the module is configured to receive the processor data set on startup, the following
rung is required:
Page 26 of 118 ProSoft Technology, Inc.
November 9, 2004
Ladder Logic MVI46-DFNT ♦ SLC Platform
EtherNet/IP Interface Module
This feature initializes the output data in the module with the values currently held in
the processor. This feature is employed to bring the output data to a known or last
set state. This rung should be placed in a routine that will be called on every scan of
the ladder logic to ensure that the restart condition is recognized.
Important: During startup, the register M1:1.4000 contains the value 1001 after it is
set by the ladder logic.
ProSoft Technology, Inc. Page 27 of 118
November 9, 2004
MVI46-DFNT ♦ SLC Platform Ladder Logic
EtherNet/IP Interface Module
Page 28 of 118 ProSoft Technology, Inc.
November 9, 2004
Configuration File MVI46-DFNT ♦ SLC Platform
EtherNet/IP Interface Module
5 Configuration File
In order for the module to operate, a configuration file (DFNT.CFG) is required. This
configuration file contains information to set the data transfer characteristics between
the module and the processor, to configure the module’s client and command list,
and to configure the pass-through features. Each parameter in the file must be set
carefully in order for the application to be implemented successfully. Before editing
the file, design your system using the forms located in the appendix of this
document. Appendix B contains a configuration form to be used to construct the
DFNT.CFG file. Appendix C contains an example listing of a DFNT.CFG file.
The text file is separated into six sections with topic header names enclosed in the [ ]
characters. The sections present in the file are as follows:
[Section] Description
[Module] General module configuration information
[DFNT Client 0] Configuration for the DFNT client
[DFNT Client 0 Commands] Command list for the DFNT client
DF1 Pass-Through Server Port 1]
[DF1 Pass-Through Port]
Parameters for the pass-through port of the send port on the
module
Parameters for the DF1 port emulated on the third port of the
module
After each section header, the file contains a set of parameters. Unique labels are
used under each section to specify a parameter. Each label in the file must be
entered exactly as shown in the file for the parameter to be identified by the program.
If the module is not considering a parameter, check the label for the data item. Each
parameter's value is separated from the label with the ':' character. This character is
used by the program to delimit the position in the data record where to start reading
data. All data for a parameter must be placed after the ':' character. For numeric
parameter values any text located after the value will not be used. There must be at
least one space character between the end of the parameter value and the following
text. The following example shows a valid parameter entry:
Baud Rate : 19200 #Sets port baud rate to 19200
The parameter label is "Baud Rate" and the parameter value is 19200. The
characters after the parameter value are ignored and are used for internal
documentation of the configuration file.
Any record that begins with the '#' character is considered to be a comment record.
These records can be placed anywhere in the file as long as the '#' character is
found in the first column of the line. These lines are ignored in the file and can be
used to provide documentation within the configuration file. Liberal use of comments
within the file can ease the use and interpretation of the data in the file.
The client command list and e-mail definition sections are formatted differently than
the other sections. These sections contain lists of parameters to be used. Each list
ProSoft Technology, Inc. Page 29 of 118
November 9, 2004
MVI46-DFNT ♦ SLC Platform Configuration File
EtherNet/IP Interface Module
begins with the label START and when the END label is reached. When entering the
records into the list, make certain that the first character in each line is left blank.
The [DFNT CLIENT 0 COMMANDS] section is used to define 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.
5.1 Command List Overview
In order to interface the module with EtherNet/IP Server devices, the user must
construct a command list of up to 100 user-defined commands. The commands in
the list specify the server device to be addressed, the function to be performed (read
or write), the data area in the device to interface with, and the registers in the internal
database to be associated with the device data. The command list is processed from
top (command #0) to bottom. A poll interval parameter is associated with each
command to specify a minimum delay time in tenths of a second between the
issuance of a command. If the user specifies a value of 10 for the parameter, the
command is executed no more frequently than every (1) second.
Write commands have a special feature, as they can be set to execute only if the
data in the write command changes. If the register data values in the command have
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 is executed. Use of this feature can lighten the load on the network. In
order to implement this feature; set the enable code for the command to a value of 2.
The module supports numerous commands. This permits the module to interface
with a wide variety of devices. This includes ControlLogix, PLC5, and SLC-5/05
processors.
5.2 Commands Supported by the Module
The format of each command in the list is dependent 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
DFNT Function Code Definition Command Function
1 Protected Write 0x00 N/A
2 Unprotected Read 0x01 N/A
3 Protected Bit Write 0x02 N/A
4 Unprotected Bit Write 0x05 N/A
5 Unprotected Write 0x08 N/A
Page 30 of 118 ProSoft Technology, Inc.
November 9, 2004
Loading...