Rockwell Automation Publication 2080-UM002N-EN-E - November 2022
151
Chapter 8 EtherNet/IP Network
0x0111
Requested Packet Interval (RPI)
out of range.
RPI not supported.
Possible causes include the following:
• The Requested Packet Interval (RPI) specified is invalid
for this module or for a module in the path to this 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.
• For Listen Only connections, the RPI set by the owner of
this module is slower than the one requested. Either
increase the requested RPI or decrease the RPI the owner
controller is using. See the Connection tab for valid RPI
values.
0x0113
Connection Request Error:
Module connection limit
exceeded.
The number of connections is greater than what is available
on the module. The number of connections must be reduced
or the hardware must be upgraded.
To reduce the number of connections:
• Change the FLEX™ I/O communication adapter
Communications Format from Input or Output
configuration to Rack Optimization. When the
Communications Format changes, the adapter must be
removed and recreated in the I/O configuration tree.
• If the configuration uses messaging over ControlNet,
sequence the messages to reduce the number that are
executing simultaneously, or reduce the number of
messages. Messages (MSG instructions) also use
connections.
0x0114
Electronic Keying Mismatch:
Electronic keying product code
and/or vendor ID mismatch.
The Product Code of the actual module hardware does not
match the Product Code of the module that is created in the
software.
Electronic Keying failed for this module. You may have a
mismatch between the module that is created in the
software and the actual module hardware.
0x0115
Electronic Keying Mismatch:
Electronic Keying product type
mismatch.
The Product Type of the actual module hardware does not
match the Product Type of the module that is created in the
software.
Electronic Keying failed for this module. You may have a
mismatch between the module that is created in the
software and the actual module hardware.
0x0116
Electronic Keying Mismatch:
Major and/or Minor revision
invalid or incorrect.
The Major or Minor revisions of the module do not match the
Major or Minor revisions of the module that is created in the
software.
Electronic Keying failed for this module.
• Verify that you have specified the correct Major and Minor
Revision if you have chosen Compatible Module or Exact
Match keying.
• You may have a mismatch between the module that is
created in the software and the actual module hardware.
0x0117
Connection Request Error:
Invalid Connection Point.
The connection is to an invalid port or port that is already in
use.
Possible causes include the following:
• Another controller owns this module and has connected
with a Communications Format different than the one
chosen by this controller. Verify that the Communications
Format chosen is identical to that chosen by the first
owner controller of the module.
• The controller may be attempting to connect to a
nonexistent tag in a producing controller.
• 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.
Additional Error Information for this fault appears as the tag
name associated with the controller to controller (C2C) that
has the fault.
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.
Table 25 - List of Connection Fault Codes (Continued)
Fault Code
Display Text
Fault
Corrective Action