Filter
Top Products
200
Troubleshooting Procedures Section 10-5
Opening and Closing
Problems
Refer to General Problems on page 199.
Reception Problems
1,2,3... 1. Is reception processing finishing?
True ➨ Step 10.
2. Is the remote node not processing to send data?
True ➨ Adjust the remote node to process send data.
3. Read controller status using the FINS command READ CONTROLLER
STATUS.
4. Have any reception errors occurred?
True ➨ There may be noise affecting the network. Increase the number of
retries or take measures against noise as described in Appendix
A Network Installation or 3-6-4 Connecting the Power Supply
(CS1W-ETN01 Only).
5. Read memory status using the FINS command READ MEMORY STATUS.
6. Is the network memory being used more than 80%?
True ➨ There may be too much load on the Ethernet Unit. If the memory
exhaustion records show counts, UDP data may be corrupted.
Check your applications.
7. Read protocol status using the FINS command READ PROTOCOL STA-
TUS.
8. Are any of the first three items in the status being counted?
True ➨ The UDP protocol of the remote node may not be compatible with
that of the Ethernet Unit. Use another communications service.
9. Check the remote node for transmission problems using the next proce-
dure. If nothing is uncovered, go to 10-5-6 Network Connection Problems
on page 203.
10. Return to the procedure for general problems.
Transmission Problems
1,2,3... 1. Is send processing not finishing?
True ➨ Return to the procedure for general problems.
2. Read protocol status using the FINS command READ PROTOCOL STA-
TUS.
3. Have any failures to reach the destination been counted in the ICMP sta-
tus?
True ➨ The UDP socket specified by the destination UDP port number in
the send parameters is not opening at the remote node.
4. Read controller status using the FINS command READ CONTROLLER
STATUS.
5. Have any send errors occurred?
True ➨ There may be too much traffic on the network and UDP packets
may be getting corrupted. Use TCP sockets or adjust the network
to reduce excessive traffic.
6. Check the reception status on the remote node.
7. Return to the procedure for general problems.