ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
1

No devices connected... Waiting for devices to be connected

asked 2014-10-27 12:36:29 -0600

Kongaloosh gravatar image

updated 2014-11-02 07:27:45 -0600

Hi,

When I start 3dsensor.launch I get:

[ INFO] [1414430559.252574176]: No devices connected.... waiting for devices to be connected

When I rosrun openni_camera openni_node by itself I get the same error.

I've trawled rosanswers looking for a solution, but nothing's worked yet. : C lsusb lists the kinect; I've followed the suggestions here, and the suggestions here, and the suggestions here, and the suggestions here, and here to no avail.

This is being run on a turtlebot2, and both the turtlebot and the workstation are on 14.04 trusty and indigo igloo. The kinect is plugged into the usb 2.0 port.

lsusb yields:

Bus 002 Device 004: ID 0bda:5605 Realtek Semiconductor Corp. 
Bus 002 Device 009: ID 045e:02ae Microsoft Corp. Xbox NUI Camera
Bus 002 Device 008: ID 045e:02ad Microsoft Corp. Xbox NUI Audio
Bus 002 Device 007: ID 045e:02c2 Microsoft Corp. 
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 03eb:883e Atmel Corp. 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Turtlebot specs are: Ubuntu 14.04 Trusty Memory 1.8 G Processor Intel Celeron @ 1.50Ghz Graphics intel ivybridge mobile OS type 64 bit

I'm at a loss. does anyone have suggestions?

I'm not entirely certain if it's related, but when I start up my minimal launch I get this:

ROS_MASTER_URI=http://172.20.11.86:11311
core service [/rosout] found
process[robot_state_publisher-1]: started with pid [12734]
process[diagnostic_aggregator-2]: started with pid [12760]
process[mobile_base_nodelet_manager-3]: started with pid [12835]
process[mobile_base-4]: started with pid [12854]
process[cmd_vel_mux-5]: started with pid [12976]
process[bumper2pointcloud-6]: started with pid [13040]
process[turtlebot_laptop_battery-7]: started with pid [13081]
process[capability_server-8]: started with pid [13098]
process[app_manager-9]: started with pid [13105]
process[master-10]: started with pid [13145]
process[interactions-11]: started with pid [13187]
process[zeroconf/zeroconf-12]: started with pid [13232]
[ INFO] [1414430339.909748537]: Zeroconf: service successfully established [turtlebot][_ros-master._tcp][11311]
/opt/ros/indigo/lib/python2.7/dist-packages/bondpy/bondpy.py:114: SyntaxWarning: The publisher should be created with an explicit keyword argument 'queue_size'. Please see http://wiki.ros.org/rospy/Overview/Publishers%20and%20Subscribers for more information.
  self.pub = rospy.Publisher(self.topic, Status)
/opt/ros/indigo/lib/python2.7/dist-packages/bondpy/bondpy.py:114: SyntaxWarning: The publisher should be created with an explicit keyword argument 'queue_size'. Please see http://wiki.ros.org/rospy/Overview/Publishers%20and%20Subscribers for more information.
  self.pub = rospy.Publisher(self.topic, Status)
[WARN] [WallTime: 1414430344.195425] Rapp Manager : No preferred rapp for 'turtlebot_rapps ...
(more)
edit retag flag offensive close merge delete

Comments

1

What do you get from lsusb? and how did you start kinect? what's your pc spec?

jihoonl gravatar image jihoonl  ( 2014-10-27 18:46:11 -0600 )edit
  • I've updated the question with the contents of lsusb.

  • The kinect is listed there, as it should. I started the kinect by making sure everything is connected. All the lights are green.

  • Which computer do you want the specs for, the workstation or the turtlebot?

Kongaloosh gravatar image Kongaloosh  ( 2014-10-28 11:35:20 -0600 )edit

turtlebot's spec would be helpful

jihoonl gravatar image jihoonl  ( 2014-10-29 21:27:31 -0600 )edit

3 Answers

Sort by ยป oldest newest most voted
0

answered 2014-11-02 07:44:44 -0600

Kongaloosh gravatar image

updated 2014-11-02 08:30:36 -0600

It turned out the solution was to get an openni patch. This resolved the connection error.

However, I now have a minor issue with RVIZ.

From the 3d Launch I get:

[ WARN] [1414934636.270421799]: Camera calibration file /home/turtlebot/.ros/camera_info/depth_0000000000000000.yaml not found. 
[ WARN] [1414934636.270594235]: Using default parameters for IR camera calibration.

rostopic echo camera/depth_registered/image_raw produces numbers, and I get a point-cloud visualization.

edit flag offensive delete link more

Comments

i've the same problem but im getting the openni drivers from apt-get install ros-indigo-openni-camera and ..-launch and executing roslaunch openni_launch openni.launch. What do you mean with "getting an openni patch"? Are you installing those drivers from git before indigo's openni packages?

lokus gravatar image lokus  ( 2014-11-26 21:26:38 -0600 )edit

@lokus, That's where you should be getting them. As far as I know, openni actually doesn't support the Kinect. The patch which I linked to fixes this. I didn't have to remove and re-install anything, I just downloaded it alongside my existing stack.

Kongaloosh gravatar image Kongaloosh  ( 2014-11-29 03:58:53 -0600 )edit

hey can you plz tell me how can i download and use "https://github.com/avin2/SensorKinect" or openni patch" on ros? i am new to linux and ros and i am facing the same above mentioned problem for kinect.

kaygudo gravatar image kaygudo  ( 2015-12-16 12:30:42 -0600 )edit
2

answered 2015-04-21 05:23:45 -0600

Kei Okada gravatar image

disabling USB3.0 on BIOS should work on openni_launch,

http://answers.ros.org/question/11558... http://answers.ros.org/question/20283...

edit flag offensive delete link more

Comments

lspci -nn | grep USB | cut -d '[' -f3 | cut -d ']' -f1 | xargs -I@ setpci -H1 -d @ d0.l=0

from: https://www.systutorials.com/how-to-f...

benwex93 gravatar image benwex93  ( 2020-06-20 18:00:15 -0600 )edit
0

answered 2015-02-11 12:57:11 -0600

130s gravatar image

updated 2015-02-11 12:59:19 -0600

Experienced a very similar (or the same) issue. I've worked it around by roslaunch freenect_launch freenect.launch. This may not work on different environment (see a Turtlebot issue for more info) though.

dpkg -p ros-indigo-openni-launch ros-indigo-freenect-launch | grep Vers
Version: 1.9.5-0trusty-20141231-0013-+0000
Version: 0.4.0-0trusty-20150131-0944-+0000
edit flag offensive delete link more

Question Tools

3 followers

Stats

Asked: 2014-10-27 12:36:29 -0600

Seen: 12,874 times

Last updated: Apr 21 '15