The openni kinect driver seems to be super flaky. I have issues with it locking up and not publishing any data, whereas the freenect driver is rock solid. It seems it's all down to the PrimeSense guys (or Willow Garage) to fix it.<div>
<br></div><div>Tom<br><br><div class="gmail_quote">2011/4/17 Björn Giesler <span dir="ltr"><<a href="mailto:bjoern@giesler.de">bjoern@giesler.de</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
One more info: kinect (the deprecated ROS driver) works.<br>
<br>
Regards,<br>
Björn<br>
<br>
Am 16.04.2011 um 20:57 schrieb Björn Giesler:<br>
<div><div></div><div class="h5"><br>
> Hi,<br>
><br>
> it took me a bit to get openni_camera compiled on my Arch Linux box. It compiles and runs now, but it doesn't find my Kinect:<br>
><br>
> -- SNIP --<br>
> [bjoern@toennchen ros]$ lsusb<br>
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>
> Bus 002 Device 017: ID 0409:005a NEC Corp. HighSpeed Hub<br>
> Bus 002 Device 018: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor<br>
> Bus 002 Device 019: ID 045e:02ad Microsoft Corp. Xbox NUI Audio<br>
> Bus 002 Device 020: ID 045e:02ae Microsoft Corp. Xbox NUI Camera<br>
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
> Bus 004 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)<br>
> -- SNIP --<br>
><br>
> ...so it's there, but<br>
><br>
> -- SNIP --<br>
> [bjoern@toennchen ros]$ roslaunch openni_camera openni_node.launch<br>
> ... logging to /home/bjoern/.ros/log/5b48de58-4fd5-11e0-9dd8-002163300bea/roslaunch-toennchen-4910.log<br>
> Checking log directory for disk usage. This may take awhile.<br>
> Press Ctrl-C to interrupt<br>
> Done checking log file disk usage. Usage is <1GB.<br>
><br>
> started roslaunch server <a href="http://toennchen:49952/" target="_blank">http://toennchen:49952/</a><br>
><br>
> SUMMARY<br>
> ========<br>
><br>
> PARAMETERS<br>
> * /rosdistro<br>
> * /openni_node1/use_indices<br>
> * /openni_node1/depth_registration<br>
> * /openni_node1/image_time_offset<br>
> * /openni_node1/depth_frame_id<br>
> * /openni_node1/depth_mode<br>
> * /openni_node1/debayering<br>
> * /rosversion<br>
> * /openni_node1/projector_depth_baseline<br>
> * /openni_node1/rgb_frame_id<br>
> * /openni_node1/depth_rgb_translation<br>
> * /openni_node1/depth_time_offset<br>
> * /openni_node1/image_mode<br>
> * /openni_node1/shift_offset<br>
> * /openni_node1/device_id<br>
> * /openni_node1/depth_rgb_rotation<br>
><br>
> NODES<br>
> /<br>
> openni_node1 (openni_camera/openni_node)<br>
> kinect_base_link (tf/static_transform_publisher)<br>
> kinect_base_link1 (tf/static_transform_publisher)<br>
> kinect_base_link2 (tf/static_transform_publisher)<br>
> kinect_base_link3 (tf/static_transform_publisher)<br>
><br>
> auto-starting new master<br>
> process[master]: started with pid [4923]<br>
> ROS_MASTER_URI=<a href="http://localhost:11311" target="_blank">http://localhost:11311</a><br>
><br>
> setting /run_id to 5b48de58-4fd5-11e0-9dd8-002163300bea<br>
> process[rosout-1]: started with pid [4936]<br>
> started core service [/rosout]<br>
> process[openni_node1-2]: started with pid [4948]<br>
> process[kinect_base_link-3]: started with pid [4949]<br>
> process[kinect_base_link1-4]: started with pid [4950]<br>
> process[kinect_base_link2-5]: started with pid [4962]<br>
> process[kinect_base_link3-6]: started with pid [4973]<br>
> [ INFO] [1300283861.936848748]: [/openni_node1] No devices connected.... waiting for devices to be connected<br>
> [ INFO] [1300283864.937603511]: [/openni_node1] No devices connected.... waiting for devices to be connected<br>
> [ INFO] [1300283867.938017792]: [/openni_node1] No devices connected.... waiting for devices to be connected<br>
> -- SNIP --<br>
><br>
> ...and there it stays. I haven't found anything about this on the web or on <a href="http://answers.ros.org" target="_blank">answers.ros.org</a>; seems it works for everyone out of the box. I've tried two different Kinects and several different USB ports on my machine. Can anyone please help me or offer some ideas on how to diagnose this?<br>
><br>
> Thank you very much in advance!<br>
><br>
> Björn<br>
> --<br>
> Björn Giesler<br>
> <a href="mailto:bjoern@giesler.de">bjoern@giesler.de</a><br>
> Verschlüssel Deine Emails -- oder schreibst Du Deine Briefe außen auf den Umschlag?<br>
> Meinen Schlüssel findest Du auf <a href="http://giesler.biz/~bjoern/downloads/bg.asc" target="_blank">http://giesler.biz/~bjoern/downloads/bg.asc</a> -- schick mir Deinen!<br>
> Mehr Informationen findest Du auf <a href="http://www.gnupg.org/index.de.html" target="_blank">http://www.gnupg.org/index.de.html</a><br>
><br>
> _______________________________________________<br>
> ros-users mailing list<br>
> <a href="mailto:ros-users@code.ros.org">ros-users@code.ros.org</a><br>
> <a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
><br>
<br>
--<br>
Björn Giesler<br>
<a href="mailto:bjoern@giesler.de">bjoern@giesler.de</a><br>
Verschlüssel Deine Emails -- oder schreibst Du Deine Briefe außen auf den Umschlag?<br>
Meinen Schlüssel findest Du auf <a href="http://giesler.biz/~bjoern/downloads/bg.asc" target="_blank">http://giesler.biz/~bjoern/downloads/bg.asc</a> -- schick mir Deinen!<br>
Mehr Informationen findest Du auf <a href="http://www.gnupg.org/index.de.html" target="_blank">http://www.gnupg.org/index.de.html</a><br>
<br>
_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org">ros-users@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
</div></div></blockquote></div><br></div>