Sale!

ProSoft MVI56-MCM ControlLogix Modbus RTU/ASCII Master-Slave Module

  • Model: MVI56-MCM
  • Brand: ProSoft Technology
  • Series: MVI56 ControlLogix In-Chassis Modules
  • Core Function: Connects ControlLogix processors to Modbus RTU/ASCII devices
  • Product Type: Modbus master/slave serial communication module
  • Key Specs: 2 isolated serial ports; Modbus RTU/ASCII; 5,000-word database; 250-word input image
  • Condition: New Original / New Surplus
  • ⚠️ Obsolete Model – Limited Stock Available
Categories: , , , , SKU: MVI56-MCM Brand:

Description

Key Technical Specifications

Parameter Value
Model MVI56-MCM
Manufacturer ProSoft Technology
Compatible platform Rockwell Automation ControlLogix 1756 chassis, local or remote
Function Modbus RTU/ASCII master/slave interface between ControlLogix processor and serial devices
Chassis slots required 1
Serial application ports 2 independent ports, PRT1 and PRT2
Serial electrical interfaces RS-232, RS-422, or RS-485, jumper selectable
Serial connectors RJ45 with supplied RJ45-to-DB-9 male adapter cables
Serial protocols Modbus RTU Master/Slave and Modbus ASCII Master/Slave
Baud rate 110 baud to 115,200 baud
Data bits 7 or 8
Stop bits 1 or 2
Parity None, even, or odd
RTS on/off delay 0 to 65,535 ms
Error checking Modbus RTU: CRC-16; Modbus ASCII: LRC
Modbus slave address 1 to 247
Master commands Up to 100 commands per master port
Shared database 5,000 user-assignable 16-bit registers
Backplane data transfer Input image: 250 words; output image: 248 words
Port isolation 500 V optical isolation from backplane
Configuration/debug port CFG, RS-232 only
Configuration method Ladder logic and controller tags in RSLogix 5000 / Studio 5000
Backplane current load 800 mA at 5 V DC; 3 mA at 24 V DC
Operating temperature 0 to +60°C
Storage temperature −40 to +85°C
Relative humidity 5% to 95%, non-condensing
Shock rating 30 g operational; 50 g non-operational
Vibration rating 5 g from 10 to 150 Hz

The MVI56-MCM is the general-purpose Modbus serial master/slave module for ControlLogix. It is preferred for a local chassis with the controller or for a remote chassis accessed over Ethernet; the MVI56-MCMR is the reduced-I/O variant intended for ControlNet remote chassis applications.

 

Product Introduction

The ProSoft MVI56-MCM is a single-slot Modbus master/slave communication module for Rockwell Automation ControlLogix 1756 chassis. It connects a ControlLogix processor to Modbus RTU or ASCII instruments, drives, meters, PLCs, and PACs over two isolated serial ports.

Each port can be independently configured as a Modbus master or slave, allowing simultaneous polling of field devices and response to external SCADA or HMI masters. The module maintains a 5,000-word shared database and exchanges a 250-word input image and 248-word output image with the processor over the backplane.

MVI56-MCM

MVI56-MCM

MVI56-MCM

MVI56-MCM

Troubleshooting Quick Reference

Symptom Possible Cause Relevance to this Part Quick Check Method Recommendation
Module not recognized in RSLogix/Studio 5000 Missing EDS file, wrong slot, or chassis configuration issue ✅ High Verify slot number, import the ProSoft EDS file, and confirm the module appears in the I/O tree Correct chassis configuration before replacing the MVI56-MCM
No Modbus communication on PRT1 or PRT2 Wrong RS-232/422/485 jumper, wiring fault, or baud/parity mismatch ✅ High Check port jumper positions, DB-9 adapter pinout, baud rate, parity, data bits, and stop bits Match port jumpers and serial settings to the field device
One port works, other does not Port-specific jumper, wiring, or ladder/configuration issue ✅ High Swap known-good serial devices between PRT1 and PRT2; compare controller-tag configuration Isolate the fault to port hardware, wiring, or configuration
Master polls but device does not respond Wrong slave address, function code, register address, or cable fault ✅ High Use a Modbus analyzer or serial sniffer; verify slave ID, function code, and starting address Correct master command configuration before replacing hardware
Slave device cannot access data Incorrect slave ID, register mapping, or write protection ✅ High Confirm slave ID, register offsets, and read/write permissions in controller tags Correct slave mapping and access settings
Data does not update in processor tags Ladder copy logic, module scheduling, or backplane image configuration issue ✅ High Verify scheduled connection, input/output image sizes, and ladder MOV/COP instructions Correct ladder data transfer and module scheduling
Module OK LED off or ERR LED on Backplane power issue, module fault, or invalid configuration ✅ High Measure chassis power budget; reseat the module; review LED status and controller diagnostics Restore power or replace the faulty module
Communication drops intermittently RS-485 termination, shield/ground issue, or excessive polling load ✅ Medium Inspect RS-485 termination and shield grounding; review polling interval and command list Correct bus termination and optimize polling configuration

❗ Do not assume the MVI56-MCM has failed because a Modbus device stops responding. Wrong slave ID, incorrect register offset, reversed RS-485 wiring, or a bad DB-9 adapter causes most serial communication faults.

If the fault remains after checking the EDS/chassis configuration, port jumpers, serial wiring, Modbus register mapping, and ladder data transfer, contact technical support with photos of the module, jumper settings, RSLogix I/O tree, and controller-tag configuration.

 

Frequently Asked Questions

Can the MVI56-MCM act as both Modbus master and slave?
Yes. Each of the two serial ports can be independently configured as a Modbus master or slave, and both ports share the module’s 5,000-word user database.

Does it support Modbus TCP/IP?
No. The MVI56-MCM supports Modbus RTU and ASCII over its two serial ports. It does not provide Modbus TCP/IP data exchange; use the MVI56-MNET or MVI56E-MNET for Ethernet-based Modbus TCP/IP integration.

Why choose the MVI56-MCM instead of the MVI56-MCMR?
Choose the MVI56-MCM for a local ControlLogix chassis or a remote chassis connected over Ethernet. It uses larger 250-word input and 248-word output images. The MVI56-MCMR uses smaller 42-word I/O images and is intended for ControlNet remote chassis applications.

How many Modbus slave devices can it poll?
Each master port supports up to 100 configured commands. The practical number of slave devices depends on the command list, polling interval, register count, and serial network response time.

Can I use RS-485 two-wire devices on both ports?
Yes. Each application port supports RS-232, RS-422, or RS-485 through jumper selection. For RS-485, verify polarity, biasing, termination, and cable shield grounding; do not connect both ports to the same multidrop network unless the application specifically requires it.

Can I hot-swap the MVI56-MCM?
No. Although it is a 1756 chassis module, removing it while active can interrupt Modbus communications and processor I/O connections. Follow a controlled removal procedure, then verify the module status and scheduled connection after reinstallation.

Why is New Surplus less expensive than factory-new stock?
New Surplus means genuine ProSoft inventory manufactured earlier but not installed or commissioned. We inspect, document, and functionally verify each unit before shipment. It is not used, repaired, or refurbished stock unless clearly stated on the product page.