Rockwell Automation 1768-EWEB EtherNet/IP Web Server Module User Manual - Manual (Page 122)

Publication ENET-UM527E-EN-P - October 2006
122 Use the Web Server Module To Connect Over Ethernet
CIP communications take priority over HTTP communications.
Generally, in the presence of heavy CIP traffic, HTTP traffic may
appear sluggish.
There are different types of CIP connections.
You cannot bridge I/O or produced/consumed tags through the web
server module.
CIP Connected Messaging Limits
CIP Unconnected Messaging Limits
The following limits of unconnected messages are the maximum
number of outstanding unconnected messages. These are
unconnected messages that are sent to the or bridged through the
web server module.
See the EtherNet/IP Performance and Application Guide, publication
number ENET-AP001, for more information on connections.
CIP Connection Type Description
Bridged connection A bridged connection is a connection that passes through the web server module. The end
point of the connection is a module other than the web server module.
Example: a connection from a controller through a 1756-ENBT to another controller.
End-node connection An end-node connection is a connection whose end point is the web server module itself.
Example: a connection from RSLinx to the web server module to set the IP address.
Product CIP Connected Messaging Limits
1756-EWEB, 1768-EWEB Each module supports
• 128 connections for any combination of data views, bridged messages, and ASP function
calls.
• 32 connections, which can be end-node connections.
Product CIP Unconnected Messaging Limits
1756-EWEB, 1768-EWEB Each module supports 256 CIP unconnected messages, of which:
• 128 can be unconnected messages from the Ethernet port to an object on the module or
to the backplane.
• 128 can be unconnected messages from the backplane to an object on the module or to
the Ethernet port.