Rockwell Automation 2080-L50E-24AWB, Руководство пользователя, Страница: 149 / 390

Rockwell Automation Publication 2080-UM002N-EN-E - November 2022 149
Chapter 8 EtherNet/IP Network
0x0012
Requested service specifies an
operation that is going to
fragment a primitive data
value.
The service specified an operation that is going to fragment
a primitive data value (for example, half a REAL data type).
• The size of the data being read or written must be
rounded to the next primitive data type size.
• The service is operating on data that is too large for the
underlying communication size limits.
0x0013
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.
0x0014
Undefined or unsupported
attribute.
A MSG instruction is configured to change an attribute that
does not exist.
See the device user manual for available programming
options.
0x0015
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.
0x0100
Connection Request Error:
Module in Use.
The connection being accessed is already in use.
Check for these conditions:
• The controller is attempting to make a specific
connection to a module and the module cannot support
multiple connections.
• The target of a connection recognizes that the owner is
attempting to remake a connection that is already
running.
0x0103
Service Request Error:
CIP transport class not
supported.
This indicates that the controller is requesting a transport
class that is not supported by the module.
Possible causes include the following:
• The controller is requesting services that are not
supported by 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 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 that is specified in the application. For more
information about electronic keying, see the user manual
for the module you are using.
0x0106
Connection Request Error:
Module owned and configured
by another controller. Module
may accept only one
connection if Unicast is used.
An ownership conflict occurred for the connection.
Check for these conditions:
• The Connection Request to this module has been rejected
due to an ownership conflict with another owner (for
example, another controller). This may occur with
modules, such as output modules that allow only one
owner to configure and control its outputs. This fault may
also occur if the module is configured as Listen Only and
supports only one connection.
• If the owner is connected to the module with a unicast
connection over EtherNet/IP network, other connections
to the module may fail because the owner controls the
one connection.
• If the owner is connected to the module with a multicast
connection over EtherNet/IP network, unicast
connections to the module may fail because the owner
controls the one connection. Configure both the owner
and the Listen Only connection as multicast.
Table 25 - List of Connection Fault Codes (Continued)
Fault Code Display Text Fault Corrective Action