daniel_ctae's profile - activity

Hello all,

As Lorenz suggested defining the ROS_IP solved my problem. I had different network interfaces (wlan0, eth0, etc) and I had to explicitly tell ROS which one to use. This is clearly explained in http://www.ros.org/wiki/ROS/EnvironmentVariables : "This setting is only needed in situations where you have multiple addresses for a computer and need to force ROS to a particular one. "

Problem solved. Thanks for your quick support.

Daniel.

Hello again,

Thanks for the quick answers and comments. I will provide more information to each of them:

tfoote, I am indeed running the roscore separately as you suggest. Your guess could have explained perfectly what we are experiencing, but it must be something else. Thanks a lot.

Dimitar Simeonov, sorry I didn't clarify it but I meant messages on topics.
bhaskara, we have this behaviour in pretty much all our nodes with different source code combinations. Unfortunately I don't have access to the source code today, so I will post it tomorrow. Thanks.

Lorenz, yes, my nodes mainly run on different nodes. All the network setup seems correct to my but I am actually not setting the ROS_IP (I thought it was enough to set ROS_MASTER_UI). I will definitely try and report here. Thanks.

Hello,

We have many ROS nodes doing a fairly standard use of the publisher/subscriber mechanism as explained in the documentation. It is clear from ROS documentation that both the publishers and the subscribers can be started at any order and ROS will connect them.

In our case, we only receive messages in the subscriber if the publisher was launched first. And even if we do so, restarting the publisher will lead to the subscriber not receiving messages any more unless we also restart the subscriber.

As far as I understand from ROS documentation, this is unexpected. Where could I start for to troubleshoot this problem?

Thanks in advanced.