Russ
Lifetime Supporting Member
I have a client who periodically experiences network communication issues. Sometimes when I VPN into the site, their SCADA systems will flash comm loss alarms, and they won't get updates on their screens from the two plant compressors. However, when they were starting up the plant (and these 700hp compressors were off, or running at low speed) I had no trouble connecting and doing a lot of programming through VPN.
The main plant plc is a 1769-32E. When I did some basic diagnostics I noticed the processor was sending 13 messages, and had a peak of 17. A few other processors also execute a couple of MSG arguments.
In speaking with Rockwell, they suspect that one/both of the ethernet cables by the compressors could be getting noise from the motors' current loads, which could be affecting comms.
Is there a way to verify this?
Would there be any benefit to using Produce & Consume tags in place of the MSG arguments? The MSG argumetns are set up for each of the main pieces of equipment. A lot of them could be replaced fairly easily with P&C. But I'm not sure how much this would benefit the client.
The main plant plc is a 1769-32E. When I did some basic diagnostics I noticed the processor was sending 13 messages, and had a peak of 17. A few other processors also execute a couple of MSG arguments.
In speaking with Rockwell, they suspect that one/both of the ethernet cables by the compressors could be getting noise from the motors' current loads, which could be affecting comms.
Is there a way to verify this?
Would there be any benefit to using Produce & Consume tags in place of the MSG arguments? The MSG argumetns are set up for each of the main pieces of equipment. A lot of them could be replaced fairly easily with P&C. But I'm not sure how much this would benefit the client.