Modbus TCP/IP to DNP over Ethernet Communication Module
5201-MNET-DNPSNET
Product Description
The ProLinx family Modbus TCP/IP to DNP over Ethernet communications module (5201-MNET-DNPSNET) creates a powerful connection between devices on Modbus TCP/IP and DNP over Ethernet networks. The module is a stand-alone DIN-rail mounted protocol gateway that provides one Ethernet port.
The ProLinx module is capable of supporting the DNP 3.0 protocol as a server using the TCP and UDP protocols using service port 20000. This port is fully configurable, providing a great deal of flexibility.
The Modbus TCP/IP (MNET) 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 MNET driver supports Client connections as well as Server connections.
Product Applications
The MNET-DNPSNET modules are the ideal solution for joining Modbus TCP/IP and DNP over Ethernet networks.
This Ethernet to Ethernet gateway is a powerful module designed with both Client and Server support for Modbus/TCP and Server support for DNP over Ethernet, enabling easy connections between the dissimilar network types. The module utilizes a shared database so that the two protocols can quickly and easily transfer data between themselves. Applications for the module are found in most industries, especially the 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.
DNPSNET Protocol Specifications
The DNPSNET protocol driver exists as a single service port (DNPSNET port 20000) implementation that supports a single TCP port connection and multiple UDP ports on a TCP/IP Ethernet network. The DNPSNET port operates as a server, supporting the DNP 3.0 protocol in a Level 2 implementation using the DNP User Group recommended extension for use on LAN/WAN. This is published in "Transporting DNP V3.00 over Local and Wide Area Networks", December 15, 1998 by the DNP Users Group and is available on the Internet at http://www.dnp.org.
The DNPSNET driver will respond to requests from a remote DNP client (master) device. All data in the module's database configured as DNP data points is available to the remote master device for read and write requests. Additionally, the driver can send unsolicited event messages to a connected, TCP, client.
|
General Parameters
|
|
Type
|
Specifications
|
|
Internal Database
|
Binary Inputs: 8000 points (500 words)
Analog Inputs:500 points of analog input data
Counters:250 (500 words)
Binary Outputs: 2000 points (125 words)
Analog Outputs: 500 points of analog output
|
|
DNP Mode
|
DNP 3.0 Slave - Level 2
|
|
DNP Object Support
|
Reference Appendix for full Object Definition document
|
|
DNP Server
|
|
Type
|
Specifications
|
|
ServicePort
|
20000
|
|
Protocols
|
TCP (1 connection) and UDP
|
|
Node address
|
0 to 65534 - software selectable
|
|
Status Data
|
Error codes, counters and port status
|
The DNPSNET module accepts DNP commands to control and monitor the data stored in the DNP databases. These data are passed between the module and the other protocol on the ProLinx module.
Modbus TCP/IP Protocol Specifications
The Ethernet driver interfaces with a common internal database in the module. This permits the sharing of data across many different protocols and networks.
Modbus TCP/IP Port Specifications
Server
The MNET module supports server functionality using the reserved Modbus TCP/IP service port 502, as well as service port 2000 to support the TCP/IP encapsulated Modbus protocol that is supported by several HMI manufacturers. Services supported in the module permit client applications (i.e., HMI software packages, Quantum processors, etc.) to read from and write to the module's database.
Data in the module's internal database is accessible for read and write operations by any node on the network supporting the MBAP (service port 502) or MNET (service ports 2000/2001) TCP/IP protocols.
There is no configuration of the MNET module required to implement Server functionality other than setting up the network and database parameters in the user configuration file.
|
Modbus TCP/IP Server
|
|
Type
|
Specification
|
|
General
|
The server driver supports connections to Modbus TCP/IP clients supporting Service Port 502 using the standard MBAP protocol, and clients supporting Modbus on Service Port 2000.
- Supports up to five (5) independent server connections for Service Port 502
- Supports up to five (5) independent server connections for Service Port 2000
|
|
Configurable Parameters
|
Module IP Address
Modbus address offsetting
|
|
Modbus Commands supported
|
1 : Read Output Status
2 : Read Input Status
3 : Read Multiple Data Registers
4 : Read Input Registers
5 : Write Single Bit
6 : Write Single Data Register
15 : Write Multiple Bits
16 : Write Multiple Data Register
|
Client
The module supports a client connection on the TCP/IP network to interface with processors (and other server based devices) using a user constructed command list of up to 100 entries.
|
Modbus TCP/IP Client
|
|
Type
|
Specification
|
|
General
|
The client driver supports the active reading and writing of data with Modbus TCP/IP compatible devices.
- One client connection available (connect up to 100 servers/devices with 100 commands)
|
|
Configurable parameters
|
Number of active commands (Up to 100 for client)
Min Command Delay
Response Timeout
Retry Count
Command Error Pointer
|
|
Modbus Commands supported
|
1 : Read Output Status
2 : Read Input Status
3 : Read Multiple Data Registers
4 : Read Input Registers
5 : Write Single Bit
6 : Write Single Data Register
15 : Write Multiple Bits
16 : Write Multiple Data Register
|
|
Command List
|
Up to 100 commands on the Client port, each fully configurable for function, Server IP address, Service Port, register to/from addressing and word/bit count
|
|
Status Data
|
Error codes available on an individual command basis.
|
|
Polling of command list
|
User configurable polling of commands, including disabled, continuous and on change of data (write only)
|
Hardware Specifications
| Power Supply |
24 VDC nominal |
| |
18-32 VDC allowed |
| |
Positive, Negative, GND Terminals |
| |
2.5 mm screwdriver blade |
Current Load
|
500 mA max@ 32 VDC max |
| Operating Temperature |
-20 to 50°C |
| |
-4 to 122°F |
|
Storage Temperature |
-40 to 85°C |
| |
-40 to 185°F |
| Relative Humidity |
5% to 95% (non-condensing) |
| Dimensions |
Standard
5.20H x 2.07W x 4.52D inches
13.2cmH x 5.25cmW x 11.48cmD
Extended
5.20H x 2.73W x 4.52D inches
13.2cmH x 6.934cmW x 11.48cmD |
|
LED Indicators |
Power and Module Status |
| |
Application Status |
| |
Serial Port Activity LED |
| |
Serial Activity and Error LED Status |
| Configuration Serial Port |
DB-9M RS-232 only |
| |
No hardware handshaking |
Ethernet Port
(Ethernet protocol gateways only) |
10Base-T half duplex RJ45 Connector |
| |
Link and Activity LED indicators |
| |
Electrical Isolation 1500 V rms at 50 Hz to 60 Hz for 60 s, applied as specified in section 5.3.2 of IEC 60950: 1991 |
| |
Ethernet Broadcast Storm Resiliency = less than or equal to 5000 [ARP] frames-per-second and less than or equal to 5 minutes duration |
|
Application Serial Ports (Serial protocol gateways only) |
RS-232/422/485 |
| |
RS232 handshaking configurable |
| |
RS-422/485 DB-9 to Screw Terminal Adaptor |
| |
Note: The number of serial application ports depends on the module type, and the combination of protocols. |
|
Serial Port Isolation |
2500V RMS port signal isolation per UL 1577 |
| |
3000V DC min. isolation port to ground and port to logic |
|
Shipped with each unit |
Mini-DIN to DB-9M serial cables |
| |
4 ft RS-232 configuration cable |
| |
2.5mm screwdriver |
| |
CD (docs and Configuration utility) |
| |
RS-422/485 DB-9 to Screw Terminal Adaptor for each serial application port (serial protocols only) |
Click here for dimensions diagram Certifications
The ProLinx gateway module has the following certifications:
CE
ATEX Cat 3 Zone 2
cULus Haz Loc Class I, Div 2
Ordering Information
|
5201-MNET-DNPSNET
|
Modbus TCP/IP to DNP over Ethernet
|
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:
|
