memphiskt007
Member
Hello all,
Been in the industry for about 20 years and have finally found a problem I cannot solve. Looking for some modbus help.
I have a Momentum PLC with an M1 adapter, part number 171CCC96030, programmed with Concept 2.6. This setup communicates via Modbus TCP/IP to a custom 3rd party device specific to this customer. It has communicated for years, no issues.
Its time to replace this device with a Modicon M340, also communicating via MB TCP/IP, programmed in Unity. Upon replacing the old PLC with the M340. I can no longer communicate with the 3rd party device via read/write vars or IO scanner. Performing a Wireshark from the 3rd party device I can see the Modbus traffic getting to the machine. I removed all devices from the customer's network so there are no managed switches between, just to make sure.
I have exchanged the 3rd party device with other identical devices on site, just to verify it still works. It works flawlessly with other momentum PlCs. I have taken my M340 to other modbus tcp/ip devices and it works fine. So the code is good. Using other M340s with the 3rd party device yields the same results.
My suspicion is something within the 3rd party device does not like the M340. The company supporting this 3rd party device has long since been out of business, so no help there. Is there anything within unity, or native to the hardware that I am missing? Any thoughts?
If there is something I have missed or not stated, feel free to ask.
Been in the industry for about 20 years and have finally found a problem I cannot solve. Looking for some modbus help.
I have a Momentum PLC with an M1 adapter, part number 171CCC96030, programmed with Concept 2.6. This setup communicates via Modbus TCP/IP to a custom 3rd party device specific to this customer. It has communicated for years, no issues.
Its time to replace this device with a Modicon M340, also communicating via MB TCP/IP, programmed in Unity. Upon replacing the old PLC with the M340. I can no longer communicate with the 3rd party device via read/write vars or IO scanner. Performing a Wireshark from the 3rd party device I can see the Modbus traffic getting to the machine. I removed all devices from the customer's network so there are no managed switches between, just to make sure.
I have exchanged the 3rd party device with other identical devices on site, just to verify it still works. It works flawlessly with other momentum PlCs. I have taken my M340 to other modbus tcp/ip devices and it works fine. So the code is good. Using other M340s with the 3rd party device yields the same results.
My suspicion is something within the 3rd party device does not like the M340. The company supporting this 3rd party device has long since been out of business, so no help there. Is there anything within unity, or native to the hardware that I am missing? Any thoughts?
If there is something I have missed or not stated, feel free to ask.