ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2014-11-24 05:35:13 -0500 | received badge | ● Notable Question (source) |
2014-11-24 05:35:13 -0500 | received badge | ● Famous Question (source) |
2013-07-28 23:01:53 -0500 | received badge | ● Popular Question (source) |
2013-07-24 21:49:06 -0500 | received badge | ● Organizer (source) |
2013-07-24 21:45:24 -0500 | asked a question | Different Outcome using rosservice call on two laptops running the same Node Hi folks, Been playing around with ROS for some time, but this is my first question on the forum. Let me know if the question needs more adjustments if it isn't clear. ##Introduction to Problem ## I'm currently playing around with this multi-hop communication protocol that runs on ROS called ros-rt-wmp (www.ros.org/wiki/ros-rt-wmp). I've followed all the instructions and have successfully set up the protocol on two separate laptops in the user space, each running their own ROS Masters. Here is some information on the laptops: Node R0: ROS Distro: Fuerte; OS Version: Ubuntu 12.04 LTS; Python Version: 2.7.3; GCC Version: 4.6.3 Node R1: ROS Distro: Fuerte; OS Version: Ubuntu 12.04 LTS; Python Version: 2.7.3; GCC Version: 4.6.3 I can successfully publish and receive messages on each laptop. ##Problem## The PROBLEM comes at the section on controlling the ros-rt-wmp node (www.ros.org/wiki/ros-rt-wmp#Controlling_the_ros_rt_wmp): From R1, I would like to remotely stop a topic called "/topicA" that is transmitting on R0. I use the following command on R1: The output was what I hoped to see: R1 was not receiving anymore data from /topicA running on R0 I tried to use the same remote call on the other laptop. In other words, from R0, I would like to remotely stop a topic called "/topicB" that is transmitting on R1. (note that /topicA and /topicB are essentially the same). I use the following command: However, the following error appears on R0: I can't figure out why this command can work on one laptop, but not the other, considering that they were both downloaded from the same source and ... (more) |