Unconnected Messaging Limits - Rockwell Automation Allen-Bradley ControlNet 1734-ACNR User Manual

Product
1788-CNx
1794-ACN15, 1794-ACNR15
and 1797-ANCR
Connected Messaging Limits
Each module supports 32 connections, of which 22 connections can be scheduled connections. With
these controllers, the number of end-node connections they effectively support is dependent on the
application's NUT and RPI:
If the NUT and The controllers support a maximum of this
the RPI are each many connections
5 ms
10 ms
20 ms
40 ms +
In the table above, with a NUT and RPI of 40 ms and greater, the ControlNet card supports 22
communications connections. In this case, the remaining 10 connections can be used for unscheduled
connections.
Each module supports a maximum 32 end-node connections for messages. With these cards, the number
of end-node connections they support is dependent on the application's NUT:
At this NUT The cards support this many
end-node connections
2.0 - 2.99ms
3.0 - 3.99ms
4.0 - 7.99ms
8.0 - 100.0

Unconnected Messaging Limits

The following limits of unconnected messages are the maximum number of
outstanding unconnected messages. These are unconnected messages that
have been sent to the module and are being processed and have not yet
generated a response or time-out.
Table A.3 Unconnected Messaging Limits
Product
1756-CN2 or 1756-CN2R
1756-CNB or 1756-CNBR
1769-L32C or 1769-L35CR
1784-PCC
1784-PCIC or 1784-PCICS
1784-PKTCS
1788-CNx
1794-ACN15, 1794-ACNR15 or
1797-ACNR15
3
6
13
22
3
12
20
32
Unconnected Messaging Limits
Supports up to 20 unconnected messages
Supports up to 20 unconnected messages
Supports up to 6 unconnected messages
Supports up to 50 unconnected messages
Supports up to 50 unconnected messages
Supports up to 50 unconnected messages
Supports up to 20 unconnected messages.
Supports up to 16 unconnected messages.
Publication CNET-UM001C-EN-P - November 2005
Connection Use Over ControlNet A-3