154
Rockwell Automation Publication 2080-UM002N-EN-E - November 2022
Chapter 8 EtherNet/IP Network
0x0312
Connection Request Error:
Invalid link address.
The controller is attempting to set up a connection with the
module and has received an error: an invalid link address
has been specified. A link address can be a slot number, a
network address, or the remote I/O chassis number and
starting group.
• Verify that the chosen slot number for this module is not
greater than the size of the rack.
• Verify that the ControlNet node number is not greater
than the maximum node number configured for the
network in RSNetWorx for ControlNet software.
0x0315
Connection Request Error:
Invalid segment type.
The segment type or route is invalid.
Possible causes include the following:
• The controller is attempting to set up a connection with
the module and has received an error: the connection
request is invalid.
• 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.
0x0317
Connection Request Error:
Connection not scheduled.
The controller is attempting to set up a ControlNet
connection with the module and has received an error.
Use RSNetWorx for ControlNet software to schedule or
reschedule the connection to this module.
0x0318
Connection Request Error:
Invalid link address - cannot
route to self.
The controller is attempting to set up a connection with the
module and has received an error: the link address is
invalid.
Verify that the associated ControlNet module has the
correct slot or node number selected.
0x0319
Connection Request Error:
No secondary resources
available in redundant chassis.
The controller is attempting to set up a connection with the
module and has received an error: the redundant module
does not have the necessary resources to support the
connection.
Reduce the size or number of connections through this
module or add another controller or ControlNet module to
the system.
0x031B
Connection Request Error:
Rack Connection Refused.
The controller is attempting to set up a Direct connection
with the module and has received an error.
A rack-optimized connection has already been established
to this module through the
1756-CNB/R in the same chassis.
• Connect to this module through the 1756-CNB/R in the
same chassis.
• Connect to this module through another 1756-CNB/R to
use a Direct connection.
• Change the first connection from rack-optimized to
Direct, and then re-establish the second direct
connection.
• Connect to this module from a controller in the same
chassis as the module (do not connect through a 1756-
CNB/R).
0x031E
Connection Request Error:
Cannot consume tag.
The controller is attempting to connect to a tag in a
producing controller and has received an error.
• The controller is attempting to connect to a tag in a
producing controller and that tag has already been used
by too many consumers.
• Increase the maximum number of consumers on the tag.
0x031F
Connection Request Error:
Tag not published.
The Consume tag was not configured to be produced in the
target module.
Make sure the name of the tag being consumed is spelled
correctly in both the consumer and producer.
0x0322
Connection Request Error:
Data format for requested
connection does not match
data format of connection
already established.
A new connection that is requested does not match the
existing connection.
Check the controllers that are using the connection and
verify that all configurations are identical.
0x0800
Network link in path to module
is offline.
A connection has already been established to the target
module at a different RPI and it cannot be changed to
accommodate the RPI specified.
It is either not physically connected to the network (media
disconnected) or otherwise unable to forward the request
onto the destination network.
0x0801
Incompatible Multicast RPI.
The controlling application has not initialized the data to be
produced by the target device. This may be caused when
“Send Data” connections are configured in a target device
and the controlling application for that target device has not
initialized the data to be produced.
• Configure the tag as unicast.
• Adjust the RPI so that all multicast consumers of the tag
use the same RPI.
• Configure the RPI so that is in the range that is allowed by
the producer.
Table 25 - List of Connection Fault Codes (Continued)
Fault Code
Display Text
Fault
Corrective Action