ProSoft Technology MVI56E-MNET/MNETXT - Manual (Page 108)

Reference MVI56E-MNET / MNETXT ♦ ControlLogix Platform
User Manual Modbus TCP/IP Interface Module
Page 108 of 181 ProSoft Technology, Inc.
April 23, 2014
5.1.1 General Specifications
 Backward compatible with previous MVI56-MNET versions
 Single-slot 1756 ControlLogix backplane compatible
 10/100 Mbps auto crossover detection Ethernet configuration and application
port
 User-definable module data memory mapping of up to 5000 16-bit registers
 CIPconnect-enabled network configuration and diagnostics monitoring using
ControlLogix 1756-ENxT and 1756-CNB modules and EtherNet/IP pass-
through communication
 ProSoft Configuration Builder (PCB) software supported, a Windows-based
graphical user interface providing simple product and network configuration
 Sample ladder logic and Add-On Instructions (AOI) are used for data transfer
between module and processor
 4-character, alpha-numeric, scrolling LED display of status and diagnostics
data in plain English – no cryptic error or alarm codes to decipher
 ProSoft Discovery Service (PDS) software used to locate the module on the
network and assign temporary IP address
 Personality Module - a non-volatile, industrial-grade Compact Flash (CF) card
used to store network and module configuration, allowing quick in-the-field
product replacement by transferring the CF card
5.1.2 Modbus TCP/IP Specifications
 ProSoft Technology’s Modbus TCP/IP implementation (MNET) includes both
Client (Master) and server (slave) capabilities
 Modbus data types overlap in the module's memory database, so the same
data can be conveniently read or written as bit-level or register-level data.
 Configurable floating-point data movement is possible, including support for
Enron or Daniel
®
floating-point formats
Modbus TCP/IP Server (Slave)
 Supports ten independent server connections for Service Port 502 (MBAP)
 Supports ten independent server connections for Service Port 2000
(Encapsulated)
 Accepts Modbus Function Codes 1, 2, 3, 4, 5, 6,7, 8, 15, 16, 17, 22 and 23
 Module data can be derived from other Modbus server devices on the
network through the Client or from the ControlLogix processor