All MVI56E products are backward-compatible with earlier MVI56 modules allowing direct replacement without the need to change existing controller programs
10,000 Word Database
Allows you to gather more data from your devices, which improves operational performance
Enjoy Enhanced features and flexibility without incurring expensive reprogramming costs
Module configuration stored within the RSLogix™ 5000 project (ACD file)
No additional programming or configuration software is required
Add-On Instruction for RSLogix 5000 version 16 or higher cuts development time and costs
Facilitates remote user access across the ControlLogix backplane through Rockwell Automation’s 1756-ENBT module
Configure, diagnose, and analyze process data and communications status
Bridge through multiple ENBT/CNBT links to connect to MVI56E-MCMs installed in remote chassis for configuration and diagnostics
Simplifies adding the module in an RSLogix 5000 project
Backward-compatible with previous MVI56-MCM version
Single Slot - 1756 ControlLogix® backplane compatible
10/100 MB Ethernet port for network configuration and diagnostics with Auto Cable Crossover Detection
User-definable module data memory mapping of up to 10,000 16-bit registers
4-character, scrolling, alphanumeric LED display of status and diagnostic data in plain English
ProSoft Discovery Service (PDS) software finds the module on the network and assigns a temporary IP address to facilitate module access
Supports RIUP (Remove and Insert Under Power)
The MVI56E-MCM will operate on a Local or Remote rack (For remote rack applications with smaller data packet size please refer to the MVI56E-MCMR product)
Supports Enron version of Modbus protocol for floating-point data transactions
PCB includes powerful Modbus network analyzer
Special functions (command control, event commands, status, and so on) aresupported by message transfer (unscheduled) using the MSG instruction
Error codes, network error counters, and port status data available in user data memory
The MVI56E-MCM module accepts Modbus function code commands of 1, 2, 3, 4, 5, 6, 8, 15, 16, 17, 22, and 23 from an attached Modbus Master unit. A port configured as a Modbus Slave permits a remote Master to interact with all data contained in the module.This data can be derived from other Modbus Slave devices on the network, through a Master port, or from the ControlLogix processor.
A port configured as a virtual Modbus Master device on the MVI56E-MCM moduleactively issues Modbus commands to other nodes on the Modbus network. Up to 325 commands are supported on each port. Additionally, the Master ports have an optimized polling characteristic that polls Slaves with communication problems less frequently.The ControlLogix processor ladder logic can issues commands directly from ladder logic or actively select commands from the command list to execute under ladder logic control.
Modbus General Specifications
Modbus Master Specifications
Command List: Up to 325 commands per Master port, each fully configurable for function code, slave address, register to/from addressing and word/bit count.
Optimized Polling: Configuration options allow Master ports and commands to be optimized to poll slaves with communication problems less frequently.
Command Status/Error Monitoring: Command Status or Error codes are generated for each command as it executes, allowing careful monitoring o fcommunication health between the Master and its Slaves.
Slave Polling Control: Master Port maintains a Slave Status list of all network Slaves. Polling of each Slave may be disabled and enabled using this list.
Modbus Slave Specifications
Full Memory Access: A port configured as a Modbus Slave permits a remote Master to read from or write to any of the 5000 registers that make up the user memory database.
Multi-source Slave data: Data presented at the Slave port can be derived from other Modbus Slave devices on a different network through the module's Master port or from the processor tag database.
Node address: 1 to 247 (software selectable)
Status Data: Slave port error codes, counters and statuses are available separately for each port when configured as a Slave