User manual

Publication CNET-UM001C-EN-P - November 2005
A-2 Connection Use Over ControlNet
The Logix5000 controller supports 250 connections. But the limit of
connections ultimately resides in the communication module you use for the
connection. If a message path routes through a communication module or
card, the connection related to the message also counts towards the
connection limit of the communication module or card.
Connected Messaging Limits
Table A.2 Connected Messaging Limits
Product Connected Messaging Limits
1756-CN2 or 1756-CN2R Supports 100 connections.
• 5 controllers can have a rack-optimized connection to the module
• 5 controllers can have a rack-optimized, listen-only connection to the module
1756-CNB or 1756-CNBR Supports 64 connections.
• 5 controllers can have a rack-optimized connection to the module
• 5 controllers can have a rack-optimized, listen-only connection to the module
1769-L32C or 1769-L35CR Built-in ControlNet port only supports 32 communication connections. With these controllers, the number
of end-node connections they effectively support is dependent on the application’s NUT and RPI of the
connection:
1784-PCC Each module supports 31 unscheduled connections.
1784-PCIC Each module supports 128 unscheduled connections.
1784-PCICS Each module supports 128 unscheduled and 127 scheduled connections.
1784-PKTCS Each module supports 128 unscheduled connections and 127 scanlist entries for scheduled connections.
If the NUT is And the RPI is The controller’s built-in ControlNet port effectively
supports this many communication connections
(1)
(1)
For each NUT/RPI combination, the number of connections supported is listed in a range. The lower number is the number
of connections we recommend you make to maintain reasonable ControlNet port CPU utilization rates. The higher number
is the maximum number of connections possible for that NUT/RPI combination.
2 ms 2 ms 0 - 1
3 ms 3 ms 1 - 2
5 ms 5 ms 3 - 4
10 ms 10 ms 6 - 9
14 ms 14 ms 10 - 12
5 ms 20 ms 12 - 16
4 ms 64 ms 31