ProSoft Insights / Technology focus

MVI56E-MNETC vs. MVI56E-MNET: What’s the difference?

Language

Search Insights

Categories

Tags

Subscribe

Yes, I would like to receive marketing information from ProSoft Technology, Inc., and its affiliates, subsidiary companies and brands indicated below.

I therefore provide my consent to the use of the personal information submitted here for the purpose of providing me marketing information related to ProSoft Technology, Inc. and its affiliates’ and subsidiaries’ products, services and marketing events. I understand that I may withdraw my consent at any time. Additional information regarding ProSoft’s data privacy policies, including how to withdraw this consent, is available at www.prosoft-technology.com/privacy. ProSoft Technology, Inc. is a subsidiary of Belden Inc., and their affiliates, subsidiary companies and brands include ProSoft Technology SAS, ProLinx Comunicacao Industria, LTDA; Global Blue Networks Inc., and ProSoft Technology (Asia Pacific) SDN BHD.

Recent Posts

Modernizing Your Material Handling Application on Your OpEx Budget

07 Dec, 2018 / News & Events

This year on ProSoft Insights we’ve taken a look at a variety of solutions that can hel...

How can Wireless keep up with Material Handling’s Moving Equipment?

04 Dec, 2018 / News & Events

ProSoft Technology provides solutions to help our customers increase production, reduce...

Making your factory smart

30 Nov, 2018 / News & Events

The digital evolution is everywhere, and has drastically changed our way of working and...

Conveying reliable communications in Italy

28 Nov, 2018 / Application stories

A logistics end user in Italy was upgrading its operation, adding EtherNet/IP™ to its 4...

MVI56E-MNETC vs. MVI56E-MNET: What’s the difference?

Wondering which module is best for your operation? Let’s compare the two:

Both modules are Modbus® TCP/IP solutions for ControlLogix®. A major difference between the modules is the number of Client connections.

The MNET version has only one Client connection, whereas the MNETC version supports up to 30 Client connections. So, why would multiple Client connections be better than only one Client connection?

In principle, one Client connection can communicate with an infinite number of devices - there is no limit in the number of targets (the limit would be the number of available commands). It would open the first connection with the first remote server, send the requests, get the responses, and then close this connection in order to open a new one with the next remote server, repeating this process as a loop. This loop of open/close can be very fast and it has been seen that some remote servers do not support this. In the case of remote server maintenance, since this device is no longer on the network, a huge delay will perturb communication with other devices.

With multiple Client connections, if the user links only one Client connection with only one remote server (one Client connection per device), removing one device from the network will not affect communication with other devices, and the known issue with the fast open/close loop is avoided.

For more information about our different ControlLogix Modbus TCP modules watch this video: https://www.youtube.com/watch?v=fR70cXH8eOA