Mvi56E-Mnetc: Should I Be Selling The MVI56E-MNET or The MVI56E-MNETC
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.
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.
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.