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.
The addition of the WEB hardware option provides the following additional features:
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. EtherNet/IP (Explicit Messaging) Compatible Devices Rockwell Automation equipment that supports EPIC:
The MNET-DFNT modules are the ideal solution for the many applications where Modbus TCP/IP connectivity can be used to integrate EtherNet/IP devices into a system. The Modbus TCP/IP gateway is a powerful module designed with both Client and Server support, 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.
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.
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.
This area is used to store error codes, counters, and port status information for each port.
This area contains module configuration information such as port configuration, network information, and command configuration. This configuration file is downloaded to, or uploaded from, this area.
Specification | Description |
Power Supply |
24 VDC nominal |
Current Load | 500 mA max @ 32 VDC max |
Operating Temperature | -4° F to 122° F (-20° C to 50° C) |
Storage Temperature | -40° F to 185° F (-40° C to 85° C) |
Relative Humidity | 5% to 95% (with no condensation ) |
Dimensions |
Standard: |
LED Indicators |
Power and Module Status |
Configuration Serial Port |
DB-9M RS-232 only |
Ethernet Port (Ethernet modules only) |
10Base-T half duplex RJ45 Connector |
Application Ports |
Modbus Plus Connector |
Serial Port Isolation |
2500 V RMS port signal isolation per UL 1577 |
Shipped with Each Unit |
Mini-DIN to DB-9M serial cables |
MNET DFNT Datasheet | 312,02 kB | Dernière Modification 23/04/2014 |
MNET Protocol Manual | 631,11 kB | Dernière Modification 16/02/2012 |
DFNT Protocol Manual | 2,03 MB | Dernière Modification 24/07/2013 |
PLX EDS File | 333,95 kB | Dernière Modification 10/05/2010 |
ProSoft Configuration Builder (PCB) Version 4.4.17.0.0280 | 56,50 MB | Dernière Modification 26/02/2018 |
The EtherNet/IP 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.
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.
General Protocol Information |
|
Messaging |
PCCC on CIP |
Miscellaneous |
125 word read and write data lengths |
EtherNet/IP Server Specifications
In Server mode, the module accepts commands from one or more clients to read/write data stored in the module's internal registers.
EtherNet/IP Server Specifications |
|
Connections | Five 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 |
CIP Services Supported |
0x4C - CIP Data Table Read |
EtherNet/IP Client Specifications
In Client mode, the module controls the read/write data transfer between the gateway and other EtherNet/IP devices. Data transfer can be initiated and executed without any ladder programming being required in the Rockwell Automation hardware.
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). |
List of Rockwell Automation material that support EPIC:
The Modbus TCP/IP protocol driver can interface many different protocols into Schneider Electric Quantum processors as well other solutions supporting the protocol. The MNET driver supports Client and Server connections, and when coupled with the Web option provides a web/ftp interface as well.
The Modbus TCP/IP driver interfaces with a common internal database in the module. This permits the sharing of data between the Modbus TCP/IP and other networks and devices.
Modbus TCP/IP Server |
|
General | Server supports up to 5 independent connections each to Modbus TCP/IP clients on Service Port 502 using the standard MBAP protocol, and Service Port 2000. |
Configurable Parameters |
Module IP Address |
Modbus TCP/IP Client |
|
General | Actively reads and writes data with Modbus TCP/IP compatible devices. One client connection (up to 100 servers/devices with 100 commands) |
Configurable parameters | Number of active commands, Min Command Delay, Response Timeout, Retry Count, Command Error Pointer |
Command List | Up to 100 fully configurable commands on the Client port |
Declaration of Conformity (RoHS/CE) | 299,92 kB | Dernière Modification 04/03/2018 |