[Documentation] [TitleIndex] [WordIndex

  Show EOL distros: 

freenect_stack: freenect_camera | freenect_launch | libfreenect

Package Summary

Contains a set of launch files for freenect_camera to produce rectified, registered and/or disparity images. Also used to produce point clouds and registered point clouds. Based on the openni_launch package.

freenect_stack

Package Summary

Launch files for freenect_camera to produce rectified, registered or disparity images. Also produce point clouds and registered point clouds. Based on the openni_launch package.

Package Summary

Launch files for freenect_camera to produce rectified, registered or disparity images. Also produce point clouds and registered point clouds. Based on the openni_launch package.

Package Summary

Launch files for freenect_camera to produce rectified, registered or disparity images. Also produce point clouds and registered point clouds. Based on the openni_launch package.

Package Summary

Launch files for freenect_camera to produce rectified, registered or disparity images. Also produce point clouds and registered point clouds. Based on the openni_launch package.

New in Fuerte

Overview

This package contains launch files for using a Microsoft Kinect using the libfreenect library. This folder replicates the API offered by openni_launch in an effort to maintain maximum compatibility with the OpenNI driver. Differences are mentioned below.

To use this package, please refer to openni_launch and rgbd_launch documentation. The migration guide to/from the OpenNI driver is documented here.

The main launch script can be run using the following command:

roslaunch freenect_launch freenect.launch

Modifications from openni_launch

freenect_launch contains a few modifications from openni_launch apart from running the libfreenect based driver. These are documented below.

freenect_launch vs openni_launch

Additional Launch Files

There are a few additional launch files in freenect_launch that demonstrate running a different constellation of nodelets. This is useful for launching the minimum set of required processing nodelets, as well as avoid unnecessary warnings during launch. For example:


2019-07-20 12:42