Tim C's profile - activity

Hello! If I understand you in right way, you should open next file:

your_project_dir/manifest.xml

and add something like this:

<depend package="mrpt_common"/>

Also, you can create new package with dependencies, e.g.

roscreate-pkg yourProjectName mrpt_common mrpt_slam mrpt_hwdrivers

After package name you should list all dependecies. Hope this will be useful.

Sorry this is probably a stupid questions...

I've downloaded and successfully built the mrpt_common, mrpt_slam, and mrpt_hwdrivers packages. I assume this now allows me to reference some, if not all, MRPT functionality in a ros package.

However, when I add a reference to a mrpt class and add the include it get errors.

So now I'm wondering whether doing rosmake --rosdep-install <mypkg> doesn't resolve things.

Can someone help me out? My goal is to be able to reference and use any of the many useful MRPT classes from within a ROS package.

Thanks

Has anyone implemented and tested a C++ version of a Chr-UM6 (9-dof) IMU?

There is a Python driver but I don't know the language and don't have time to learn. My goal is to use it in the Mobile Robot Programming Toolkit and later ROS.

Thanks

I'm trying to rosmake pcl_tutorials and receive the following error:

tim@Linux-laptop-1:~/ros_workspace/pcl_tutorials$ rosmake --rosdep-install pcl_tutorials [ rosmake ] Packages requested are: ['pcl_tutorials']
[ rosmake ] Logging to directory/home/tim/.ros/rosmake/rosmake_output-20110914-153143
[ rosmake ] Expanded args ['pcl_tutorials'] to: ['pcl_tutorials']
[ rosmake ] Generating Install Script using rosdep then executing. This may take a minute, you will be prompted for permissions. . .
Failed to find rosdep libtiff for package pcl_tutorials on OS:ubuntu version:natty [ rosmake ] rosdep install failed: Rosdep install failed
tim@Linux-laptop-1:~/ros_workspace/pcl_tutorials$

======

Any suggestions?

I did also tried to add/update the libtiff using Synaptic pkg manager but no difference.

Thanks

Here is a launch file that should work:

<launch>
  <node pkg="hokuyo_node" type="hokuyo_node" name="hokuyo_node"/>

  <node pkg="laser_scan_matcher" type="laser_scan_matcher_node"
    name="laser_scan_matcher_node" output="screen">
    <param name="use_alpha_beta" value="true"/>
    <param name="max_iterations" value="10"/>
  </node>

  <node pkg="tf" type="static_transform_publisher" name="base_link_to_laser"
    args="0.0 0.0 0.0 0.0 0.0 0.0 /base_link /laser 40" />

</launch>

The first node launches the hokuyo_node driver, the second one launches the laser_scan_matcher, and the third one provides the neccessary tf from the base_link to the laser frame.

The parameters in the laser_scan_matcher aren't required, but tweaking them will probably improve performance. Check the documentation to see what the parameter options are and to find out what works best for you.

EDIT

The clock parameter is documented here.

Hi, I have a hokuyo Lidar compatible with hokuyo_node package and can run it fine. And, I've also run the default laser_scan_matcher demo executed from roslaunch.

My goal is to see the same demo but using live laser scan messages. I'm new to ROS so I'm sure I'm missing something.

I've taken the default demo.launch file and cut out the rosbag part and started a hokuyo_node instead, but I don't appear to see anything the rvis. I've used rxgraph to compare the to and the only piece I don't understand is the purpose and necessity of the "clock" topic from rosbag to laser_scan_matcher. It's not mentioned in the scarce documentation.

Would someone please offer direction on how to substitude the laser scans from rosbag to a hokuyo_node.

Thanks