Souldier's profile - activity

I know a couple of days ago I read a question where another user was having issues with 13.04 (http://answers.ros.org/question/62467/publisher-sleeping-forever/) -- Obviously, this won't help you in any way other than to let you know that others are experiencing problems..

+1 for more detail

Similar questions/answers exist - see here, here.

Unless you add your workspace to the package path in your ~/.bashrc file, each time you open a new terminal you will need to source your workspace (see this tutorial).

To set your workspace permanently, open your .bashrc file in a text editor, for example -- gedit ~/.bashrc -- and add

export ROS_PACKAGE_PATH=/your/path/to/workspace:$ROS_PACKAGE_PATH

at the bottom of your file. Obviously, make sure you change "/your/path/to/workspace" to your exact workspace path..

It may be because you are calling rospy.spin() in your Main loop. According to the documentation on rospy.spin() (see here and search for "spin") it "Blocks until ROS node is shutdown." - which could explain why you are only seeing the first pass through the talker method..

Not sure if this will help you or not but I figured I might as well add...

I was having this same problem a couple of weeks back and here is what I learned:

1. Make sure that you have a package called "external_sensor_interface" that contains a msg directory with your "data_logger_measurement" msg defined there. This package should be on your ROS_PACKAGE_PATH (see http://ros.org/wiki/ROS/EnvironmentVariables). Changing it should look something like...

   echo ROS_PACKAGE_PATH="/path/to/your/project/":$ROS_PACKAGE_PATH

2. Build your messages - You need to edit your CMakeLists file (and you indicated that you already did this..) and rebuild your project. NOTE: This is where I was having problems - specifically with catkin. I switched my entire project to use rosbuild and I had smooth sailing from that point forward.

If all that worked correctly, you should be able to do,

rosmsg show data_logger_measurement

which will display your message details...From there you should be good to go.

I was exploring the rosbridge package and noticed a package called roswww. Is that just the package that rosbridge uses for server logic (connection management)?

I haven't been able to find any documentation on roswww..

Can someone point me somewhere for more information, or explain what roswww is / what role it plays in the rosbridge package?

Thanks, -James

Ok. No harm no foul. Looks like I just needed to close out the rosbridge terminal window and restart it. I guess it was having trouble "seeing" the new project..

Hey everyone.

I walked through the tutorials and created a custom message called "Person.msg" under a project named "testing". I can see the message and its definition using "rosmsg show". I can also publish data using the message definition and with a subscriber see the data being published.

So with that said, here is my issue. I have a rosbridge server running and have had success connecting, advertising, publishing, and subscribing to preexisting message types (ex: std_msgs/String). However, when I try to simply subscribe to my custom message type, I get an error displayed in rosbridge which states:

"subscribe: Unable to load the manifest for package testing. Caused by: testing"

My manifest file in the testing package is as follows

<package>
  <description brief="testing">

        testing
  </description>
  <author>James</author>
  <license>BSD</license>
  <review status="unreviewed" notes=""/>
  <url>"couldnt post the url..."</url>
  <depend package="std_msgs"/>
  <depend package="rospy"/>
  <depend package="roscpp"/> </package>

Anyone have any suggestions on what I am doing wrong? Thanks!