ProSoft Technology MVI46 Series Modules: MVI46-MCM Master/Slave Communication Module —

Technical Dossier

Product Details And Specifications

ProSoft Technology MVI46 Series: Comprehensive Module Range and Technical Overview

The ProSoft Technology MVI46 series represents one of the most widely deployed communication module platforms in global heavy industry. Designed as plug-in modules for the Allen-Bradley SLC 500 backplane, MVI46 units are installed across petrochemical refineries, nuclear auxiliary systems, offshore platforms, pulp and paper mills, and large-scale water treatment facilities. Their role is protocol bridging — translating between the SLC 500's native DF1 or DH485 environment and external field devices, SCADA hosts, or legacy serial networks. The installed base of MVI46 modules in continuous-process industries is substantial, and many facilities operate these modules under 20+ year maintenance cycles, making long-term spare parts availability a critical operational requirement.

The Evolution of MVI46 Architecture

The MVI46 platform was introduced by ProSoft Technology in the mid-1990s as a direct response to the SLC 500's limited native communication capability. Early modules such as the MVI46-MCM and MVI46-MNET established the core architecture: a single-slot SLC 500 backplane module with an onboard processor, dual serial ports, and a shared memory block mapped into the SLC 500's M0/M1 file space. Data exchange between the module and the SLC 500 processor occurs via ladder logic read/write instructions targeting this memory block — a design that remains unchanged across the entire product generation.

Through the 2000s, ProSoft expanded the MVI46 catalog to cover an increasing number of industrial protocols: Modbus RTU/ASCII, PROFIBUS DP, DeviceNet, DNP3, IEC 60870-5-101, and proprietary vendor protocols. The hardware platform remained consistent, while firmware and port configuration differentiated models. This architectural stability is both an advantage (spare parts interchangeability at the chassis level) and a constraint (no native Ethernet; all communication is serial or via a separate Ethernet bridge module).

By the 2010s, the SLC 500 platform itself entered end-of-life status with Rockwell Automation, and ProSoft's MVI46 series followed a parallel trajectory. Most MVI46 models are now classified as discontinued or last-time-buy. ProSoft's current recommended migration path leads to the MVI56E series for ControlLogix or the MVI69E series for CompactLogix. However, the installed base of SLC 500 systems in brownfield facilities ensures continued demand for MVI46 spare parts through at least the 2030s.

MVI46 Full Catalog & Functionalities (SKU List)

The following SKUs represent verified, commonly sourced models within the MVI46 series, organized by functional category. All models occupy a single slot in the SLC 500 chassis.

Master/Slave & Multi-Protocol Communication

MVI46-MCM: Modbus RTU/ASCII master/slave, dual serial ports, configurable baud rate up to 115.2 kbps.
MVI46-MNET: Modbus TCP/IP client/server via Ethernet port; bridges SLC 500 to Ethernet Modbus networks.
MVI46-MNETC: Modbus TCP/IP client-only variant; optimized for polling remote Modbus TCP servers.
MVI46-MNETR: Modbus TCP/IP with redundancy support; dual Ethernet ports for ring topology.
MVI46-MCM-DFCM: Modbus master/slave with DF1 concurrent master capability on second port.

PROFIBUS

MVI46-PDPMV1: PROFIBUS DP-V1 master; supports acyclic data exchange and GSD file-based configuration.
MVI46-PDPS: PROFIBUS DP slave; presents SLC 500 data as a PROFIBUS DP slave device to an external master.
MVI46-PDP: PROFIBUS DP master (earlier generation, pre-V1); widely installed in legacy chemical plant I/O networks.

DeviceNet

MVI46-ADN: DeviceNet adapter (slave); connects SLC 500 to a DeviceNet master scanner.
MVI46-DNET: DeviceNet scanner (master); polls DeviceNet slave devices and maps data to SLC 500 files.

DNP3 & Utility Protocols

MVI46-DNP: DNP3 master/slave; used in SCADA-connected substations and water utility RTU applications.
MVI46-101S: IEC 60870-5-101 slave; transmits SLC 500 process data to IEC 101 SCADA masters.
MVI46-101M: IEC 60870-5-101 master; polls IEC 101 slave RTUs from the SLC 500 host.

Proprietary & Specialty Protocols

MVI46-GSC: Generic serial communication module; configurable ASCII/DF1 for custom serial device integration.
MVI46-HART: HART protocol master; reads HART secondary variables from field instruments over 4–20 mA loops.
MVI46-LNG: Lonworks FTT-10 network interface; used in building automation and legacy process control integration.
MVI46-DFNT: DF1 to Ethernet/IP bridge; extends SLC 500 DF1 messaging over Ethernet infrastructure.

Sourcing Hard-to-Find & Obsolete MVI46 Parts

The majority of MVI46 series models have been discontinued by ProSoft Technology. Standard distribution channels no longer carry active stock, and lead times through authorized channels — when available — can exceed 26 weeks. DriveKNMS maintains a dedicated inventory program for end-of-life ProSoft MVI46 modules, sourced through certified secondary market channels and tested prior to shipment.

For facilities operating SLC 500 systems under long-term maintenance agreements, DriveKNMS provides: verified surplus stock of high-demand models including MVI46-MCM, MVI46-PDPMV1, and MVI46-DNP; firmware version matching to ensure compatibility with existing ladder logic and configuration files; and documentation support including legacy ProSoft configuration software (PCB) and sample ladder logic files where available. Emergency same-day quotation is available for critical plant shutdowns.

Quality Control for the MVI46 Range

MVI46 modules present specific test challenges due to their dual-port serial architecture and shared memory interface with the SLC 500 backplane. DriveKNMS applies a structured test protocol to all MVI46 units prior to shipment:

Each module is seated in a live SLC 500 chassis and powered through a full boot cycle. The M0/M1 file interface is verified using a reference ladder logic program that confirms read/write integrity across the full mapped data block. Both serial ports are tested at all supported baud rates (1200 through 115,200 bps) using loopback and live-device simulation. For Modbus variants, master and slave modes are independently verified using a Modbus simulator. For PROFIBUS variants, GSD file loading and cyclic data exchange are confirmed against a reference DP master. Modules exhibiting backplane communication errors, port initialization failures, or configuration file rejection are quarantined and not shipped.