15-51
15 Troubleshooting
NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)
15-2 Troubleshooting
15
15-2-3 Troubleshooting
15-2-3 Troubleshooting
Problem Correction
Tag data is not concurrent. Check the following items and correct the user program.
• Data concurrency is maintained for each connection between the CPU
Unit and the built-in EtherNet/IP port. To maintain data concurrency for tag
data links, set a refreshing task for the network variables that are
assigned to tags. Refer to 7-1-7 Concurrency of Tag Data Link Data for
details.
• Refer to the product manuals for products from other manufacturers.
At startup, some of the receive
data is FALSE when it should be
TRUE.
• If the user program uses receive data, make sure that the All Tag Data
Link Communications Status in communications status 1 or the Controller
Operating Mode for the target node is TRUE before you use the receive
data. To use operation information from the Controller, use Controller sta-
tus in the tag sets on both the sending and receiving nodes.
• If the Fault Action setting of the output (produce) tag is enabled, The out-
put (produce) data changes to FALSE when a fatal error occurs in the
CPU Unit. Check the error status at the output (producing) Controller.
Tag data link communications are
not stable.
• For an NX701 CPU Unit, use a 1,000 Mbps Ethernet switch if 10 or 100
Mbps is set or if you are using a 10 Mbps repeater hub, a 100 Mbps
repeater hub, or a 1,000 Mbps repeater hub. The performance of the tag
data links assumes that an Ethernet switch is used to achieve a 40,000-
pps bandwidth for full-duplex, 1,000-Mbps auto-negotiation communica-
tions.
• For an NJ-series CPU Unit and an NX1P2 CPU Unit, use a 100 Mbps
Ethernet switch if 100 Mbps is set or if you are using a 10 Mbps or 100
Mbps repeater hub. For unit version 1.03 or later, the performance of the
tag data links assumes that an Ethernet switch is used to achieve a 3,000-
pps bandwidth for full-duplex, 100-Mbps auto-negotiation communica-
tions. For unit version 1.00 to 1.02, a 1,000-pps bandwidth is assumed.
• Refer to 15-3 Checking Status with the Network Configurator to access
the error counters and discarded packed counters on the Ethernet Infor-
mation Tab Page. Use the information to check for noise on the communi-
cations path, non-standard cables, damaged cables/connectors,
unexpectedly high communications traffic, and incorrect loops in connec-
tions between Ethernet switches.
• Contact the Ethernet switch manufacturer if there are problems with the
transfer capacity of the Ethernet switches in the communications path. If
Ethernet switches are cascaded, the load may be concentrated on the
middle Ethernet switches. Change the network configuration so that the
load is not concentrated.
• Also, refer to 15-3 Checking Status with the Network Configurator and use
the connection status on the Connections Tab Page to remove the cause
of the error according to information in 15-3-2 Connection Status Codes
and Troubleshooting.
To Next Page
Loading...
Need help?
General
