Rockwell Automation Logix5000 Controllers Major, Minor, and I/O Faults Programming Manual - Manual (Page 43)

I/O fault codes Chapter 3
Code Interpretation
#0109 The connection size is inconsistent with the expected size.
Possible causes include the following.
•
The controller is attempting to set up a connection with the module and cannot because the size of the connection is invalid.
• The controller may be attempting to connect to a tag in a producing controller whose size does not match the tag in this 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 passed 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 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 specified in the I/O configuration tree of the Logix Designer application.
For more information about electronic keying, see the user manual for the module you are using.
If the module is a 1756 ControlNet module, verify that the chassis size is correct.
For remote I/O adapters, verify that the rack size and rack density is correct.
#0110 The controller is attempting to set up a Listen Only connection with the module and cannot because the module has not been configured and connected to by an Owner
(for example, another controller). This controller is not an Owner of this module because it is attempting to establish a Listen Only connection, which requires no
module configuration. It cannot connect until an Owner configures and connects to the module first.
#0111 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 are used in the
module configuration instead of the Exact Match option.
Despite passing the electronic keying test, the module being connected 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 matches the module specified in the I/O configuration tree of the Logix Designer 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.
#0114 The Product Code of the actual module hardware does not match the Product Code of the module created in the software.
Electronic Keying failed for this module. You may have a mismatch between the module created in the software and the actual module hardware.
#0115 The Product Type of the actual module hardware does not match the Product Type of the module created in the software.
Electronic Keying failed for this module. You may have a mismatch between the module created in the software and the actual module hardware.
#0116 The Major or Minor revisions of the module do not match the Major or Minor revisions of the module created in the software.
Verify that you have specified the correct Major and Minor Revision if you have chosen Compatible Module or Exact Match keying
Electronic Keying failed for this module. You may have a mismatch between the module created in the software and the actual module hardware.
Rockwell Automation Publication 1756-PM014G-EN-P – October 2014 43