Freenect_launch does not detect Kinect, BeagleBoard-xM, Ubuntu

Hi,

I'm trying to run the freenect_launch package on a BeagleBoard-xM (Rev C) running Ubuntu 13.04. The aim is to record a short rosbag of kinect data and store it, to be later transmitted for offboard processing.

The prebuilt demo image of Ubuntu was installed following the instructions on the elinux page for BeagleBoardUbuntu.

I installed ros-hydro-freenect-launch using apt-get.

roslaunch freenect_launch freenect.launch successfully launches roscore and starts the kinect-related processes, but does not detect the kinect. It repeatedly displays

No devices connected.... waiting for devices to be connected

I've tried blacklisting the gspca_kinect module, but to no avail.

lsusb shows that the Kinect is recognized:

Bus 001 Device 012: ID 045e:02ad Microsoft Corp. Xbox NUI Audio
Bus 001 Device 011: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor
Bus 001 Device 013: ID 045e:02ae Microsoft Corp. Xbox NUI Camera

I'd really appreciate if someone could help getting freenect to recognize the kinect, or suggest alternatives.

EDIT 1:

We are no longer facing this issue with the latest release of Ros-hydro for Ubuntu-ARM (the hydro/Installation/UbuntuARM page has been updated on 18th Jan 2014) with the namniart repositories. We have also switched over to a Pandaboard (Rev A3) for greater computing power, so we cannot say for sure that the issue has been resolved on the Beagleboard-xM.

After installing ros-hydro-freenect-stack on Ubuntu 13.04 (OMAP4 Desktop Image) on the Pandaboard, freenect.launch detects the Kinect and publishes topics successfully.

Asked by Gour on 2014-01-14 05:10:02 UTC

Comments

The last time I tried this, it didn't work.

Asked by ahendrix on 2014-01-20 12:21:24 UTC

Thank you for the response. Freenect-launch worked with the Kinect on a Pandaboard after the recent repository update.

Asked by Gour on 2014-01-21 02:48:58 UTC

Awesome! Can you post that as an answer? (Yes, you're allowed to answer your own question)

Asked by ahendrix on 2014-01-21 08:47:29 UTC

Answers

On Pandaboard Ubuntu 13.04, hydro freenect launch says:

process[camera/disparity_registered_sw-17]: started with pid [3840] [ INFO] [1390366533.711813148]: rgb_frame_id = '/camera_rgb_optical_frame' [ INFO] [1390366533.716695960]: depth_frame_id = '/camera_depth_optical_frame' process[camera/disparity_registered_hw-18]: started with pid [3884] [ WARN] [1390366533.933431800]: Camera calibration file /home/team751/.ros/camera_info/rgb_A00363914850112A.yaml not found. [ WARN] [1390366533.954244789]: Using default parameters for RGB camera calibration. [ WARN] [1390366533.959615882]: Camera calibration file /home/team751/.ros/camera_info/depth_A00363914850112A.yaml not found. [ WARN] [1390366533.960867103]: Using default parameters for IR camera calibration. process[camera_base_link-19]: started with pid [3902] process[camera_base_link1-20]: started with pid [3927] process[camera_base_link2-21]: started with pid [3948] process[camera_base_link3-22]: started with pid [3963] [ INFO] [1390366536.003347572]: Stopping device RGB and Depth stream flush.

rostopic list shows lots of topics, but echo shows they are all empty of data.

This is the same for openni launch.

I am guessing something to do with USB 3 vs 2? -or- bad calibration file?

Asked by DrBot on 2014-01-21 17:59:19 UTC

Comments

This is not an answer. Please ask it as a new question.

Asked by ahendrix on 2014-01-21 21:44:27 UTC