Omron Sysmac NJ-series

15-37
15 Troubleshooting
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
15-2 Troubleshooting
15
15-2-2 Error Descriptions
*1 This applies to an NJ-series CPU Unit.
*2 This applies to an NX-series CPU Unit.
Event name Tag Data Link Connection Failed Event code 84070000 hex
Meaning Establishing a tag data link connection failed.
Source EtherNet/IP Function Module Source details
CIP,
*1
CIP1,
*2
or
CIP2
*2
Detection
timing
When establish-
ing tag data link
connection
Error attributes Level Minor fault Recovery Automatic
recovery
Log category System
Effects User program Continues. Operation Data links will not operate for connections that could not
be established. Data links for other connections will oper-
ate.
Indicators EtherNet/IP NET RUN EtherNet/IP NET ERR EtherNet/IP LINK/ACT
Flashes at 1-s intervals. Flashes at 1-s intervals. ---
System-defined
variables
Variable Data type Name
_EIP_TDLinkOpnErr
*1
BOOL Tag Data Link Connection Failed
_EIP1_TDLinkOpnErr
*2
BOOL CIP Communications1 Tag Data Link
Connection Failed
_EIP2_TDLinkOpnErr
*2
BOOL CIP Communications2 Tag Data Link
Connection Failed
Cause and
correction
Assumed cause Correction Prevention
The tag data link connection informa-
tion is not the same for the originator
and target.
Correct the tag data link connection
information, and then download the
device parameters or connection set-
tings from the Network Configurator
or Sysmac Studio.
Before you use the tag data links,
make sure that the tag data link con-
nection information in the originator
and target are suitable.
Insufficient connections Reduce the number of class-3 mes-
sages.
Reduce the number of data links and
class-3 messages that are used.
Attached
information
Attached information 1: Target node IP address (example: C0A8FA01 hex = address 192.168.250.1)
Attached information 2: Connection instance No. 0 to 255
Attached information 3: Connection status (example: 010000117 hex for General Status 01 and Additional Status 0117)
Precautions/
Remarks
• You can investigate a detailed cause from the connection status.
Refer to 15-3-2 Connection Status Codes and Troubleshooting.
• This event occurs only once even if this error occurred simultaneously in several connections for the same target
node.