0% found this document useful (0 votes)
124 views2 pages

Mvi56E-Mnetc: Should I Be Selling The MVI56E-MNET or The MVI56E-MNETC

The document discusses differences and capabilities between the MVI56E-MNET and MVI56E-MNETC modules. The MVI56E-MNETC module now supports up to 10,000 registers in the database array compared to the previous maximum of 5,000 registers. It also now supports Modbus TCP/IP server functionality in addition to client functionality. A revision 3 firmware can be used with older ladder logic but new features require the latest add-on instruction.

Uploaded by

Andres Manrique
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
124 views2 pages

Mvi56E-Mnetc: Should I Be Selling The MVI56E-MNET or The MVI56E-MNETC

The document discusses differences and capabilities between the MVI56E-MNET and MVI56E-MNETC modules. The MVI56E-MNETC module now supports up to 10,000 registers in the database array compared to the previous maximum of 5,000 registers. It also now supports Modbus TCP/IP server functionality in addition to client functionality. A revision 3 firmware can be used with older ladder logic but new features require the latest add-on instruction.

Uploaded by

Andres Manrique
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

MVI56E-MNETC

Should I be selling the MVI56E-MNET or the MVI56E-MNETC

Sell the MVI56E-MNETC. It solves all the applications the MVI56E-MNET does plus
more.
You now have the best of both modules, the MVI56E-MNET and MVI56E-MNETC
modules, combined into one unit.

What has been added to the MVI56E-MNETC module with the


revision 3 firmware?

The MVI56E-MNETC module has been upgraded, providing support for up to a maximum
of 10,000 registers (16-bit INT) to be exchanged between the ControlLogix processor and
the module. The previous revision 2 firmware only supported 5000 registers. This
expanded database array will allow you to use the module in larger applications, requiring
the exchange of more data with the various devices on the Modbus network.

Additionally, the module has also been upgraded to support Modbus TCP/IP server level
support (previously only offered on the MVI56E-MNET module). This now allows the
MVI56E-MNETC module to support Modbus TCP/IP client level support of up to 30 client
connections (with 480 Modbus TCP/IP master commands) and provide support of up to 20
Modbus TCP/IP servers.

There’s no more having to figure out if the module requires Modbus TCP/IP client
capability (MVI56E-MNETC) or Modbus TCP/IP server and client capability (MVI56E-
MNET) as the MVI56E-MNETC rev3 firmware will now support both.

Is the MVI56E-MNETC rev3 module backwards compatible with my


old ladder logic?
Yes, a revision 3 firmware module can operate with revision 2 ladder logic without any
issues. So replacing a revision 2 module with a new revision 3 unit will work just fine
without any ladder changes.
NOTE: To take advantage of new features you must use revision 3 Add-On Instruction
Do I have to use the new Add-On Instruction to take advantage of the
increased register space?
Yes, while you can use the revision 3 module with older revision 2 Add-On Instructions, in
order to take advantage of up to 10,000 registers per module, you must use the latest
released Add-On Instruction.

Can I upgrade my revision 2 module with the revision 3 firmware?


Yes, contact our technical support group and they can walk you through the upgrade
process.

Will the MVI56E-MNET, MVI56E-MNETR, and MVI56E-MNETCR also


be enhanced to support 10,000 registers?

Not at this time. Since the MVI56E-MNETR and MVI56E-MNETCR modules are
designed for applications where the module will sit in a remote I/O rack over ControlNet,
the limited backplane data transfer is better for the limited bandwidth on the ControlNet
network.

You might also like