Closed pirobot closed 9 years ago
How about if you add depth_registration:=true?
Running
$ roslaunch openni2_launch openni2.launch depth_registration:=true
does not fix the problem.
Did this previously work (under hydro or whatnot?)
Also -- have you tried from source? There is an issue with tf2/indigo/tf_prefix that causes certain things to have tf errors (due to "/" at beginning of tf frame) -- I've recently fixed that, but not yet released new debs.
Good question. I thought it worked under Hydro a long time ago but my guess is I was using openni_launch and not openni2_launch. Now when I try it with the latest Hydro debs, openni_launch cannot see the device and openni2_launch sees the device but I get the same null result on /camera/rgb/image_color as I do under Indigo.
So I guess my expectations were incorrect. What started all this is that the Indigo freenect_launch package does publish image data on /camera/rgb/image_color when using a Kinect...
Closed by original posted as expectations were incorrect.
When using an Asus Xtion Pro and the latest Indigio Debian packages under Ubuntu 14.04, after running
$ roslaunch openni2_launch openni2.launch
there is no image data on the topic /camera/rgb/image_color as expected but the color image is on the topic /camera/rgb/image_raw.