Module Faults: 16#0000 - 16#00ff

These are the module faults: 16#0000 - 16#00ff
Code
String
Explanation and Possible Causes/Solutions
16#0001
Connection Error.
A connection to a module failed.
16#0002
Resource unavailable.
Either:
  • there are not enough connections available either for the controller or for the communication module being used to connect through.
    Check the connection use of the controller or communication module. If all of the connections are used, try to free some of the used connections or add another module to route the errant connection through.
  • the I/O memory limits of the controller are exceeded.
    Check the I/O memory available and make program or tag changes if needed.
  • the I/O module targeted does not have enough connections available.
    Check the number of controllers making a connection to this I/O module and verify that the number of connections is within the limits of the I/O module.
16#0005
Connection Request Error: Bad Class
The controller is attempting to make a connection to the module and has received an error.
Either:
  • the configured address for the connection to the module is incorrect.
  • 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 Module 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 specified in the I/O configuration tree of the
    Logix Designer
     application.
    If you are using a 1756-DHRIO module, verify that the Channel type selected in the software (
    DH+
     or remote I/O network) matches the module’s rotary switch settings.
16#0006
Connection Request Error: Bad Class.
Either:
  • the response buffer is too small to handle the response data.
  • 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 Module 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 specified in the I/O configuration tree of the
    Logix Designer
     application.
16#0007
Connection Request Error: Bad Class.
A service request is unconnected, but should be connected.
16#0008
Service Request Error: Unsupported Service
The controller is attempting to request a service from the module that is not supported by the module.
16#0009
Module Configuration Invalid: parameter error.
Tip:
Additional Fault Information for this fault will be displayed as a hex code on the Connection Tab.
The configuration for the module is invalid. The module configuration may have been changed in the Data Monitor or programmatically.
If available for the module, access the Connections tab of the Module Properties dialog box for the additional fault code. The additional fault code indicates the configuration parameter that is causing the fault. You may have to correct multiple parameters before this fault is cleared and connection is properly established.
16#000A
An attribute in the Get_Attributes_List or Set_Attributes_List has a non-zero status.
Either:
  • a connection is being created where the connection type is invalid.
  • an object attribute or tag value is invalid.
If an object attribute or tag is invalid, export the
Logix Designer
 file, then re-import it. Reschedule the ControlNet network after re-importing if applicable.
16#000C
Service Request Error: Invalid mode/state
for service request.
The controller is attempting to request a service from the module and has received an error. First, verify that the module is not faulted.
For an I/O module, this may indicate that the module has one of these conditions:
  • Limited communication, but has a Major Fault
  • A firmware update needs to be completed or is currently being completed.
Refer to the Module Info tab to determine the exact cause.
16#000D
Object already exists.
An I/O map instance is created where the instance is already in use.
16#000E
Attribute value cannot be set.
A MSG instruction is configured to change an attribute value that cannot be changed.
16#000F
Access permission denied for requested service.
A MSG instruction has been configured to delete a map object that cannot be deleted.
16#0010
Mode or state of module does not allow object to perform requested service.
The state of the device prevents a service request from being handled.
16#0011
Reply data too large.
The reply to a message has a data size that is too large for the destination.
Change the destination to a tag that can handle the data size and type being returned.
16#0013
Module Configuration Rejected: Data size too small.
The configuration for the module is invalid - not enough configuration data was sent.
Verify that the correct module is being targeted.
16#0014
Undefined or unsupported attribute.
A MSG instruction is configured to change an attribute that does not exist.
16#0015
Module Configuration Rejected: Data size too large.
The configuration for the module is invalid - too much configuration data was sent.
Verify that the correct module is being targeted.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.