Modbus TCP/IP Multi-Client to EtherNet/IP Gateway
5201-MNETC-DFNT
Product Description
The ProLinx Modbus TCP/IP Multi-Client to EtherNet/IP Gateway creates a powerful connection between Modbus TCP/IP and EtherNet/IP networks. The module provides one Ethernet port.
The ProLinx Modbus TCP/IP (MNETC) Multi Client driver can be used to interface many different protocols into the Schneider Electric Quantum family of processors as well other software solutions supporting the protocol.
- 5 MNET Modbus TCP/IP servers (port 2000)
- 5 MBAP Modbus TCP/IP servers (port 502)
- 10 Modbus TCP/IP clients (MNET or MBAP), each supporting up to 16 Modbus TCP/IP commands.
The addition of the WEB hardware option provides the following additional features:
- 2 HTTP servers
- 1 mail client
- 1 FTP server
The Ethernet driver interfaces with a common internal database in the module. This permits the sharing of data across many different protocols and networks.
The Ethernet/IP (DFNT) protocol driver supports the Explicit Messaging implementation of the protocol. User-configurable as both a Client and a Server, the EtherNet/IP port is a very powerful data transfer tool.
Product Applications
The MNETC-DFNT modules are the ideal solution for the many applications where Modbus TCP/IP Client connectivity can be used to integrate EtherNet/IP devices into a system. The Modbus TCP/IP gateway is a powerful module designed with up to five Clients, enabling easy connection to other Modbus TCP/IP devices (Modicon processors and many others). In combination with the EtherNet/IP device support, the module provides a very powerful interface to the many EtherNet/IP devices which are in use in the industrial marketplace today. Applications for the module are found in most industries, especially Manufacturing, Oil and Gas, Electrical Power and Food Processing.
Functional Specifications
Internal Database
The ProLinx module contains an internal database that consists of areas for application data, status information, and configuration information.
The internal database is shared between all ports on the module and is used as a conduit to pass information from a device on one network to one or more devices on another network.
Application Data Area
The data area is used to store and retrieve data by the protocol drivers and for data exchange between protocols. The database is used as a source for write commands to remote devices and holds data collected from the remote devices. Commands defined in the configuration file (stored in the configuration data area) control how the data is to be handled in the database.
Status Data Area
This area is used to store error codes, counters, and port status information for each port.
Configuration File
This file contains module configuration information such as port configuration, network information, and command configuration. This configuration file is downloaded to, or uploaded from, the module.
Modbus TCP/IP Client
The Modbus TCP/IP Client driver interfaces with a common internal database in the module. This permits the sharing of data between the Modbus TCP/IP Client and other networks and devices.
|
Modbus TCP/IP Client
|
|
General
|
Actively reads and writes data with Modbus TCP/IP compatible devices.
- 5 MNET Modbus TCP/IP servers (port 2000)
- 5 MBAP Modbus TCP/IP servers (port 502)
- 10 Modbus TCP/IP clients (MNET or MBAP), each supporting up to 16 Modbus TCP/IP commands.
The addition of the WEB hardware option provides the following additional features:
- 2 HTTP servers
- 1 mail client
- 1 FTP server
|
|
Configurable parameters
|
Number of active commands, Min Command Delay, Response Timeout, Retry Count, Command Error Pointer
|
|
Command List
|
Up to 16 fully configurable commands on each Client
|
EtherNet/IP Protocol Specifications
The EtherNet/IP protocol is one of the primary connectivity tools to the different Rockwell Automation platforms. The Explicit Messaging aspect of the protocol (only) has been implemented in the ProLinx units to provide the data transfer link between the ProLinx units and the Rockwell Automation hardware. (Implicit Messaging (I/O communications) is not supported)
|
General Protocol Information
|
|
Messaging
|
PCCC on CIP
Explicit Messaging supported
|
|
Compatibility
|
Compatible devices include a wide assortment of other client/server devices such as:
- PLC5/E Rev. C/N, D/E, E/D or later
- SLC5/05 Series A, OS503 frn4 or later
- ControlLogix processor via 1756-ENET
- 1785-ENET Series A, Rev. D
- Interchange (release dependent)
- RSLinx Gateway V1.7 or later
|
|
Miscellaneous
|
125 word read and write data lengths
Floating point data supported
|
EtherNet/IP Server Specifications
When in the Server mode, the module accepts commands from one or more clients to read/write data stored in the module's internal registers.
The following table lists EtherNet/IP Server specifications:
|
EtherNet/IP Server Specifications
|
|
Connections
|
Five (5) independent TCP server sockets permit remote clients to interact with all data contained in the module.
|
|
Data File
|
Data Table File Start - Fixed at N10
Data Table File Size - 100 or 1000 words
|
|
PCCC on CIP
Commands supported
(DF1 commands)
|
Basic Command Set
0x00 Protected Write
0x01 Unprotected Read
0x02 Protected Bit Write
0x05 Unprotected Bit Write
0x08 Unprotected Write
PLC-5 Command Set (0x0F)
0x00 WordRange Write (Binary Address)
0x01 WordRange Read (Binary Address)
0x00 WordRange Write (ASCII Address)
0x01 WordRange Read (ASCII Address)
SLC Command Set (0x0F)
0xA1 Prot Typed Read w/ 2 addr fields
0xA2 Prot Typed Read w/ 3 addr fields
0xA9 Prot Typed Write w/ 2 addr fields
0xAA Prot Typed Write w/ 3 addr fields
|
|
CIP Services Supported
|
0x4C CIP Data Table Read
0x4D CIP Data Table Write
|
EtherNet/IP Client Specifications
When configured in Client mode, the module controls the read/write data transfer between the gateway and other Ethernet/IP devices. When configured in this mode, data transfer can be initiated and executed without any ladder programming being required in the Rockwell Automation hardware.
The following table provides Ethernet/IP Client specifications:
|
EtherNet/IP Client Specifications
|
|
General
|
One client
|
|
Command List
|
Support for 100 commands, each configurable for command, IP address, register to/from addressing and word/bit count
|
|
Polling of command list
|
User configurable polling of commands, including disabled, continuous and on change of data (write only)
|
|
PCCC on CIP
Commands Supported
(DF1 Commands)
|
Basic Command Set
0x00 Protected Write
0x01 Unprotected Read
0x02 Protected Bit Write
0x05 Unprotected Bit Write
0x08 Unprotected Write
PLC-5 Command Set (0x0F)
0x00 WordRange Write (Binary Address)
0x01 WordRange Read (Binary Address)
0x26 Read-Modify-Write (Binary Address)
0x00 WordRange Write (ASCII Address)
0x01 WordRange Read (ASCII Address)
0x26 Read-Modify-Write (ASCII Address)
SLC Command Set (0x0F)
0xA1 Prot Typed Read w/ 2 addr fields
0xA2 Prot Typed Read w/ 3 addr fields
0xA9 Prot Typed Write w/ 2 addr fields
0xAA Prot Typed Write w/ 3 addr fields
0xAB Prot Typed Write w/ Mask 3 addr fields
|
|
Status Data
|
Error codes available on an individual command basis.
|
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
- RSLinx Gateway V1.7+
- ControlLogix 1756-ENET/ENBT/EN2T
Hardware Specifications
Click here for dimensions diagram Certifications
The ProLinx gateway module has the following certifications:
CE
ATEX Cat 3 Zone 2
cULus Haz Loc Class 1, Div 2
Ordering Information
|
5201-MNETC-DFNT
|
Modbus TCP/IP Multi Client to EtherNet/IP Gateway
|
To place an order, please contact your local ProSoft Technology, Inc. distributor. For a list of ProSoft distributors near you, click here.
Distributors:
Place your order by email to orders@prosoft-technology.com:, fax to +1 661-716-5101.
Sales and Support:
|
