[ros-users] Strange problem running ROS across multiple machines

[Ander Ansuategui]

Hi,

Thanks for your fast response and advice. We resolved the issue by adding the ip-hostname of the laptop in the robot’s /etc/hosts file. We already had the robots ip-hostname in the laptop’s hosts file, but the other one was missing. We didn’t thought this was necessary because what was failing was the communication in the opposite direction (from laptop to robot). However, it seems that each computer needs the other ones hostname.

Thanks again for your help.

Ander

On Thu, 2011-09-08 at 11:27 +0200, Lorenz M�senlechner wrote:
> Hi,
>
> have a look at the network setup wiki page:
> http://www.ros.org/wiki/ROS/NetworkSetup
>
> Lorenz
>
> > Hi Ander,
> >
> > Have you checked ROS_IP or ROS_HOSTNAME in addition to ROS_MASTER_URI? I’ve had similar problems when not setting these variables on my teleop computer.
> >
> > Take a look here: http://www.ros.org/wiki/ROS/EnvironmentVariables#ROS_IP.2BAC8-ROS_HOSTNAME
> >
> > Benoit
> >
> >
> > From: Ander Ansuategui
> > Sent: Thursday, September 08, 2011 10:57 AM
> > To: ros-users at code.ros.org
> > Subject: [ros-users] Strange problem running ROS across multiple machines
> >
> > Hi,
> >
> > we are facing some strange problems regarding communication between multiple  machines. We are developing a teleoperation package for our Segway RMP200 robot, which has a Kinect on top. We run roscore, openni and the segway driver on the robot, and we can see all the topics by using rostopic list  command from a laptop. Moreover, we receive the kinect image successfully in our teleoperation application running in the laptop, and we also have a ros service running on the robot, which is called also successfully.
> >
> > The problem comes when we try to move the robot by sending Twist messages to /cmd_vel topic. Apparently the messages don’t reach the robot because when we run “rostopic echo /cmd_vel” command no data is shown. But when running the same command in the laptop, the data is shown as expected.
> >
> > Following the tutorials, we have just changed the  laptop’s ROS_MASTER_URI var. We have tried ad-hoc wired and wireless communication. We are surprised because most of the communication works (kinect and service call for instance) but writing to topics doesn’t. Has anyone experienced a similar behavior?
> >
> > We would be very grateful for any help.
> >
> > Regards.
> >
> > Ander
> >
> >
> > Mezu honen informazioa isilpekoa izan daiteke eta indarrean dagoen legediak babesten du. Hutsegite baten ondorioz jaso baduzu, bidal iezaiozu berriro bidaltzaileari eta ezaba ezazu. Milesker zure laguntzagatik.
> > La información de este correo puede ser confidencial y está protegida por la legislación vigente. Si ha recibido este correo por error, reenvíelo a su emisor y elimínelo. Gracias por su ayuda.
> > This e-mail may contain confidential information that is protected by our laws. If you have received this e-mail by mistake, please, notify the sender and delete it. Thank you for your help.
> >
> >
> >
> > --------------------------------------------------------------------------------
> > _______________________________________________
> > ros-users mailing list
> > ros-users at code.ros.org
> > https://code.ros.org/mailman/listinfo/ros-users
>
> > _______________________________________________
> > ros-users mailing list
> > ros-users at code.ros.org
> > https://code.ros.org/mailman/listinfo/ros-users
>
>


_______________________________________________
ros-users mailing list
ros-users at code.ros.org
https://code.ros.org/mailman/listinfo/ros-users


Mezu honen informazioa isilpekoa izan daiteke eta indarrean dagoen legediak babesten du. Hutsegite baten ondorioz jaso baduzu, bidal iezaiozu berriro bidaltzaileari eta ezaba ezazu. Milesker zure laguntzagatik.
La información de este correo puede ser confidencial y está protegida por la legislación vigente. Si ha recibido este correo por error, reenvíelo a su emisor y elimínelo. Gracias por su ayuda.
This e-mail may contain confidential information that is protected by our laws. If you have received this e-mail by mistake, please, notify the sender and delete it. Thank you for your help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20110908/64613196/attachment-0002.html>