Revision history [back]

And in console there is a error massage like:

Failed to connect to server, rc -1, Error: "No route to host" (errno: 113)

The massage on TP is

34447 I RSTA Waiting for ROS state prox

This tells me that the driver hasn't actually connected to your Roboguide simulation.

First I run TP program (ROSSTATE) and run on Linux PC as:

roslaunch fanuc_lrmate200id_support robot_state_visualize_lrmate200id.launch robot_ip:=IP_OF_ROBOGUIDE use_bswap:=false

Did you replace IP_OF_ROBOGUIDE with an actual IP address (ie: 1.2.3.4)?

Can you ping the IP of the computer running Roboguide from your ROS computer?

If you cannot, then the driver cannot connect either.

If you can ping, and have replaced IP_OF_ROBOGUIDE with the actual IP address, but the driver still cannot connect, make sure your Windows machine isn't blocking incoming connections to Roboguide. Check the Windows Firewall settings.

And in console there is a error massage like:

Failed to connect to server, rc -1, Error: "No route to host" (errno: 113)

The massage on TP is

34447 I RSTA Waiting for ROS state prox

This tells me that the driver hasn't actually connected to your Roboguide simulation.

RVIZ started but the robots configuration (RVIZ and ROBOGUIDE) are not match.

which would be the case if the driver hasn't actually connected to Roboguide.

First I run TP program (ROSSTATE) and run on Linux PC as:

roslaunch fanuc_lrmate200id_support robot_state_visualize_lrmate200id.launch robot_ip:=IP_OF_ROBOGUIDE use_bswap:=false

Did you replace IP_OF_ROBOGUIDE with an actual IP address (ie: 1.2.3.4)?

Can you ping the IP of the computer running Roboguide from your ROS computer?

If you cannot, then the driver cannot connect either.

If you can ping, and have replaced IP_OF_ROBOGUIDE with the actual IP address, but the driver still cannot connect, make sure your Windows machine isn't blocking incoming connections to Roboguide. Check the Windows Firewall settings.

And in console there is a error massage like:

Failed to connect to server, rc -1, Error: "No route to host" (errno: 113)

The massage on TP is

34447 I RSTA Waiting for ROS state prox

This tells me that the driver hasn't actually connected to your Roboguide simulation.

RVIZ started but the robots configuration (RVIZ and ROBOGUIDE) are not match.

which would be the case if the driver hasn't actually connected to Roboguide.

First I run TP program (ROSSTATE) and run on Linux PC as:

roslaunch fanuc_lrmate200id_support robot_state_visualize_lrmate200id.launch robot_ip:=IP_OF_ROBOGUIDE use_bswap:=false

Did you replace IP_OF_ROBOGUIDE with an actual IP address (ie: 1.2.3.4)?

Can you ping the IP of the computer running Roboguide from your ROS computer?

If you cannot, then the driver cannot connect either.

If you can ping, and have replaced IP_OF_ROBOGUIDE with the actual IP address, but the driver still cannot connect, make sure your Windows machine isn't blocking incoming connections to Roboguide. Check the Windows Firewall settings.

And in console there is a error massage like:

Failed to connect to server, rc -1, Error: "No route to host" (errno: 113)

The massage on TP is

34447 I RSTA Waiting for ROS state prox

This tells me that the driver hasn't actually connected to your Roboguide simulation.

RVIZ started but the robots configuration (RVIZ and ROBOGUIDE) are not match.

which would be the case if the driver hasn't actually connected to Roboguide.

First I run TP program (ROSSTATE) and run on Linux PC as:

roslaunch fanuc_lrmate200id_support robot_state_visualize_lrmate200id.launch robot_ip:=IP_OF_ROBOGUIDE use_bswap:=false

Did you replace IP_OF_ROBOGUIDE with an actual IP address (ie: 1.2.3.4)?

Can you ping the IP of the computer running Roboguide from your ROS computer?

If you cannot, then the driver cannot connect either.

If you can ping, and have replaced IP_OF_ROBOGUIDE with the actual IP address, but the driver still cannot connect, make sure your Windows machine isn't blocking incoming connections to Roboguide. Check the Windows Firewall settings.

Edit:

I tried setting IP and gateway as follows: Linux PC IP: 192.168.0.100 Mask: 255.255.255.0 (Default Gateway: 192.168.0.101)

WinPC (installed ROBOGUIDE) IP: 192.168.0.101 Mask: 255.255.255.0

ROBOT (ROBOGUIDE) IP: 192.168.0.2 Mask: 255.255.255.0 (Default gateway: 192.168.0.101)

Connection between Linux and Windows seems to be good (by ping) However, I couldn't connect to (virtual) robot. Are there mistakes with IP setting described above. (Sorry I am not good at communication)

The problem here is that you are trying to configure the virtual robot's IP, which doesn't work.

Roboguide will always use the IP of your Windows PC for the virtual robot.

So in your case, the IP of your virtual robot is 192.168.0.101. If you use that IP for the robot_ip argument to the launch file, things should start working.

And in console there is a error massage like:

Failed to connect to server, rc -1, Error: "No route to host" (errno: 113)

The massage on TP is

34447 I RSTA Waiting for ROS state prox

This tells me that the driver hasn't actually connected to your Roboguide simulation.

RVIZ started but the robots configuration (RVIZ and ROBOGUIDE) are not match.

which would be the case if the driver hasn't actually connected to Roboguide.

First I run TP program (ROSSTATE) and run on Linux PC as:

roslaunch fanuc_lrmate200id_support robot_state_visualize_lrmate200id.launch robot_ip:=IP_OF_ROBOGUIDE use_bswap:=false

Did you replace IP_OF_ROBOGUIDE with an actual IP address (ie: 1.2.3.4)?

Can you ping the IP of the computer running Roboguide from your ROS computer?

If you cannot, then the driver cannot connect either.

If you can ping, and have replaced IP_OF_ROBOGUIDE with the actual IP address, but the driver still cannot connect, make sure your Windows machine isn't blocking incoming connections to Roboguide. Check the Windows Firewall settings.

Edit:

I tried setting IP and gateway as follows: Linux PC IP: 192.168.0.100 Mask: 255.255.255.0 (Default Gateway: 192.168.0.101)

WinPC (installed ROBOGUIDE) IP: 192.168.0.101 Mask: 255.255.255.0

ROBOT (ROBOGUIDE) IP: 192.168.0.2 Mask: 255.255.255.0 (Default gateway: 192.168.0.101)

Connection between Linux and Windows seems to be good (by ping) However, I couldn't connect to (virtual) robot. Are there mistakes with IP setting described above. (Sorry I am not good at communication)

The problem here is that you are trying to configure the virtual robot's IP, which doesn't work.

Roboguide will always use the IP of your Windows PC for the virtual robot.

So in your case, the IP of your virtual robot is 192.168.0.101. If you use that IP for the robot_ip argument to the launch file, things should start working.

Edit 2:

Hello, finally I could connect to my LR mate from RVIZ. The initial configuration of rviz robot is same as the real one. However, it doesn't trace jogging motion.

please update your original question with the exact sequence of steps and commands you use to start everything. On both the ROS PC and the Roboguide robot Teach Pendant (or the real one).

Use the edit button/link to append (ie: add, don't overwrite) the new information to your original question text.