Module Faults: 16#fe00 - 16#feff

TUV
Code
String
Explanation and Possible Causes/Solutions
16#fe01
An invalid configuration format was encountered.
16#fe02
Requested Packet Interval (RPI) out of range.
The Requested Packet Interval (RPI) specified is invalid for this module.
  • See the Connection tab for valid RPI values.
16#fe03
The input connection point has not been set.
16#fe04
Connection Request Error: Invalid input data pointer.
The controller is attempting to set up a connection with the module and has received an error.
16#fe05
Connection Request Error: Invalid input data size.
Either:
  • The controller is attempting to set up a connection with the module and has received an 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#fe06
The input force point has not been set.
16#fe07
The output connection point has not been set.
16#fe08
Connection Request Error: Invalid output data pointer.
The controller is attempting to set up a connection with the module and has received an error.
16#fe09
Connection Request Error: Invalid output data size.
Either:
  • The controller is attempting to set up a connection with the module and has received an 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#fe0a
The output force pointer has not been set.
16#fe0b
Invalid symbol string.
Either:
  • The tag to be consumed on this module is invalid. Verify that the tag is marked as being produced.
  • 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#fe0c
Invalid
PLC-5
 instance number.
The controller is attempting to set up a connection with the
PLC-5
 and has received an error.
Verify that the instance number specified has been properly specified in the
PLC-5
.
16#fe0d
Tag does not exist in peer controller.
The symbol instance number was found to not be set.
16#fe0e
Automatic Firmware Update in progress.
The module is currently being updated.
16#fe0f
Automatic Firmware Update Failed: Firmware file incompatible with the module.
Firmware supervisor has attempted to update an unsupported module.
16#fe10
Automatic Firmware Update Failed: Firmware file not found.
The firmware file to update the module cannot be found.
16#fe11
Automatic Firmware Update Failed: Firmware file invalid.
The firmware file is corrupted.
16#fe12
Automatic Firmware Update Failed.
An error has occurred while updating the module.
16#fe13
Automatic Firmware Update Failed: Detected Active Connections.
An active connection could not be made to the target module.
16#fe14
Automatic Firmware Update pending: Searching NVS file for appropriate module identity.
The firmware file is currently being read.
16#fe22
The target-to-originator netparams connection type is invalid.
16#fe23
The target-to-originator netparams connection does not specify whether unicast is allowed.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.