Rockwell Automation Publication 2080-UM002N-EN-E - November 2022
153
Chapter 8 EtherNet/IP Network
0x0206
Connection Request Error:
Requested size too large.
The controller is attempting to set up a connection with the
module and has received an error – the request size is too
large.
Possible causes include the following:
• The module in use (that is, the physical module) is
different than the module specified in the I/O
configuration tree and is therefore causing the
connection or service to fail.
• The fault may occur even when the module passes the
electronic keying test. This may result when Disable
Keying or Compatible Keying options were used in the
module configuration instead of the Exact Match option.
• Despite passing the electronic keying test, the module
being connected to does not have the same features or
settings as the module specified in the I/O configuration
tree and does not support the connection or service being
attempted.
• Verify that the path to this module is sufficiently close to
the controller.
• Check the module in use and verify that it exactly
matches the module that is specified in the application.
For more information about electronic keying, see the
user manual for the module you are using.
0x0301
Connection Request Error:
Out of buffer memory.
The controller is attempting to set up a connection with the
module and has received an error: a module in the path is
out of memory.
Possible causes include the following:
• The controller may be attempting to connect to a tag in a
producing controller that is not marked as being
produced.
• The controller may be attempting to connect to a tag in a
producing controller. That tag may not be configured to
allow enough consumers.
• The size or number of connections through this module
must be reduced.
• One of the network modules between the module and the
controller may be out of memory. Check network
configuration of the system.
• The module may be out of memory. Check the system
configuration and capabilities of the module.
• The module in use (that is, the physical module) is
different than the module specified in the I/O
configuration tree and is therefore causing the
connection or service to fail.
• The fault may occur even when the module passes the
electronic keying test. This may result when Disable
Keying or Compatible Keying options were used in the
module configuration instead of the Exact Match option.
• Despite passing the electronic keying test, the module
being connected to does not have the same features or
settings as the module specified in the I/O configuration
tree and does not support the connection or service being
attempted.
Check the module in use and verify that it exactly matches
the module that is specified in the application. For more
information about electronic keying, see the user manual
for the module you are using.
0x0302
Connection Request Error:
Out of communication
bandwidth.
The controller is attempting to set up a connection with the
module and has received an error: a module in the path has
exceeded its communication bandwidth capacity.
• Increase the Requested Packet Interval (RPI) and
reconfigure your network with RSNetWorx™ software.
• Distribute the load on another bridge module.
0x0303
Connection Request Error:
No bridge available.
The controller is attempting to set up a connection with the
module and has received an error: a module in the path has
exceeded its communication bandwidth capacity.
Distribute the load on another bridge module.
0x0304
Not configured to send
scheduled data.
The ControlNet module is not scheduled to send data.
Use RSNetWorx for ControlNet software to schedule or
reschedule the ControlNet network.
0x0305
Connection Request Error:
ControlNet configuration in
controller does not match
configuration in bridge.
The ControlNet configuration in the controller does not
match the configuration in the bridge module. This may
occur because a ControlNet module was changed after the
network was scheduled, or because
a new control program
has been loaded into the controller.
Use RSNetWorx for ControlNet software to reschedule the
connections.
0x0306
ControlNet Keeper not
available.
The ControlNet Configuration Master (CCM) cannot be found.
The 1756-CNB module and PLC-5® ControlNet processor are
the only devices capable of being a CCM and the CCM must
be node 1.
This fault may temporarily occur when the system is
powered up and is being cleared when the CCM is located.
Verify that a 1756-CNB modules or PLC-5 ControlNet
processor is at node 1 and is functioning properly.
0x0311
Connection Request Error:
Invalid port.
The controller is attempting to set up a connection with the
module and has received an error.
Verify that all modules in the I/O Configuration tree are the
correct modules.
Table 25 - List of Connection Fault Codes (Continued)
Fault Code
Display Text
Fault
Corrective Action