| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
I use two different laser scan on my Pioneer robot. The first is a Sick LMS100, the second a Sick TiM300. How can I integrate their scan data in a single ROS node?
In my launch file I call the two laser drivers, but in the main scan data overlap: in a cycle, I obtain the first laser scan data, in another cycle I obtain the second laser scan data and so on...
Thanks
I would say it completely depends on your system configuration. Normally, it should not be a problem when both lasers publish their data on the same topic since the LaserScan message contains a header with a frame_id and a time stamp. Of course, this requires a valid TF tree and the laser drivers to be configured to use a different frame id for each scanner. Amcl, for instance, supports several lasers on one topic.
By using topic remapping, you can configure your laser scanners to publish on different topics. Have a look at this question/answer for more information on that.
Finally, if you don't want to use the LaserScan message but a point cloud, you can use the laser_assembler node as @weiin suggests in his answer. However, this solution won't work for amcl or any other node that requires a LaserScan message.
On our robot, we use two Hokuyo lasers for amcl. Both laser drivers publish on separate topics and in the amcl node, we relay both topics to amcl's input topic using topic_tools' relay. That way, we can access the laser scans separately or, if needed, on one single topic.
Laser pipeline is what you need, in particular, the assembler.
We have created a special laser_tools node for this issue, have a look here https://github.com/iralabdisco/ira_la...
Asked: 2012-07-02 23:29:49 -0600
Seen: 5,465 times
Last updated: Mar 26 '16
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
