Revision history [back]

In short, it doesn't look promising. Here's the stack:

http://wiki.ros.org/freenect_stack

The stack installs two packages:

http://wiki.ros.org/freenect_camera

http://wiki.ros.org/freenect_launch

At the bottom of freenect_camera:

http://wiki.ros.org/freenect_camera#Migration_guide

Other OpenNI devices

There are a couple of reasons why other devices using the OpenNI standard (namely the Primesense PSDK, Asus Xtion Pro and Pro Live) are not currently supported:

libfreenect hardcodes information about the Kinect in a way that makes it difficult to gain access to different types of OpenNI devices using the same code. It might be easy to patch libfreenect to use these other devices, generate separate libraries for each device, and make multiple binaries of the driver linking against each library separately.

There might be other approaches but Kinect seems to have more support and documentation in the community.

In short, it doesn't look promising. Here's the stack:

http://wiki.ros.org/freenect_stack

The stack installs two packages:

http://wiki.ros.org/freenect_camera

http://wiki.ros.org/freenect_launch

At the bottom of freenect_camera:

http://wiki.ros.org/freenect_camera#Migration_guide

Other OpenNI devices

There are a couple of reasons why other devices using the OpenNI standard (namely the Primesense PSDK, Asus Xtion Pro and Pro Live) are not currently supported:

libfreenect hardcodes information about the Kinect in a way that makes it difficult to gain access to different types of OpenNI devices using the same code. It might be easy to patch libfreenect to use these other devices, generate separate libraries for each device, and make multiple binaries of the driver linking against each library separately.

There might In simplest terms, each device has to be other approaches but individually reverse-engineered to gain access to full features. The Kinect seems to have more is relatively cheap for the sensor's ability and it has seen widespread use so there's a lot of support and documentation in the community.

In short, it doesn't look promising. Here's the stack:

http://wiki.ros.org/freenect_stack

The stack installs two packages:

http://wiki.ros.org/freenect_camera

http://wiki.ros.org/freenect_launch

At the bottom of In freenect_camera:

Overview

This package provides a ROS interface to the Microsoft Kinect using the libfreenect library from OpenKinect. Other devices using the OpenNI standard are currently not supported. Please see the section on other OpenNI devices for more information.

Other OpenNI devices

There are a couple of reasons why other devices using the OpenNI standard (namely the Primesense PSDK, Asus Xtion Pro and Pro Live) are not currently supported:

libfreenect hardcodes information about the Kinect in a way that makes it difficult to gain access to different types of OpenNI devices using the same code. It might be easy to patch libfreenect to use these other devices, generate separate libraries for each device, and make multiple binaries of the driver linking against each library separately.

In simplest terms, each device has to be individually reverse-engineered to gain access to full features. The Kinect is relatively cheap for the sensor's ability and it has seen widespread use so there's a lot of support for it.

In short, it doesn't look promising. Here's the stack:

http://wiki.ros.org/freenect_stack

The stack installs two packages:

http://wiki.ros.org/freenect_camera

http://wiki.ros.org/freenect_launch

In freenect_camera:

Overview

This package provides a ROS interface to the Microsoft Kinect using the libfreenect library from OpenKinect. Other devices using the OpenNI standard are currently not supported. Please see the section on other OpenNI devices for more information.

Other OpenNI devices

There are a couple of reasons why other devices using the OpenNI standard (namely the Primesense PSDK, Asus Xtion Pro and Pro Live) are not currently supported:

libfreenect hardcodes information about the Kinect in a way that makes it difficult to gain access to different types of OpenNI devices using the same code. It might be easy to patch libfreenect to use these other devices, generate separate libraries for each device, and make multiple binaries of the driver linking against each library separately.

In simplest terms, each device has to be individually reverse-engineered to gain access to full features. The Kinect is relatively cheap for the sensor's ability and it has seen widespread use so there's a lot of support for it.