OpenNI & Kinect error "no devices connected.... waiting for devices to be connected"

Dear: LMR

Just to let you know I am trying to use a kinect sensor with openni and slam but am running into a few problems. I keep running into this error "No devices connected.... waiting for devices to be connected" inside my terminal. I've tried using freenect_launch, I've tried installing KinectSensor-unstable repair files, and I've tried different methods like using openni2 and nothing is different. Here's what my terminal shows when I put in "roslaunch openni_launch openni.launch" into the terminal after pressing enter.

Can I please have help? The kinect LED is green so I know it is a software error. Thank you.

From: Noah

 

 

 



SUMMARY
========

PARAMETERS
 * /camera/camera_nodelet_manager/num_worker_threads: 4
 * /camera/depth_rectify_depth/interpolation: 0
 * /camera/depth_registered_rectify_depth/interpolation: 0
 * /camera/disparity_depth/max_range: 4.0
 * /camera/disparity_depth/min_range: 0.5
 * /camera/disparity_registered_hw/max_range: 4.0
 * /camera/disparity_registered_hw/min_range: 0.5
 * /camera/disparity_registered_sw/max_range: 4.0
 * /camera/disparity_registered_sw/min_range: 0.5
 * /camera/driver/depth_camera_info_url:
 * /camera/driver/depth_frame_id: camera_depth_opti...
 * /camera/driver/depth_registration: False
 * /camera/driver/device_id: #1
 * /camera/driver/rgb_camera_info_url:
 * /camera/driver/rgb_frame_id: camera_rgb_optica...
 * /rosdistro: indigo
 * /rosversion: 1.11.13

NODES
  /camera/
    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)
    depth_registered_rectify_depth (nodelet/nodelet)
    disparity_depth (nodelet/nodelet)
    disparity_registered_hw (nodelet/nodelet)
    disparity_registered_sw (nodelet/nodelet)
    driver (nodelet/nodelet)
    points_xyzrgb_hw_registered (nodelet/nodelet)
    points_xyzrgb_sw_registered (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 [14758]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 1cc71a1e-a68d-11e5-bf90-20689de92e57
process[rosout-1]: started with pid [14771]
started core service [/rosout]
process[camera/camera_nodelet_manager-2]: started with pid [14788]
process[camera/driver-3]: started with pid [14789]
[ INFO] [1450556071.820304724]: Initializing nodelet with 4 worker threads.
process[camera/debayer-4]: started with pid [14825]
process[camera/rectify_mono-5]: started with pid [14839]
[ INFO] [1450556071.973861741]: No devices connected.... waiting for devices to be connected
process[camera/rectify_color-6]: started with pid [14854]
process[camera/rectify_ir-7]: started with pid [14868]
process[camera/depth_rectify_depth-8]: started with pid [14882]
process[camera/depth_metric_rect-9]: started with pid [14896]
process[camera/depth_metric-10]: started with pid [14910]
process[camera/depth_points-11]: started with pid [14924]
process[camera/register_depth_rgb-12]: started with pid [14938]
process[camera/points_xyzrgb_sw_registered-13]: started with pid [14952]
process[camera/depth_registered_rectify_depth-14]: started with pid [14966]
process[camera/points_xyzrgb_hw_registered-15]: started with pid [14980]
process[camera/disparity_depth-16]: started with pid [14994]
process[camera/disparity_registered_sw-17]: started with pid [15008]
process[camera/disparity_registered_hw-18]: started with pid [15022]
process[camera_base_link-19]: started with pid [15036]
process[camera_base_link1-20]: started with pid [15047]
process[camera_base_link2-21]: started with pid [15058]
process[camera_base_link3-22]: started with pid [15069]
[ INFO] [1450556074.974405851]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556077.974793600]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556080.975113616]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556083.975570711]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556086.976015178]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556089.976441028]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556092.976976921]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556095.977320351]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556098.977766096]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556101.978260762]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556104.978783114]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556107.979311220]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556110.979739562]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556113.980134267]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556116.980501872]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556119.980858909]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556122.981204083]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556125.981547046]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556128.982110643]: No devices connected.... waiting for devices to be connected
[ INFO] [1450556131.982493349]: No devices connected.... waiting for devices to be connected

Kinect Launch

Hi Noah

Openni launch causes problems for most people I use freenect instead works well

 

 

Peter

That causes different problems for me.

Dear: Peter

Just to let you know if I type “roslaunch freenect_launch freenect.launch” I get strange warning and eventually an error. The error says "Stopping device RGB and Depth stream flush"Here is what it says in the terminal below.

From: Noah

 

… logging to /home/noah/.ros/log/62169188-a69e-11e5-8588-20689de92e57/roslaunch-noah-HP-Pavilion-g7-Notebook-PC-17601.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.

SUMMARY
========

PARAMETERS
 * /camera/camera_nodelet_manager/num_worker_threads: 4
 * /camera/depth_rectify_depth/interpolation: 0
 * /camera/depth_registered_rectify_depth/interpolation: 0
 * /camera/disparity_depth/max_range: 4.0
 * /camera/disparity_depth/min_range: 0.5
 * /camera/disparity_registered_hw/max_range: 4.0
 * /camera/disparity_registered_hw/min_range: 0.5
 * /camera/disparity_registered_sw/max_range: 4.0
 * /camera/disparity_registered_sw/min_range: 0.5
 * /camera/driver/data_skip: 0
 * /camera/driver/debug: False
 * /camera/driver/depth_camera_info_url:
 * /camera/driver/depth_frame_id: camera_depth_opti…
 * /camera/driver/depth_registration: False
 * /camera/driver/device_id: #1
 * /camera/driver/diagnostics_max_frequency: 30.0
 * /camera/driver/diagnostics_min_frequency: 30.0
 * /camera/driver/diagnostics_tolerance: 0.05
 * /camera/driver/diagnostics_window_time: 5.0
 * /camera/driver/enable_depth_diagnostics: False
 * /camera/driver/enable_ir_diagnostics: False
 * /camera/driver/enable_rgb_diagnostics: False
 * /camera/driver/rgb_camera_info_url:
 * /camera/driver/rgb_frame_id: camera_rgb_optica…
 * /rosdistro: indigo
 * /rosversion: 1.11.13

NODES
  /camera/
    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)
    depth_registered_rectify_depth (nodelet/nodelet)
    disparity_depth (nodelet/nodelet)
    disparity_registered_hw (nodelet/nodelet)
    disparity_registered_sw (nodelet/nodelet)
    driver (nodelet/nodelet)
    points_xyzrgb_hw_registered (nodelet/nodelet)
    points_xyzrgb_sw_registered (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 [17613]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 62169188-a69e-11e5-8588-20689de92e57
process[rosout-1]: started with pid [17626]
started core service [/rosout]
process[camera/camera_nodelet_manager-2]: started with pid [17643]
process[camera/driver-3]: started with pid [17644]
[ INFO] [1450563489.562419333]: Initializing nodelet with 4 worker threads.
process[camera/debayer-4]: started with pid [17680]
process[camera/rectify_mono-5]: started with pid [17694]
process[camera/rectify_color-6]: started with pid [17711]
process[camera/rectify_ir-7]: started with pid [17725]
process[camera/depth_rectify_depth-8]: started with pid [17739]
process[camera/depth_metric_rect-9]: started with pid [17753]
process[camera/depth_metric-10]: started with pid [17775]
process[camera/depth_points-11]: started with pid [17789]
process[camera/register_depth_rgb-12]: started with pid [17817]
process[camera/points_xyzrgb_sw_registered-13]: started with pid [17834]
[ INFO] [1450563490.283925490]: Number devices connected: 1
[ INFO] [1450563490.284191240]: 1. device on bus 000:00 is a Xbox NUI Camera (2ae) from Microsoft (45e) with serial id ‘A00365A04468136A’
[ INFO] [1450563490.286756007]: Searching for device with index = 1
process[camera/depth_registered_rectify_depth-14]: started with pid [17852]
[ INFO] [1450563490.360444923]: Starting a 3s RGB and Depth stream flush.
[ INFO] [1450563490.362811940]: Opened ‘Xbox NUI Camera’ on bus 0:0 with serial number 'A00365A04468136A’
process[camera/points_xyzrgb_hw_registered-15]: started with pid [17894]
process[camera/disparity_depth-16]: started with pid [17916]
process[camera/disparity_registered_sw-17]: started with pid [17933]
process[camera/disparity_registered_hw-18]: started with pid [17964]
[ WARN] [1450563490.633966896]: Could not find any compatible depth output mode for 1. Falling back to default depth output mode 1.
process[camera_base_link-19]: started with pid [18005]
[ INFO] [1450563490.712988278]: rgb_frame_id = ‘camera_rgb_optical_frame’
[ INFO] [1450563490.713074571]: depth_frame_id = ‘camera_depth_optical_frame’
process[camera_base_link1-20]: started with pid [18047]
[ WARN] [1450563490.801776913]: Camera calibration file /home/noah/.ros/camera_info/rgb_A00365A04468136A.yaml not found.
[ WARN] [1450563490.801872580]: Using default parameters for RGB camera calibration.
[ WARN] [1450563490.801995993]: Camera calibration file /home/noah/.ros/camera_info/depth_A00365A04468136A.yaml not found.
[ WARN] [1450563490.802065445]: Using default parameters for IR camera calibration.
process[camera_base_link2-21]: started with pid [18079]
process[camera_base_link3-22]: started with pid [18091]
[ INFO] [1450563493.361685020]: Stopping device RGB and Depth stream flush.

Stream flush

Hi Noah

stream flush means nothing is subcribed to the kinect topics if you open rviz and conect pointcloud2 to the kinect topic(depth registered points set depth_registration to true with rqt) then the warning will go away

every thing else looks normal

 

Peter

Dear: PeterHow do you

Dear: Peter

How do you subscribe to the Kinect topics? You said that if I open rviz and connect to pointcloud to the Kinect it will go away. I don’t know how to do that. Thank you though.

From: Noah

Rviz

on the left side pane in rviz click add go down to pointcloud2 and add it

expand pointcloud2 and select the topic the pull down list will show the topics

set the frame to one from the camera ei camera link

have a read of the rviz tutorial on the ROS wiki

Rviz is one of the main tools in ROS you will be using a lot

Hey I can understand mostly what to do.

Dear: Peter

Just to let you know I got rviz to run. I added a pointcloud2 and I did expand it but one problem. There are two topics under pointcloud2 and I don’t know how to set the frame to one from teh camera ei camera link. I noticed there are a few errors in the GlobalStatus tab I am not sure if that is important. It says “Fixed Frame [map] does not exist”. What should I do? Thank you.

 

From: Noah

Rviz

Hi Noah

Change the fixed frame to what ever you like just click the field and it will show the options 

when you launch freenect you have some static frames like base_like or camera_link try one of those

when you have set the frame and the topic in point cloud2 you should see the image 

you can also add a camera  set its topic to camera/rgb/image_raw or somthing like that again it will show you the valid options

 

Peter

It works!!! Thank you so much!!!

Dear: Peter

Thank you so much I can’t tell you how happy I am. It works!!!

From: Noah

freenect or openni usb3

 

hello

do you know that the Kinect does not work with USB3 !

 

Mo

Yeah I knew that.
Dear: mlavie1
Yeah I knew that. I wasn’t using usb 3 I was using 2. Why do you say that and I did fix the issue.
From: Noah

Kinect camera issue using Robotino

Hello,

I am new to robot programming and I am having similar problem with Kinect connection usin openni or freenect. I am using robotino.

When I connect the kinect to my laptop, it works fine. But when I connect the kinect with Robotino and do the “roslaunch freenect_launch freenect.launch” … I get the message:

[ INFO] [1465902396.516936708]: No devices connected… waiting for devices to be connected

-----------------------------------------------------

What can i do now? Can anyone please suggest me…

This is to inform that both laptop and robotino configuration are the same(same version of ubuntu linux, ROS indigo, API2, AVIN2 etc…)

Other nodes are connected, like roslaunch robotino_node robotino_node.launch hostname:=172.26.1.1 is perfectly working.

Teleop node is also working fine.

Please suggest me to fix the issue :slight_smile: