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

Chapter 3 I/O fault codes
Code Interpretation
#0117 The connection is to an invalid port or port that is already in use.
One of these conditions exists.
•
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 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.
• The controller may be attempting to connect to a nonexistent tag in a producing controller.
#0118 An invalid configuration format was used.
One of these conditions exists.
•
The configuration class specified does not match the class supported by the module.
• The connection instance is not recognized by the module.
• The path specified for the connection is inconsistent.
• 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.
#0119 The controlling connection is not open.
Where a Listen Only connection is requested, the controlling connection is not open.
#011A The controller is attempting to set up a connection with the module and cannot because required resources are unavailable.
If the module is a 1756 ControlNet module, up to five controllers can make Rack Optimization connections to the module. Verify that this number has not been
exceeded.
If the module is a 1794-ACN15, 1794-ACNR15, or 1797-ACNR15 adapter, only one controller can make a Rack Optimization connection to the module. Verify that this
number has not been exceeded.
#0203 The owner or originator recognizes that the target device is on the network or backplane. However, I/O data and messages are not being responded to. In other words,
the target can be reached, but its response is not as expected. For example, this fault may be indicated where multicast Ethernet packets are not returned.
When this fault occurs, the controller usually attempts to continuously remove and remake the connection.
If you use FLEX I/O modules, verify that you are using the correct terminal device.
#0204 The controller is attempting to make a connection; however, the target module is not responding.
The device also appears to be missing from the backplane or network.
To recover, take the following steps.
•
Verify that the module has not been removed and is still functioning and receiving power.
• Verify that the correct slot number has been specified.
• Verify that the module is properly connected to the network.
If you are using FLEX I/O modules, verify that the correct terminal block is in use.
44 Rockwell Automation Publication 1756-PM014G-EN-P – October 2014