Closed piyushk closed 11 years ago
Did some basic debugging of openni_camera and removed a redundant call for getting the device list. The launch script now works extremely reliably. Instructions for applying this patch are now present in the robot setup/upgrade script at http://z.cs.utexas.edu/users/piyushk/bwi_share/setup_robot.sh, and the patch is lcoated at http://cs.utexas.edu/~piyushk/bwi_share/openni_camera.patch
This is definitely not a permanent solution. I don't even know if this bug occurs for us because of all the USB 3.0 patching. Hopefully the new openni debs will reliable enough for us to revert back to using the standard openni launch stuff.
I am closing this issue for now. We'll open it again if the device becomes unstable again.
The segbot laptops have USB 3.0 only, which is not supported by the libfreenect based drivers (see https://github.com/piyushk/freenect_stack/issues/5). For the time being, the segbot code has reverted back to using patched openni ones.
The segbots currently run openni drivers after modifications suggested by the following threads: http://answers.ros.org/question/9179/kinect-and-usb-30/ http://answers.ros.org/question/33622/openni_launch-not-working-in-fuerte-ubuntu-precise-1204/
The driver is not extremely reliable and typically requires a reboot before relaunching it again.