Erik S

I have never done the IO scanning with a TSX processor, but I have done it with a Quantum processor, and it worked in both Concept and Unity software to a ProSoft module. A couple of things to remember: 1) You can only have 5 I/O scan lists, matching the 5 server socket connections that are available on the ProSoft converter. (some ProSoft devices have more, but I think 5 is the minimum they support). 2) Make sure that the format for the Ethernet port is set for "ETHERNET" instead of "IEEE". In Concept, I had to change this, as this cause frames that were not TCP/IP frames to be sent out to the ProSoft module. The ProSoft module only supports Modbus TCP/IP. 3) I don't think I/O scanner will allow you to do more than this, but limit the count to 120 words of data or less. I think 125 is the max, but it would be good to be just a little under the max count and not right at it. Hope this helps.

Doug, The MVI56E-MNET module should be able to communicate with any device that supports Modbus TCP/IP protocol. A couple of things to check. 1) In the configuration for the Modbus commands section, what Device Address are you using. With the MNET module, a FC 3 with a Device Address of 0 will issue a poll for Modbus address 40,001 in the slave device. So you will want to make sure that the FC and Device Address fields are configured accordingly. 2) If you are using a FC (function code) of 3, have you tried a 4? Sometimes you are using the wrong function code for the application. 3) If you monitor the Command Error code, are you getting any errors for those commands? 4) Lastly, if you have the ability to obtain a Wireshark capture of the communications between the Square D software and the device, ProSoft will be able to take a look at this and see how the software is polling for data. They may be using Encapsulated Modbus (also supported by the MVI56E-MNET module) instead of the standard Modbus TCP/IP (MBAP). ProSoft has a training video on this product on their website. It is a step-by-step tutorial on the product. It sounds like you have progressed beyond this, but it might give you some ideas of what could have been missed. http://www.prosoft-technology.com/training/mvi56emnet.php And lastly, if you have any questions I'm sure ProSoft support could give you a couple more ideas. But if you have the ability to get a Wireshark capture, this would certainly allow them to make suggestions based on the software that is working currently.