4.4. Ethernet Communication Troubleshooting
4.4. Ethernet Communication Troubleshooting
When the system does not operate normally related to the RS-232C communication, open the Command Prompt window as shown in [Figure 4.25] and [Figure 4.26], and execute the ping command for the IP address of the robot controller.
The conclusion based on the test result is shown in [Table 4-4].
Figure 4.25 Example of Ping Response from Robot Controller
Figure 4.26 Example of No Ping Response from Robot Controller
Table 4‑4 Ping Test Result from Robot Controller
Result | Conclusion (Estimated cause) |
Reply from {IP address} is shown. That is, there is a ping response from the robot controller. | Even though the Ethernet connection between the robot controller and the PC is normal, the communication is failing due to a different cause. - Incorrect communication setting in HRLadder - Robot controller monitoring service error → Try rebooting both the HRLadder and the robot controller. - Service for HRLadder prohibited due to Windows Firewall → Include HRLadder to the exceptional program list of the Windows Firewall. (Control Panel – Security Center – Windows Firewall – Exception Tab) |
Request timed out is shown. That is, there is no ping response from the robot controller. | ▶ When the applicable PC has problem connecting to Internet or LAN: → Ethernet function error on PC. Request to have PC checked |
▶ When the applicable PC does not have problems connecting to Internet or LAN: - Incorrect IP address setting or incorrect subnet.
- Incorrect Ethernet connection between robot controller and PC. (Disconnected cable, defective cable etc.) - (When using hub) Hub error, poor power supply → Check/Replace cable after testing with LAN tester.
- Disconnected Ethernet cable inside the robot controller cabinet Or Ethernet function error on controller main board → Consult the A/S Center |