Allen-Bradley 1756-L55 controller to communicate with MVI56-MCM

What firmware is your controller using?...

Hi and Welcome to the Forum!

The older 1756-L55 processor is supported up as far as firmware revision 16. So it is also supported up as far as RSLogix 5000 v16.

Even though your 1756-L55 might be using an older firmware revision, the reason I am mentioning it is supported up to v16 is because that is when the Add-On Instruction (AOI) feature was introduced.

This is relevant because at v16 an Add-On Instruction (AOI) was introduced by Prosoft specifically for the MVI56(E)-MCM module to greatly assist in handling the module's raw I/O data, processing it and passing it to the controller. The encapsulated logic for the AOI is quite involved and can save a user hours of figuring out and writing logic, or their own AOI.

The AOI will also expose the MCM configuration parameters via tags, which is very useful.

In RSLogix v16, we can select a module profile (which was created for v15 and up) for the MVI56E-MCM (before that we had to create a 1756 Generic module). This module profile will add the module-defined data types for the input and output data for the module (both large INT arrays).

The Add-On Instruction will then, once you have it configured for your module I/O tags, interact with the module I/O data and do as I mentioned above.

So the current firmware revision of the controller will be important in deciding what level of support for all or any of the above will be available?

If you are at firmware revision 16, then please see the following Prosoft webpage for relevant downloads...

Modbus Master/Slave Enhanced Network Interface Module for ControlLogix
MVI56E-MCM/MCMXT


Regards,
George
 
Oh, good man! I have that User Manual open here since earlier but I forgot to directly link to it in my first post, although it is also available via the links we've provided.

The older MVI56-MCM (not Enhanced) model is supported in the v16 AOI (Add-On Instruction) and v15 AOP (Add-On Profile) downloadable via the links we have provided, even though it is listed and referred to as "MVI56(E)-MCM" in most places we look (E = Enhanced model).

And yes, as I mentioned, if you are using older than version 15, and do not want to or cannot upgrade the processor firmware, then you will have to add it as a 1756-MODULE (Generic Module), as per the manual, and will also not have the AOI available to use.

If not at revision/version 16, I would highly recommend getting there, if you can.

I've also just checked and the downloadable AOI is v2.8 from either source location.

The EDS from your linked source is v1.0 of the EDS file and is specific to the non-Enhanced model MVI56-MCM.
The EDS from my linked source is v3.1 of the EDS file and is specific to the Enhanced model MVI56E-MCM.
Other than File/Device descriptions though, the contents of the EDS file are identical for Classification and Modular definitions.
But I would recommend using the older EDS for the MVI56-MCM (KuulKuum's link), if interested in it.

Regards,
George
 
Last edited:

Similar Topics

Hi, I have a ControlLogix system with 1756-IF16 analogue inputs. I can't scale the inputs at the card as there is a requirement to facilitate...
Replies
2
Views
41
Hi all, installed on chassis A17 an A/I from Allen-Bradley , problem is what ever I do , all channels are sticked on value 39.9 and cannot change...
Replies
1
Views
132
I am using Allen Bradley PLC 1756-L81E and EIP module 1756-EN2TR for Ethernet/IP communication. My communication works fine but in Get-Attribute...
Replies
2
Views
197
Dear All: I have the flashing red light on the FDBK indicator. The manual said that it means: The axis servo loop error tolerance has been...
Replies
2
Views
631
Hi Guys, Here I have Started to work on some difficult task I hope I will get some solution here. I wanted to communicate ABB CI 840 IO Master...
Replies
2
Views
890
Back
Top Bottom