ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2016-10-17 00:13:57 -0500 | received badge | ● Famous Question (source) |
2016-02-18 06:23:24 -0500 | received badge | ● Famous Question (source) |
2015-11-13 04:19:05 -0500 | received badge | ● Famous Question (source) |
2015-07-24 04:47:11 -0500 | received badge | ● Notable Question (source) |
2015-07-24 04:47:11 -0500 | received badge | ● Popular Question (source) |
2015-02-20 14:21:54 -0500 | received badge | ● Notable Question (source) |
2015-02-20 02:51:31 -0500 | received badge | ● Popular Question (source) |
2014-11-25 13:07:00 -0500 | received badge | ● Editor (source) |
2014-11-25 13:06:06 -0500 | asked a question | rosjava custom messages: can compile and import, but not use as expected I am using rosindigo and rosjava. I created a rosjava_message package to create a custom foo.msg for use in my rosjava node. I followed the example in http://wiki.ros.org/rosjava/Tutorials... Ros recognizes my message:
I see it is built and foo.class looks reasonable. The generated cpp files look good too. I can import foo_msgs.foo in my publisher node and create a publisher:
Now I expect to be able to do myMessage.setIntVar(5), but that results in a compilation error. If I use java's inspection to print the methods available to myMessage, it's the same methods availabe if it was a std_msgs.String message! If I do rostopic echo /custom/topic, an exception results. I the rostopic echo expects my foo message type, but I think the std_msgs.String is being used and results in this exception:
Any pointers on how to proceed? I don't understand why the class I'm importing somehow isn't the right class(?). I only define foo.msg in one place. |
2014-11-18 16:26:48 -0500 | asked a question | rosbridge/rosjs communication problem (vs rostopic pub) Hello... It seems I am having a problem with websockets. I'm using ros indigo. I have a webpage using the ros javascript which creates a publisher for my topic and publishes messages when I press a button. It works! The message gets published. I have a node that listens for this topic and changes its behavior based on the message it gets. The problem is it doesn't always work. Sometimes, the node does not respond to my button press. The node is supposed to change its state based on the message in my topic. I verified that message is being published on my topic (with rostopic echo). However, if I use rostopic pub I can reach my node with the message, as expected. I think this means the problem lies with the rosbridge, but I'm not sure how to go further with debugging it. Also, the failure state is not easily reproduced. If/when it happens, I need to stop and restart ros in order to regain control via my button. There is no other way for the button to control the node. It seems to me this indicates the problem is with rosbridge. Any suggestions on how to debug further or what to look for? Has anyone else noticed this? |
2014-11-14 15:14:19 -0500 | commented question | Guaranteed message delivery Right now I am using the messages to pass sensor data collected from certain nodes to other nodes. It is very important that I don't miss data. All the nodes are running on a single physical machine. |
2014-11-11 11:54:22 -0500 | received badge | ● Notable Question (source) |
2014-11-10 05:01:56 -0500 | received badge | ● Popular Question (source) |
2014-11-09 19:58:55 -0500 | received badge | ● Student (source) |
2014-11-09 19:41:00 -0500 | asked a question | Guaranteed message delivery Hello, It seems ROS makes no guarantee of message delivery. I know some can be lost at the beginning (nodes haven't fully started up) but of course they can also be dropped later. It is the dropping messages later that I am concerned about. I have seen rosbags suggested at the way to get guaranteed message delivery (maybe minus the node start up situation, which I'm not worried about). It seems they are used for capturing/replaying messages and are not thread-safe. Has anyone used them for receiving messages in real-time? Is there another way to go? I know queue sizes/publishing rates are adjustable and this can minimize loss, but there are certain messages I can't afford to drop, even occassionally. And I am losing some. Thanks. |
2014-11-09 18:06:11 -0500 | received badge | ● Supporter (source) |