kBrz
Member
Hi folks, I'm new to this forum, learning my way around. Please bear with me.
At my company, a contractor is wrapping up a project where multiple PLC's are getting condensed into a single CPU (with redundancy), upgraded from PLC5 on Data Highway +, to ControlLogix on Ethernet IP.
They gave us multiple laptops each with an activation for Studio 5000 Logix designer.
Most of the time, we are able to have more than one laptop connected concurrently, for monitoring, making online edits, etc.
But sometimes the network doesn't allow it. This problem is characterized by seeing a link in RSLinx to each of the dozen's of nodes on the network (remote i/o racks, barcode scanners, etc.) but getting a red X on the node containing the CPU. We can't go online, nor can we ping the IP address. Unplugging the other PLC's will allow the one that was blocked access.
Has anyone seen this happen before? All the managed network switches are locked down by our IT department, but they are not seeing anything in the configuration that would cause this issue.
Any suggestions would be greatly appreciated.
At my company, a contractor is wrapping up a project where multiple PLC's are getting condensed into a single CPU (with redundancy), upgraded from PLC5 on Data Highway +, to ControlLogix on Ethernet IP.
They gave us multiple laptops each with an activation for Studio 5000 Logix designer.
Most of the time, we are able to have more than one laptop connected concurrently, for monitoring, making online edits, etc.
But sometimes the network doesn't allow it. This problem is characterized by seeing a link in RSLinx to each of the dozen's of nodes on the network (remote i/o racks, barcode scanners, etc.) but getting a red X on the node containing the CPU. We can't go online, nor can we ping the IP address. Unplugging the other PLC's will allow the one that was blocked access.
Has anyone seen this happen before? All the managed network switches are locked down by our IT department, but they are not seeing anything in the configuration that would cause this issue.
Any suggestions would be greatly appreciated.