Ask Your Question
0

RGBDSLAM v2 on Kinect v2: No devices connected, waiting for devices to be connected

asked 2016-05-18 21:53:59 -0600

Mr. Kro gravatar image

I'm trying to run RGBDSLAM v2 with Kinect v2.

After sucessfully building, roslaunch rgbdslam openni+rgbdslam.launch resulted in the program running correctly, but there are no images coming from the Kinect v2. On the error output, it says:

process[rgbdslam-26]: started with pid [7843]
Initializing Node...
[ INFO] [1463623928.121529730]: Connected to roscore
[ INFO] [1463623928.405880762]: Using ORB keypoint detector.
[ INFO] [1463623928.405991250]: Using gridded keypoint detector with 3x3 cells, keeping 900 keypoints in total.
[ INFO] [1463623928.406055834]: Using adjusted keypoint detector with 5 maximum iterations, keeping the number of keypoints between 67 and 100
[ INFO] [1463623928.444573891]: Listening to /camera/rgb/image_color and /camera/depth_registered/sw_registered/image_rect_raw
[ INFO] [1463623931.311227274]: No devices connected.... waiting for devices to be connected

The last line repeated as the program stays running.

Seems like although test programs that come with Kinect drivers have recognized the Kinect v2 correctly, the program RGBDSLAM hasn't yet.

Protonect or NiViewer2 run OK and output RGB images and depth images, although it's left-right mirrored, and NiViewer2's output screen's lower half is black. However NiViewer doesn't recognize Kinect and outputs:

~$ NiViewer
One or more of the following nodes could not be enumerated:

Device: PrimeSense/SensorKinect/5.1.2.1: The device is not connected!
Device: PrimeSense/SensorV2/5.1.6.6: The device is not connected!
Device: PrimeSense/SensorV2/5.1.0.41: The device is not connected!
Device: PrimeSense/SensorKinect/5.1.2.1: The device is not connected!
Device: PrimeSense/SensorV2/5.1.6.6: The device is not connected!
Device: PrimeSense/SensorV2/5.1.0.41: The device is not connected!
Device: PrimeSense/SensorKinect/5.1.2.1: The device is not connected!
Device: PrimeSense/SensorV2/5.1.6.6: The device is not connected!
Device: PrimeSense/SensorV2/5.1.0.41: The device is not connected!

Press any key to continue . . .

lsusb outputs 3 Microsoft Corp. at the 3 USB ports corresponding to the USB slot Kinect v2 is plugged in.

I have tested with the patch avin2 ( https://github.com/avin2/SensorKinect ) but that didn't make RGBDSLAM v2 recognize the Kinect v2 (maybe that caused multiple identical lines in the NiViewer output above).

I want to ask how I can solve or can get to know mor about this error? Why is NiViewer2 and Protonect uses the Kinect v2 correctly but RGBDSLAM doesn't?

edit retag flag offensive close merge delete

3 Answers

Sort by ยป oldest newest most voted
3

answered 2016-05-19 04:57:13 -0600

Your problem is not really related to RGBDSLAM. You can not use roslaunch rgbdslam openni+rgbdslam.launch because this is for Kinect V1.

Your first step muss be: Your Kinect V2 muss run with ROS. You can find enough information in this FAQ and there: https://github.com/code-iai/iai_kinect2

Then you can create a modified launch file, see my post: http://answers.ros.org/question/23041...

edit flag offensive delete link more

Comments

Worked like a charm! Thank you very much.

Mr. Kro gravatar imageMr. Kro ( 2016-05-25 14:43:55 -0600 )edit
1

answered 2016-05-25 14:50:54 -0600

Mr. Kro gravatar image

Thanks to @MicaelKorn I could get the RGBDSLAM work on the Kinect v2. Just to summarize:

Steps to run RGBDSLAM with a Kinect One (Kinect v2)

  1. Install RGBDSLAM v2 indigo on ROS indigo https://github.com/felixendres/rgbdsl...
  2. Install libfreenect2 and iai_kinect2 https://github.com/OpenKinect/libfree... and https://github.com/code-iai/iai_kinect2
  3. Create a file named rgbdslam_kinect2.launch with contents like below.
  4. Run roslaunch rgbdslam rgbdslam_kinect2.launch and rosrun kinect2_bridge kinect2_bridge.launch from different Terminal windows

Now the RGBDSLAM GUI should appear and does its work.

rgbdslam_kinect2.launch: <launch> <node pkg="rgbdslam" type="rgbdslam" name="rgbdslam" cwd="node" required="true" output="screen">

<param name="config/topic_image_depth"             value="/kinect2/qhd/image_depth_rect"/>

<param name="config/topic_points"                  value=""/> <!--if empty, poincloud will be reconstructed from image and depth -->

<!-- These are the default values of some important parameters -->
<param name="config/feature_extractor_type"        value="SIFTGPU"/><!-- also available: SIFT, SIFTGPU, SURF, SURF128 (extended SURF), ORB. -->
<param name="config/feature_detector_type"         value="SIFTGPU"/><!-- also available: SIFT, SURF, GFTT (good features to track), ORB. -->
<param name="config/detector_grid_resolution"      value="3"/><!-- detect on a 3x3 grid (to spread ORB keypoints and parallelize SIFT and SURF) -->

<param name="config/optimizer_skip_step"           value="15"/><!-- optimize only every n-th frame -->
<param name="config/cloud_creation_skip_step"      value="2"/><!-- subsample the images' pixels (in both, width and height), when creating the cloud (and therefore reduce memory consumption) -->

<param name="config/backend_solver"                value="csparse"/><!-- pcg is faster and good for continuous online optimization, cholmod and csparse are better for offline optimization (without good initial guess)-->

<param name="config/pose_relative_to"              value="first"/><!-- optimize only a subset of the graph: "largest_loop" = Everything from the earliest matched frame to the current one. Use "first" to optimize the full graph, "inaffected" to optimize only the frames that were matched (not those inbetween for loops) -->

<param name="config/maximum_depth"           value="2"/>
<param name="config/subscriber_queue_size"         value="20"/>

<param name="config/min_sampled_candidates"        value="30"/><!-- Frame-to-frame comparisons to random frames (big loop closures) -->
<param name="config/predecessor_candidates"        value="20"/><!-- Frame-to-frame comparisons to sequential frames-->
<param name="config/neighbor_candidates"           value="20"/><!-- Frame-to-frame comparisons to graph neighbor frames-->
<param name="config/ransac_iterations"             value="140"/>

<param name="config/g2o_transformation_refinement"           value="1"/>
<param name="config/icp_method"           value="gicp"/>  <!-- icp, gicp ... -->

<!--
<param name="config/max_rotation_degree"           value="20"/>
<param name="config/max_translation_meter"           value="0.5"/>

<param name="config/min_matches"           value="30"/>   

<param name="config/min_translation_meter"           value="0.05"/>
<param name="config/min_rotation_degree"           value="3"/>
<param name="config/g2o_transformation_refinement"           value="2"/>
<param name="config/min_rotation_degree"           value="10"/>

<param name="config/matcher_type"         value="SIFTGPU"/>
 -->
</node>
</launch>
edit flag offensive delete link more
0

answered 2017-06-09 06:52:01 -0600

yalan gravatar image

hi i have tried with kinect 2 (ubuntu 14.04 -indigo )according to this tutorial :: http://answers.ros.org/question/23465... its very slow ! i need know whether there are some problems ? or should be like this? and i have these messages after running ::

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2016-05-18 21:53:59 -0600

Seen: 5,506 times

Last updated: May 25 '16