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

Chapter 3 I/O fault codes
Code Interpretation
#0014 A MSG instruction is configured to change an attribute that does not exist.
#0015 The configuration for the module is invalid. Too much configuration data was sent.
Verify that the correct module is being targeted.
#0100 The connection being accessed is already in use.
Possible causes include the following.
•
The controller is attempting to make a specific connection to a module and the module cannot support more than one of these connections.
• The target of a connection recognizes that the owner is attempting to remake a connection that is already running.
#0103 Possible causes include the following.
•
The controller is requesting services not supported by 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 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 Logix Designer application.
For more information about electronic keying, see the user manual for the module you are using.
#0106 An ownership conflict occurred for the connection.
One of the following conditions exists.
•
The Connection Request to this module has been rejected due to an Ownership conflict with another Owner (for example, another Controller). This may occur with
modules, such as output modules, that allow only a single Owner to configure and control its outputs.
This fault may also occur if the module is configured as Listen Only and supports only one connection.
• If the Owner is connected to the module with a Unicast connection over EtherNet/IP network, other connections to the module may fail because the Owner controls
the one connection.
If the Owner is connected to the module with a Multicast connection over EtherNet/IP network, Unicast connections to the module may fail because the Owner
controls the one connection.
Configure both the Owner and the Listen Only connection as Multicast.
#0107 A connection being accessed was not found.
#0108 An invalid connection type was used.
One of the following conditions exists.
•
The controller is requesting a connection type not supported by 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 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.
• You have configured a consumed tag or module to use a Unicast connection over EtherNet/IP network, but the producer does not support Unicast connections.
42 Rockwell Automation Publication 1756-PM014G-EN-P – October 2014