Rockwell Automation Logix5000 Controllers Major, Minor, and I/O Faults Programming Manual User Manual

Page 48

Chapter 3 I/O fault codes

Code

Interpretation

#FE09

Possible causes include the following.
•

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 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 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.

#FE0A

A connection has been opened without the output force pointer being set.

#FE0B

Possible causes include the following.
•

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

#FE0C

The controller is attempting to set up a connection with the PLC-5 controller and has received an error.
Verify that the instance number specified has been properly specified in the PLC-5 controller.

#FE0D

The symbol instance number was found to not be set.

#FE0E

The module is currently being updated.

#FE0F

Firmware supervisor has attempted to update an unsupported module.

#FE10

The firmware file to update the module cannot be found.

#FE11

The firmware file is corrupted.

#FE12

An error has occurred while updating the module.

#FE13

An active connection could not be made to the target module.

#FE14

The firmware file is currently being read.

#FE22

The target-to-originator netparams connection type is invalid.

#FE23

The target-to-originator netparams connection does not specify whether unicast is allowed.

#FF00

The controller is attempting to set up a connection with the module and has received an error.
Verify that the physical module is the same module type (or is a compatible module) as created in the software.
If the module is a 1756-DHRIO module in a remote chassis (connected via a ControlNet network), verify that the network has been scheduled with RSNetWorx software.
Even after the network has been scheduled with RSNetWorx for ControlNet software, if you are online and if the 1756-DHRIO module is configured for DH+ network
only, a #ff00 Module Fault (no connection instance) may occur. The module is properly communicating even though Faulted is displayed as its Status on the Module
Properties dialog box. Disregard the error message and fault status and continue.

#FF01

The controller is attempting to set up a connection with the module and has received an error.
Verify that the path to this module is a valid length.

#FF04

The controller’s map instance attempted to access a connection while in an invalid state.

#FF08

The controller is attempting to set up a connection with the module and has received an error.
Verify that the path to this module is a valid length.

Rockwell Automation Publication 1756-PM014G-EN-P – October 2014