Cannot View Kinect Data on Fuerte [closed]

asked 2013-01-08 11:19:06 -0500

Merdad gravatar image

updated 2016-10-24 08:34:19 -0500

ngrennan gravatar image

I am trying to use the RGBDSLAM package for my project. I got everything to build successfully according to the instructions on the wiki page after a few attempts. I can launch openni using roslaunch openni_launch openni.launch but, when I try running rgbdslam using rosrun rgbdslam rgbdslam I can`t see any image (depth or rgb).
I tried viewing the kinect data using rviz but, again, no luck. I followed the instructions on the rviz quick start tutorial page but pointclouds2 gives me a warning and says that nothing is being published to the topic.
I also tried rosrun image_view image_view image:=/camera/rgb/image_color; still no image.
The interesting thing is that the red lights in the depth sensor on the Kinect turns on when I try viewing the depth image...but no image!

Any thoughts on why this is happening and how to fix it? Thanks


EDIT: Here is the console output when I run roslaunch openni_launch openni.launch


XYZ@ubuntu:~$ roslaunch openni_launch openni.launch
... logging to /home/mehrdad/.ros/log/51b1b762-5a8b-11e2-adf5-e8e0b78c5661/roslaunch-ubuntu-4775.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://ubuntu:47290/

SUMMARY
========

PARAMETERS
* /camera/depth/rectify_depth/interpolation
* /camera/depth_registered/rectify_depth/interpolation
* /camera/disparity_depth/max_range
* /camera/disparity_depth/min_range
* /camera/disparity_depth_registered/max_range
* /camera/disparity_depth_registered/min_range
* /camera/driver/depth_camera_info_url
* /camera/driver/depth_frame_id
* /camera/driver/depth_registration
* /camera/driver/device_id
* /camera/driver/rgb_camera_info_url
* /camera/driver/rgb_frame_id
* /rosdistro
* /rosversion

NODES
/camera/depth/
metric (nodelet/nodelet)
metric_rect (nodelet/nodelet)
points (nodelet/nodelet)
rectify_depth (nodelet/nodelet)
/camera/rgb/
debayer (nodelet/nodelet)
rectify_color (nodelet/nodelet)
rectify_mono (nodelet/nodelet)
/
camera_base_link (tf/static_transform_publisher)
camera_base_link1 (tf/static_transform_publisher)
camera_base_link2 (tf/static_transform_publisher)
camera_base_link3 (tf/static_transform_publisher)
camera_nodelet_manager (nodelet/nodelet)
/camera/
disparity_depth (nodelet/nodelet)
disparity_depth_registered (nodelet/nodelet)
driver (nodelet/nodelet)
points_xyzrgb_depth_rgb (nodelet/nodelet)
register_depth_rgb (nodelet/nodelet)
/camera/ir/
rectify_ir (nodelet/nodelet)
/camera/depth_registered/
metric (nodelet/nodelet)
metric_rect (nodelet/nodelet)
rectify_depth (nodelet/nodelet)

auto-starting new master
Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading'="" from="" '="" usr="" lib="" python2.7="" threading.pyc'=""> ignored
process[master]: started with pid [4791]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 51b1b762-5a8b-11e2-adf5-e8e0b78c5661
Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading'="" from="" '="" usr="" lib="" python2.7="" threading.pyc'=""> ignored
process[rosout-1]: started with pid [4804]
started core service [/rosout]
Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading'="" from="" '="" usr="" lib="" python2.7="" threading.pyc'=""> ignored
process[camera_nodelet_manager-2]: started with pid [4816]
[ INFO] [1357756520.727453287]: Initializing nodelet with 4 worker threads.
Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading'="" from="" '="" usr="" lib="" python2.7="" threading.pyc'=""> ignored
process[camera/driver-3]: started with pid [4845]
Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading'="" from="" '="" usr="" lib="" python2.7="" threading.pyc'=""> ignored
process[camera/rgb/debayer-4]: started with pid [4868]
Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading'="" from="" '="" usr="" lib="" python2.7="" threading.pyc'=""> ignored
process[camera ...









































































(more)
edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by tfoote
close date 2015-09-28 01:16:05.581129

Comments

2

When you run "roslaunch openni_launch openni.launch", does it find the kinect? Could you post the console output from that command?

jbinney gravatar imagejbinney ( 2013-01-08 12:26:12 -0500 )edit

Are you using USB 3.0? Have you searched through answers to similar problems? I had trouble with openni in fuerte, but found all my answers just by searching for older questions.

georgebrindeiro gravatar imagegeorgebrindeiro ( 2013-01-08 17:47:09 -0500 )edit

Thanks for the fast response. I posted the console output.

Merdad gravatar imageMerdad ( 2013-01-09 07:18:03 -0500 )edit

Regarding USB 3.0, I read that there are some issues with it. That's why I'm using USB 2.0 :). I have been going through the old questions, but haven't found a solution yet. I am going to search a bit more.

Merdad gravatar imageMerdad ( 2013-01-09 07:19:52 -0500 )edit

Your output seems OK, but very similar to what I got when connecting to USB 3.0: the hardware is found but data is nowhere to be seen. Maybe you have too many things connected on that USB bus? Are you using a USB hub by any chance?

georgebrindeiro gravatar imagegeorgebrindeiro ( 2013-01-09 14:48:35 -0500 )edit
1

@Merdad: Try checking if you have updated openni libraries. See http://answers.ros.org/question/51865/how-to-get-the-topics-data-from-kinect/

piyushk gravatar imagepiyushk ( 2013-01-09 23:40:50 -0500 )edit

Tried everything that was suggested...even double checked to make sure my laptop ports are USB 2.0. Still no image. @georgebrindeiro: I am not using a USB hub wither. even disconnected my mouse to make sure the only thing connected is the Kinect

Merdad gravatar imageMerdad ( 2013-01-10 09:34:04 -0500 )edit

Could it be a hardware problem? I am working on a Toshiba Ultrabook with 3rd gen. i7 and HD4000 graphics.

Merdad gravatar imageMerdad ( 2013-01-10 09:36:19 -0500 )edit