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

I/O fault codes Chapter 3
Code Interpretation
#0205 Possible causes include the following.
•
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 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.
#0206 Possible causes include the following.
•
The controller is attempting to set up a connection with the module and has received an error - the request size is too large. Verify that the path to this module is
sufficiently close to the controller.
• 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.
#0301 One of these conditions may exist.
•
The controller is attempting to set up a connection with the module and has received an error: a module in the path is out of memory.
• The controller may be attempting to connect to a tag in a producing controller that is not marked as being produced.
• The controller may be attempting to connect to a tag in a producing controller. That tag may not be configured to allow enough consumers.
• The size or number of connections through this module needs to be reduced.
• One of the network modules between the module and the controller may be out of memory. Check network configuration of the system.
• The module may be out of memory. Check the system configuration and capabilities 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 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.
#0302 The controller is attempting to set up a connection with the module and has received an error: a module in the path has exceeded its communication bandwidth
capacity.
Increase the Requested Packet Interval (RPI) and reconfigure your network with RSNetWorx software.
Distribute the load on another bridge module.
#0303 The controller is attempting to set up a connection with the module and has received an error: a module in the path has exceeded its communication bandwidth
capacity.
Distribute the load on another bridge module.
#0304 The ControlNet module is not scheduled to send data. Use RSNetWorx for ControlNet software to schedule or reschedule the ControlNet network.
#0305 The ControlNet configuration in the controller does not match the configuration in the bridge module. This may occur because a ControlNet module was changed after
the network was scheduled, or because a new control program has been loaded into the controller.
Use RSNetWorx for ControlNet software to reschedule the connections.
Rockwell Automation Publication 1756-PM014G-EN-P – October 2014 45