openni_launch not working on ROS Groovy/Hydro in Ubuntu 12.04 32-bit [closed]

asked 2013-08-30 11:49:35 -0600

updated 2016-10-24 09:07:34 -0600

ngrennan gravatar image

Hi everyone,

I have recently upgraded my ROS distros in my Pioneer 3 robots to ROS Hydro and I can't get my Kinects to work using openni_launch. Could anyone help me figure out why?

I am guessing it has something to do with 32-bit Ubuntu 12.04, since everything works fine on my desktop computer. Also it definitely has something to do with these two ROS distros (or the version of OpenNI that is pulled with them), since I can still run openni_launch just fine in ROS Fuerte. That, of course, rules out any hardware issues.

Below I copy the output I get when things crash, though the errors messages are not in themselves terribly informative. If you need any specific logs or tests let me know... Thanks in advance!

EDIT1: This issue might be related to the problems I am facing.

EDIT2: This problem might be hardware specific. I am using the Versalogic Cobra EBX-12 computer that shipped with our Pioneer 3 robots and apparently it does not support SSE3 instructions. Unfortunately, the OpenNI binaries ship with that compilation flag set, as stated in the Adept MobileRobots wiki. I will try compiling OpenNI from source and see if that works.

aramis@aramis:~$ roslaunch openni_launch openni.launch 
... logging to /home/aramis/.ros/log/6e2cdf32-11bc-11e3-9dce-00026f50d4b3/roslaunch-aramis-12391.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 <a href="http://aramis:60433/">http://aramis:60433/</a>


 * /camera/camera_nodelet_manager/num_worker_threads
 * /camera/depth_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

    camera_nodelet_manager (nodelet/nodelet)
    debayer (nodelet/nodelet)
    depth_metric (nodelet/nodelet)
    depth_metric_rect (nodelet/nodelet)
    depth_points (nodelet/nodelet)
    depth_rectify_depth (nodelet/nodelet)
    disparity_depth (nodelet/nodelet)
    disparity_depth_registered (nodelet/nodelet)
    driver (nodelet/nodelet)
    points_xyzrgb_depth_rgb (nodelet/nodelet)
    rectify_color (nodelet/nodelet)
    rectify_ir (nodelet/nodelet)
    rectify_mono (nodelet/nodelet)
    register_depth_rgb (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)

auto-starting new master
process[master]: started with pid [12405]

setting /run_id to 6e2cdf32-11bc-11e3-9dce-00026f50d4b3
process[rosout-1]: started with pid [12418]
started core service [/rosout]
process[camera/camera_nodelet_manager-2]: started with pid [12421]
process[camera/driver-3]: started with pid [12422]
process[camera/debayer-4]: started with pid [12423]
process[camera/rectify_mono-5]: started with pid [12424]
process[camera/rectify_color-6]: started with pid [12425]
[ INFO] [1377898677.209749508]: Initializing nodelet with 4 worker threads.
process[camera/rectify_ir-7]: started with pid [12527]
process[camera/depth_rectify_depth-8]: started with pid [12541]
process[camera/depth_metric_rect-9]: started with pid [12555]
process[camera/depth_metric-10]: started with pid [12569]
process[camera/depth_points-11]: started with pid [12584]
process[camera/register_depth_rgb-12]: started with pid [12598]
process[camera/points_xyzrgb_depth_rgb-13]: started with pid [12599]
process[camera/disparity_depth-14]: started with pid [12626]
process[camera/disparity_depth_registered-15]: started with pid [12640]
[FATAL] [1377898678.954258670]: Service call failed!
[FATAL] [1377898678.954927374]: Service call failed!
[FATAL] [1377898678.955324070]: Service call failed ...
edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by tfoote
close date 2016-08-08 01:40:47.396966