Module Faults: 16#0200 - 16#02ff

TUV
Code
String
Explanation and Possible Causes/Solutions
16#0203
Connection timed out.
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 are using FLEX I/O modules, verify that you are using the correct terminal device.
16#0204
Connection Request Error: Connection request timed out.
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 these actions:
  • 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.
16#0205
Connection Request Error: Invalid parameter.
Either:
  • The controller is attempting to set up a connection with the module and has received an error - a parameter is in error.
  • 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#0206
Connection Request Error: Requested size too large.
Either:
  • The controller is attempting to set up a connection with the module and has received an error - the request size is too large.
  • 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.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.