Concurrent C-more Connection Limits

Topic: CM524

One of the major benefits of Ethernet connectivity is the ability to have more than 1 network master (Client) communicating to a PLC or device. A common question that arises when using C-more (since it is a network master on most of theProtocolsthat it supports) is how many C-mores can be concurrently connected to 1 device?

The answer to this question is: it depends…

There are many factors that affect the answer of how many C-mores that can be concurrently connected to an Ethernet device. If the Protocol being used is over TCP, most devices will have a TCP connection limit. The resources of the Ethernet device are a factor. The PLC scan time (assuming the device is a PLC) will be a major factor. And the rate at which C-more sends requests (“Poll Time” field inC-more Programming Software Panel Manager) can be a tremendous factor.

As you can tell from the information above, the number of concurrent C-mores that can be successfully connected to a device is very application specific. But to give a general idea of what can be achieved; several tests were run with C-more to its supported PLC on Ethernet and the results are posted in the table below. The PLC were running almost no logic in the tests performed in the table below so the scan times were much faster than what would be normal in most applications. Unless otherwise noted, the C-more projects were configured for a 0 poll rate which means that it will send requests as fast as it can (when not busy doing other things).

 

Note: The results noted below may not be typical for your application. The chart below should be used as a guideline and not a specification for your system. It is also important to note that even when successfully achieving the number of concurrent connections shown in the table below, the update and performance of your project running on the C-more panel may not be acceptable for your application. Additional optimizations in your C-more project and/or PLC project may be needed.

Protocol PLC Used in Test # C-more Panels Connected Notes
AutomationDirect ECOM Ethernet (DL05/06/205/405) DL260 & H2-ECOM100 32 Use an increased Poll rate of 100ms
AutomationDirect Productivity3000 (P3-550) P3-550 32
Allen-Bradley EtherNet/IP Client (MicroLogic 1100) (1100) 1763-L16BWA 16
Allen-Bradley EtherNet/IP Client (MicroLogic 1100) (1400) 1766-L32BXBA 16
Allen-Bradley EtherNet/IP Client (SLC5/05/ENI Adapter) (SLC 5/05) 1747-L551-L551 FRN10 28
Allen-Bradley EtherNet/IP Client (SLC5/05/ENI Adapter) (SLC 5/05) 1747-L552 FRN8 20
Allen-Bradley EtherNet/IP Client (SLC5/05/ENI Adapter) (ENI) 1761-NET-ENI 4
Allen-Bradley EtherNet/IP Client (Control/CompactLogix) *(Control) 1756-L61A 32 Use an increased Poll rate of 100ms
Allen-Bradley EtherNet/IP Client (Control/CompactLogix) (Compact) 1769-L35E 32

 

Entivity Modbus TCP/IP Ethernet (H2-WinPLC) H2-WPLC2 20 Use an increased Poll rate of 100ms
Siemens S7-200 (Ethernet:ISO over TCP/IP) CPU226 & CP243-1 8
Siemens S7-300 (Ethernet:ISO over TCP/IP) CPU319-3 32
Mitsubishi Q/QnA Ethernet Q12HCPU & QJ71E1-100 16
Omron CS/CJ FINS Ethernet CJ1H CPU65H & ETN21 32 Station #8 reserved, do not use
* When tested using a 1756-ENBT/A, (4) C-mores connected utilized 42% of the PLC Ethernet Module "System Resource Utilization".
Device Version
DL260 Ver. 2.60
H2-ECOM100 Ver. 4.0.0.1456
P3-550 Ver. 1.0.7.20
(1100) 1763-L16BWA Ser. A Rev. C FRN 3
(1400) 1766-L32BXBA Ser. A Rev. A FRN 3
(SLC 5/05) 1747-L551-L551 FRN10 OS501 Ser. C FRN 10
(SLC 5/05) 1747-L552 FRN8 OS501 Ser. C FRN 8
(ENI) 1761-NET-ENI Ser. C FRN 3.01
(Control) 1756-L61A Rev. 17
1756-ENBT/A Rev. 3.01
1756-EN2T/A Rev. 1.003
(Compact) 1769-L35E Rev. 17
H2-WPLC2 Ver. 8.0.0.0
CPU226 Rev. 02.01
CP243-1 Rev. 0101 Hardware Rev. 1
CPU319-3 Ver. 2.4
Q12HCPU Ver. B 0911
QJ71E1-100 Ver. D 0911
CJ1H CPU65H Rev. L Soft Rev. AB
ETN2 Rev. J Soft Rev. C