Cannot View Kinect Data on Fuerte
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 opennilaunch 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 imageview imageview image:=/camera/rgb/imagecolor; 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 opennilaunch openni.launch
XYZ@ubuntu:~$ roslaunch opennilaunch 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/depthregistered/rectifydepth/interpolation
* /camera/disparitydepth/maxrange
* /camera/disparitydepth/minrange
* /camera/disparitydepthregistered/max_range
* /camera/disparitydepthregistered/min_range
* /camera/driver/depthcamerainfo_url
* /camera/driver/depthframeid
* /camera/driver/depth_registration
* /camera/driver/device_id
* /camera/driver/rgbcamerainfo_url
* /camera/driver/rgbframeid
* /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)
/
camerabaselink (tf/statictransformpublisher)
camerabaselink1 (tf/statictransformpublisher)
camerabaselink2 (tf/statictransformpublisher)
camerabaselink3 (tf/statictransformpublisher)
cameranodeletmanager (nodelet/nodelet)
/camera/
disparity_depth (nodelet/nodelet)
disparitydepthregistered (nodelet/nodelet)
driver (nodelet/nodelet)
pointsxyzrgbdepth_rgb (nodelet/nodelet)
registerdepthrgb (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'",) inignored
process[master]: started with pid [4791]
ROSMASTERURI=http://localhost:11311
setting /run_id to 51b1b762-5a8b-11e2-adf5-e8e0b78c5661
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[rosout-1]: started with pid [4804]
started core service [/rosout]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[cameranodeletmanager-2]: started with pid [4816]
[ INFO] [1357756520.727453287]: Initializing nodelet with 4 worker threads.
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/driver-3]: started with pid [4845]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/rgb/debayer-4]: started with pid [4868]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/rgb/rectify_mono-5]: started with pid [4890]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/rgb/rectify_color-6]: started with pid [4921]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/ir/rectify_ir-7]: started with pid [4976]
xception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/depth/rectify_depth-8]: started with pid [5061]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/depth/metric_rect-9]: started with pid [5083]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/depth/metric-10]: started with pid [5141]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/depth/points-11]: started with pid [5198]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/registerdepthrgb-12]: started with pid [5248]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/depthregistered/rectifydepth-13]: started with pid [5316]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/depthregistered/metricrect-14]: started with pid [5385]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/depth_registered/metric-15]: started with pid [5425]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/pointsxyzrgbdepth_rgb-16]: started with pid [5472]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/disparity_depth-17]: started with pid [5533]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camera/disparitydepthregistered-18]: started with pid [5560]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camerabaselink-19]: started with pid [5589]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camerabaselink1-20]: started with pid [5649]
[ERROR] [1357756521.921194801]: Tried to advertise a service that is already advertised in this node [/camera/depthregistered/imagerectraw/compressedDepth/setparameters]
[ERROR] [1357756521.927395642]: Tried to advertise a service that is already advertised in this node [/camera/depthregistered/imagerectraw/compressed/setparameters]
[ERROR] [1357756521.932908761]: Tried to advertise a service that is already advertised in this node [/camera/depthregistered/imagerectraw/theora/setparameters]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camerabaselink2-21]: started with pid [5702]
Exception AttributeError: AttributeError("'DummyThread' object has no attribute 'Thread__block'",) inignored
process[camerabaselink3-22]: started with pid [5753]
[ INFO] [1357756522.882365480]: Number devices connected: 1
[ INFO] [1357756522.882700148]: 1. device on bus 003:06 is a Xbox NUI Camera (2ae) from Microsoft (45e) with serial id 'A00364A07870048A'
[ INFO] [1357756522.885294286]: Searching for device with index = 1
[ INFO] [1357756522.948003340]: Opened 'Xbox NUI Camera' on bus 3:6 with serial number 'A00364A07870048A'
[ INFO] [1357756523.020022711]: rgbframeid = '/camerargboptical_frame'
[ INFO] [1357756523.020249629]: depthframeid = '/cameradepthoptical_frame'
[ WARN] [1357756523.033610925]: Camera calibration file /home/mehrdad/.ros/camerainfo/rgbA00364A07870048A.yaml not found.
[ WARN] [1357756523.033788502]: Using default parameters for RGB camera calibration.
[ WARN] [1357756523.034028761]: Camera calibration file /home/mehrdad/.ros/camerainfo/depthA00364A07870048A.yaml not found.
[ WARN] [1357756523.035953428]: Using default parameters for IR camera calibration.
Asked by Merdad on 2013-01-08 12:19:06 UTC
Comments
When you run "roslaunch openni_launch openni.launch", does it find the kinect? Could you post the console output from that command?
Asked by jbinney on 2013-01-08 13:26:12 UTC
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.
Asked by georgebrindeiro on 2013-01-08 18:47:09 UTC
Thanks for the fast response. I posted the console output.
Asked by Merdad on 2013-01-09 08:18:03 UTC
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.
Asked by Merdad on 2013-01-09 08:19:52 UTC
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?
Asked by georgebrindeiro on 2013-01-09 15:48:35 UTC
@Merdad: Try checking if you have updated openni libraries. See http://answers.ros.org/question/51865/how-to-get-the-topics-data-from-kinect/
Asked by piyushk on 2013-01-10 00:40:50 UTC
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
Asked by Merdad on 2013-01-10 10:34:04 UTC
Could it be a hardware problem? I am working on a Toshiba Ultrabook with 3rd gen. i7 and HD4000 graphics.
Asked by Merdad on 2013-01-10 10:36:19 UTC
Unlikely a hardware problem, but you shouldn't rule it out: if you can, install ROS Electric on a PC with an older Ubuntu version to check.
Asked by georgebrindeiro on 2013-01-10 16:31:52 UTC
Have you checked out the verified answer to this question? It helped me when I had issues in ROS Fuerte+Ubuntu 12.04 64-bit: http://answers.ros.org/question/33622/openni_launch-not-working-in-fuerte-ubuntu-precise-1204/
Asked by georgebrindeiro on 2013-01-10 16:32:33 UTC
@georgebrindeiro The new openni packages should take care of the problem mentioned in thread you mentioned. @merdad My last recommendation would be to try the libfreenect system package, as well as add the output of lsusb and dmesg to your original question.
Asked by piyushk on 2013-01-10 20:48:20 UTC
Maybe this question could help: http://answers.ros.org/question/51865/how-to-get-the-topics-data-from-kinect/
Asked by Fabian Saccilotto on 2013-01-11 23:04:18 UTC
I switched to a workstation instead of laptops and no more issues with viewing Kinect images. I guess hardware was the issue.
Asked by Merdad on 2013-01-23 17:34:50 UTC
@Merdad: This is a bit odd. I don't think I've seen hardware dependent problems with the Kinect apart from the USB 3.0 issue. It is good to know you have something working, Would you mind posting the output of dmesg right after plugging in the Kinect in your laptop?
Asked by piyushk on 2013-01-23 18:46:50 UTC
Sure. I'll do that on Friday since I don't have access to that computer until then.
Asked by Merdad on 2013-01-23 19:27:00 UTC
@Merdad: Did u get it to work finally. I am having the same issue and still couldn't figure out the issue. http://answers.ros.org/question/57412/cant-see-kinect-data/
Asked by preetham.hegde on 2013-04-02 03:46:46 UTC