Ask Your Question

freenect on ARM

asked 2013-08-25 18:33:51 -0500

aswin gravatar image

updated 2016-10-24 08:35:14 -0500

ngrennan gravatar image

Hi all, I am able to run the freenect_stack on my x86 13.04 Hydro without any problems. However, I dont get any data when running on my beaglebone black 13.04 Hydro. Following is the output:

Number devices connected: 1
1. device on bus 000:00 is a Xbox NUI Camera (2ae) from Microsoft (45e) with serial id 'A00363A02841103A'
Searching for device with index = 1
Starting a 3s RGB and Depth stream flush.
Opened 'Xbox NUI Camera' on bus 0:0 with serial number 'A00363A02841103A'
rgb_frame_id = '/camera_rgb_optical_frame' 
depth_frame_id = '/camera_depth_optical_frame' 
Camera calibration file /home/hope/.ros/camera_info/rgb_A00363A02841103A.yaml not found.
Using default parameters for RGB camera calibration.
Camera calibration file /home/hope/.ros/camera_info/depth_A00363A02841103A.yaml not found.
Using default parameters for IR camera calibration.
Stopping device RGB and Depth stream flush.
Device timed out. Flushing device.
Starting a 3s RGB and Depth stream flush.
Stopping device RGB and Depth stream flush.
Device timed out. Flushing device.

...and this repeats

I installed the stack using sudo apt-get install ros-hydro-freenect-stack.

Any suggestions welcome.

edit retag flag offensive close merge delete


Hey there, I too am working on getting kinect working on beaglebone black. I just installed ros hydro and freenect stack but my kinect is not connecting when the freenect.launch is run.With lsusb i can see that all the three(cam,motor,audio) are visible.Could you help me out?

balakumar-s gravatar image balakumar-s  ( 2013-09-16 07:47:04 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2013-09-17 11:30:05 -0500

ahendrix gravatar image

updated 2014-10-31 18:49:16 -0500

I played around with this a bit, both with a Kinect and with an Asus Xtion Pro Live, and I wasn't able to get either to work.

The Kinect appeared to have problems enumerating properly on the USB bus, and tended to cause the kernel on my Beaglebone Black to crash or lock up.

The Asus seemed to enumerate OK, but isn't supported by libfreenect, and I didn't have time to try a modified driver with it.


I've since gotten the Kinect to work with the freenect drivers on one of my other ARM boards, and I've heard other users have had good luck using the OpenNI2 drivers with the Asus Xtion.

edit flag offensive delete link more


I recently tried openni and freenect without success on a Radxa Rock board. though lsusb sees the Kinect, no data is getting published. The openni roslaunch gives a USB device not supported! message. I am thinking this a Radxa kernel module issue.

DrBot gravatar image DrBot  ( 2014-10-31 18:29:02 -0500 )edit

ROS's libfreenect drivers do NOT work: they are defective and crash the Kinect. Your error report (output) is exactly what you get with those defective "drivers". The only always working drivers are Avin2

ROS_Portland_State_University_Robot gravatar image ROS_Portland_State_University_Robot  ( 2014-12-14 00:15:26 -0500 )edit

I've had no trouble with the libfreenect drivers, and no trouble with the USB ports on any of my many ASUS boards. Please try to stay on-topic and be constructive with your criticism.

ahendrix gravatar image ahendrix  ( 2014-12-14 02:59:30 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools



Asked: 2013-08-25 18:33:51 -0500

Seen: 1,872 times

Last updated: Oct 31 '14