The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
What sort of router? Do you mean a switch? Because from the tracepath output it doesn't look like there is a router. I would've expected to see a hop between you and the robot in that case with a different IP address.
Could you tell us what sort of computers are involved? A laptop? A desktop PC? Is there a wireless link involved?
Could you also login to the robot (using SSH, user: root, pass: easybot) and try to ping 192.168.69.4? Also try: nc 192.168.69.4 50002 when you have the driver running on the ROS side. If that doesn't connect or time-out (it can take a while, up to 2.5 minutes), it would indicate something is blocking connections between the robot controller and the ROS PC.
| | 2 | No.2 Revision |
What sort of router? Do you mean a switch? Because from the tracepath output it doesn't look like there is a router. I would've expected to see a hop between you and the robot in that case with a different IP address.
Could you tell us what sort of computers are involved? A laptop? A desktop PC? Is there a wireless link involved?
Could you also login to the robot (using SSH, user: root, pass: easybot) and try to ping 192.168.69.4? Also try: nc 192.168.69.4 50002 when you have the driver running on the ROS side. If that doesn't connect or time-out (it can take a while, up to 2.5 minutes), it would indicate something is blocking connections between the robot controller and the ROS PC.
Right now I believe you're using the wrong IP address for the reverse connection (ie: the one from the robot controller to the PC).
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
