jtashaffer said:
...I ran in to a similar problem on a controllogix plc...They said to upgrade the Ethernet module or replace it. I am still waiting for it to come in to see if it solves the problem.
yang1216 said:
...Maybe I have to add a ENB module not use the CPU's ethernet port.
GTUnit said:
That would increase your available # of connections and fix the issue
Careful,
jtashaffer is referring to an issue with a 1756 ControlLogix platform and 1756 Ethernet Bridge Module, and not a 1769 CompactLogix platform.
This is a 1769-L32E CompactLogix we are dealing with. There is no "ENB" Ethernet bridge module available for the 1769 chassis. There is a 176
8-ENBT Ethernet module, or a 176
8-EWEB Ethernet module, but they can only be used in a 1768 chassis, which is only present on the left side of a 1768-L4x CompactLogix controller.
So you only have the "CPU's ethernet port" on the 1769-L32E to use in this application.
The 1769-L32E has a limit of 32 CIP connections. Without the HMI connected, you counted 25 connections. The HMI can add up to 5 CIP connections (4 read, 1 write), so this brings it up to a possible 30 connections just while running normal. When you add your PC to the network and attempt to browse/Go Online, you are adding another connection.
This would appear as though you are 1 connection shy of the limit, but the 25 you are seeing, plus the potential 5 from the HMI when connected, may not be a fixed total when you are not online counting. The total can be dynamic, depending on what is configured to communicate with this L32E. If some of the other controllers are passing varying amounts of data to and from this controller, then that connection limit could quite easily be reached, or exceeded.
This 1769-L32E CompactLogix controller is as good as maxed out for the current application setup.
What can you do about it?
Well, you could upgrade the controller to a newer 5370 CompactLogix controller. These support up to 256 connections. A 1769-L33ER, for instance, would allow up to 32 nodes to be added to the I/O Configuration. A node is any device that can be added to the project I/O tree. A node will have its own connection limit, but the limit for all 32 nodes would be 256 connections to the controller. They can pass 6000 packets/sec for I/O and up to 400 messages/sec for HMI/Messaging.
A newer CompactLogix would physically replace an older equivalent fairly easily. Converting an older CompactLogix project to a newer version is also relatively simple. Messaging paths would need reconfiguring, but not much else.
Apart from spending money, one other thing you can try is to force the PanelView application to limit the number of connections it uses at any given time. This can free up a couple of badly needed spare connections.
Since FactoryTalk View Studio ME v5.10, the runtime application will automatically limit the number of connections, to certain limited devices connected to the terminal, to just 1. While the 1769-L2x controllers were added (32 connections max.), the 1769-L3x controllers were not. So you have to implement the following "fix" either through the provided file, or manually, by editing the Windows Registry...
39366 - CIP connections with RSLinx Enterprise (Reducing PanelView Plus connections)
Access Level: TechConnect
Regards,
George