ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
ERROR 1441118076.606392345: Failed to connect to server, rc: -1. Error: 'Connection timed out' (errno: 110)
This seems to suggest that the fanuc_driver/robot_state
node running on your ROS PC is unable to connect with the ros_state
program running on your simulated robot controller. I can think of a number of reasons why this could be the case:
robot_ip
is incorrect: make sure this is the IP of the Windows PC running Roboguidefrvirtual.exe
process (which actually runs the virtual controller) is allowed to accept connections on ports 11000 and 11002 from hosts on your network. See Allow a program to communicate through Windows Firewall fi on how to do this for Windows 7.You can use the following command to check whether things would work (without having to use the robot_state_visualize_m20ia.launch
file):
nc ip.of.your.windowspc 11002
This should begin to dump a continuous stream of semi-printable data to your terminal (use ctrl+c
to stop it).
2 | No.2 Revision |
ERROR 1441118076.606392345: Failed to connect to server, rc: -1. Error: 'Connection timed out' (errno: 110)
This seems to suggest that the fanuc_driver/robot_state
node running on your ROS PC is unable to connect with the ros_state
program running on your simulated robot controller. I can think of a number of reasons why this could be the case:
robot_ip
is incorrect: make sure this is the IP of the Windows PC running Roboguidefrvirtual.exe
process (which actually runs the virtual controller) is allowed to accept connections on ports 11000 and 11002 from hosts on your network. See Allow a program to communicate through Windows Firewall fi on how to do this for Windows 7.You can use the following command (on your ROS pc) to check whether things would work (without having to use the robot_state_visualize_m20ia.launch
file):
nc ip.of.your.windowspc 11002
This should begin to dump a continuous stream of semi-printable data to your terminal (use ctrl+c
to stop it).