Key Technical Specifications
- Product Model: PROSOFT MVI56E-MNET
- Manufacturer: ProSoft Technology
- Platform: Rockwell Automation ControlLogix (1756 Backplane)
- Protocol: Modbus TCP/IP
- Client Capacity: Up to 30 simultaneous client connections
- Server Capacity: Up to 20 server connections
- Data Memory: 10,000 words (16-bit integers) for custom mapping
- Network Port: Single 10/100 Mbps Ethernet (Auto-MDI/MDI-X)
- Configuration Tool: ProSoft Configuration Builder (PCB)
- Backplane Power: 5 VDC @ 800 mA, 24 VDC @ 3 mA
- Operating Temp: 0°C to 60°C (32°F to 140°F)
- Diagnostic Interface: Built-in Web Server and CIP Connect
Product Introduction
PROSOFT MVI56E-MNET is a single-slot communication module designed for the ControlLogix platform, functioning as a dedicated Modbus TCP/IP gateway. It handles network traffic independently, mapping data directly to the PLC backplane without taxing the primary controller’s CPU.This module supports true parallel processing for up to 30 client connections and 20 server connections, eliminating the serial polling delays typical of native PLC AOI configurations. With 10,000 words of dedicated memory, it manages high-density data exchange for third-party instruments, SCADA systems, and DCS networks. (A quick warning: always check the revision suffix on the label before ordering, as older revisions may require specific PCB software versions).
Installation & Configuration Guide
Preparation (10 min)
Verify the ControlLogix chassis has an available slot and the power supply has adequate 5VDC headroom (this module draws 800 mA). Download the latest ProSoft Configuration Builder (PCB) software and the matching Add-On Instruction (AOI) file for your Studio 5000 firmware version.Removal (5–10 min)
If replacing a legacy MVI56-MNETC, power down the rack. Remove the Ethernet cable and loosen the captive screws. Pull the module straight out. Self-correction: I previously assumed hot-swapping was safe here, but ProSoft explicitly warns against inserting or removing modules while backplane power is active due to arcing risks. Always de-energize.Installation (10 min)
Align the PROSOFT MVI56E-MNET with the backplane connector and slide it in firmly. Secure the captive screws to ensure proper grounding and mechanical retention. Connect a CAT5e/CAT6 Ethernet cable to the front port. Ensure the write-protect jumper on the module is in the OFF (open) position unless you specifically intend to flash new firmware.Power-On & Test (10 min)
Restore rack power. Observe the front panel LEDs; the “Module OK” indicator should illuminate solid green within 30 seconds. Connect your laptop to the module’s web server IP (found via ProSoft Discovery Service) to verify the default configuration. Open Studio 5000 and confirm the AOI instance reports no major faults.
Troubleshooting Quick Reference
| Symptom | Probable Cause | Corrective Action |
|---|---|---|
| Module Fault LED Solid Red | Firmware mismatch or corrupt config | Verify AOI version matches PCB config. Reload config via PCB. |
| No Client Connections | IP Subnet or Gateway error | Ping target device. Verify subnet mask matches PLC ENBT/EN2TR module. |
| Intermittent Data Drops | Network congestion or cabling | Check for duplex mismatches. Ensure daisy-chain length < 100m. |
| AOI Shows “No Comm” | Backplane handshake failure | Reseat module. Verify chassis keying matches AOI slot assignment. |
| Web Server Unreachable | IP Conflict or static route missing | Use ProSoft Discovery tool to assign temporary IP. Check router ACLs. |
Dimensions, Mounting & Wiring Notes
- Form Factor: Single-slot ControlLogix (1756 chassis)
- Mounting: Standard backplane wedge connector with front-panel captive screws
- Network Wiring: Standard RJ45; supports Auto-MDI/MDI-X (straight-through or crossover cables accepted)
- Clearance: Requires minimum 1 inch (25.4 mm) front clearance for airflow and cable bend radius
FAQ
Can I use this module in a remote chassis?
Yes, but only if the remote chassis is connected via an ENBT or EN2TR module that supports CIP Connect. You will need to configure the routing path in the PCB software and the PLC tag structure.I’m getting a “Version Mismatch” error in Studio 5000. What gives?
The PROSOFT MVI56E-MNET requires AOI revision 16 or higher for newer firmware. If your PLC is running v15 or lower, you must use the legacy ladder logic example files instead of the AOI. Check the exact firmware rev on the module label.Is this module still being manufactured?
No, the MVI56E-MNET is considered a legacy product. ProSoft now manufactures the MVI56E-MNETC. While the MVI56E-MNET remains fully functional and supported via firmware updates, new system designs should specify the MNETC variant.How much memory does it actually have?
It features 10,000 words of 16-bit integer memory dedicated to Modbus data mapping. This is isolated from the PLC’s memory, meaning you don’t lose controller capacity when scaling up third-party device integrations.Do I need a special license for the configuration software?
No. ProSoft Configuration Builder (PCB) is free to download and use. However, updating the module’s firmware may require contacting ProSoft support for an authorization code.Can it handle both client and server roles simultaneously?
Absolutely. It can act as a client to poll 30 field devices while simultaneously serving data to 20 SCADA/DCS systems. The internal processor handles this in parallel, not sequentially.What happens if one Modbus server stops responding?
The module isolates the fault automatically. It will timeout on the unresponsive server and continue polling the remaining 29 clients without delay. You’ll see a specific error counter increment in the web diagnostic page.
