mkt29's profile - activity

overview network karma followed questions activity

2013-12-01 05:08:45 -0500	received badge	● Famous Question (source)
2013-12-01 05:08:45 -0500	received badge	● Popular Question (source)
2013-12-01 05:08:45 -0500	received badge	● Notable Question (source)
2011-07-14 03:32:23 -0500	marked best answer	launch file ignoring a message Just a guess, but maybe you specified a different node name in the launch file than when calling ros::init in your subscriber node. If you use relative topic names, they will be in a namespace named according to your node name. `rostopic list` and `rostopic echo` might help, too. Start up everything and try to find out if your topic is present twice, in different namespaces (just call `rostopic list`). Then do a `rostopic info <topic>` to verify the node names that publish/subscribe to the topic. If my guess is correct, either change your nodes to use absolute node names or use topic remapping to fix the topic name or simply rename your node in the launch file.
2011-07-14 03:32:23 -0500	received badge	● Scholar (source)
2011-07-14 03:31:20 -0500	commented answer	launch file ignoring a message Yep, that was the problem. Thanks!
2011-07-14 03:31:07 -0500	received badge	● Supporter (source)
2011-07-13 08:55:07 -0500	commented answer	launch file ignoring a message Hm, didn't work for me.
2011-07-13 08:38:33 -0500	commented question	launch file ignoring a message The message is published by a program outside of the launch file and it's being published constantly so I don't think that's the problem.
2011-07-13 07:17:57 -0500	asked a question	launch file ignoring a message I'm using a launch file to start a driver node and another node at the same time. Meanwhile, I'm running another file, which is supposed to publish a message to a topic, to which the non-driver node in the launch file is subscribed. When I don't use the launch file and run the driver separately, everything works fine. The message is published and read correctly. However, when I use the launch file, the message appears not to be read.