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

Problem with openni2_camera, Primesense not detected.

asked 2014-09-01 08:17:43 -0500

zeinab gravatar image

updated 2018-01-23 01:31:58 -0500

130s gravatar image

Hi,

I am trying to access the rgdb information of a Primesense sensor. I have ros-hydro-openni2-* installed using sudo apt-get and it previously worked just fine with the following command: rosrun openni2_camera openni2_camera_node but now when I run this command this is what I get:

~device_id is not set! Using first device.
[ INFO] [1409576381.725333109]: No matching device found.... waiting for devices. Reason: std::string openni2_wrapper::OpenNI2Driver::resolveDeviceURI(const string&) @ /tmp/buildd/ros-hydro-openni2-camera-0.1.3-0precise-20140720-0503/src/openni2_driver.cpp @ 623 : Invalid device number 1, there are 0 devices connected.
[ INFO] [1409576384.725593448]: No matching device found.... waiting for devices. Reason: std::string openni2_wrapper::OpenNI2Driver::resolveDeviceURI(const string&) @ /tmp/buildd/ros-hydro-openni2-camera-0.1.3-0precise-20140720-0503/src/openni2_driver.cpp @ 623 : Invalid device number 1, there are 0 devices connected.

I used to be able to access the rgbd information and the topics using exactly the same command about a month ago. I dont know if there has been an update which has led to this. I have ubuntu 12.04 and ROS hydro installed.

I get the same error whether the Primesense sensor is plugged in or not and lsusb doesnt detect this device. I have tried setting the UsbInterface=0 in /etc/openni2/PS1080 as suggested in one of the posts but it didn't help. I would really appreciate your help on this.

Any suggestions are welcome, thanks in advance!


Update 20140903

So this is the output

$ lsusb
    Bus 001 Device 003: ID 058f:9540 Alcor Micro Corp. 
    Bus 001 Device 002: ID 8087:8000 Intel Corp. 
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 002: ID 17ef:1010 Lenovo 
    Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 002 Device 005: ID 5986:026a Acer, Inc 
    Bus 002 Device 004: ID 138a:0017 Validity Sensors, Inc. 
    Bus 002 Device 003: ID 1199:a001 Sierra Wireless, Inc. 
    Bus 002 Device 007: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
    Bus 002 Device 006: ID 17ef:100f Lenovo 
    Bus 002 Device 002: ID 17ef:1010 Lenovo 
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

// now with the Primesense connected

$ lsusb
Bus 001 Device 003: ID 058f:9540 Alcor Micro Corp. 
Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 17ef:1010 Lenovo 
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 5986:026a Acer, Inc 
Bus 002 Device 004: ID 138a:0017 Validity Sensors, Inc. 
Bus 002 Device 003: ID 1199:a001 Sierra Wireless, Inc. 
Bus 002 Device 007: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 002 Device 006: ID 17ef:100f Lenovo 
Bus 002 Device 002: ID 17ef:1010 Lenovo 
Bus 002 Device 008: ID 1d27:0609 ASUS 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I tried another ... (more)

edit retag flag offensive close merge delete

Comments

It might be that the PrimeSense sensor died, it is sad, but it happened to me before. If you have spare, try another sensor.

Martin Peris gravatar image Martin Peris  ( 2014-09-01 20:53:09 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
2

answered 2014-09-01 12:41:19 -0500

ahendrix gravatar image

If your sensor doesn't appear in lsusb, it means that the OS isn't detecting it properly. This is usually a hardware problem.

You may want to try a different USB port or a different USB cable, if you can. If you're using a USB extension cable, try plugging the sensor in directly.

It may also be useful to review the kernel log ( dmesg ) to see if the device is partially detected, and is having signal integrity or other problems.

edit flag offensive delete link more

Comments

Thanks a lot for your reply. I installed OpenNI2 and was able to run an example which accessed the depth information and printed them. However lsusb still does not show the Primesense sensor. I think there must be a problem with ros-hydro-openni2 or openni2_camera since it is working outside ROS.

zeinab gravatar image zeinab  ( 2014-09-02 05:16:00 -0500 )edit

The lsusb database doesn't include names for some of the primesense devices. I suspect your device may be showing up in lsusb without a label. Can you add your lsusb output to your question?

ahendrix gravatar image ahendrix  ( 2014-09-02 13:40:26 -0500 )edit

You are right. I post the what I get with and without the sensor being connected to the computer in the post below.

zeinab gravatar image zeinab  ( 2014-09-03 05:38:06 -0500 )edit

Question Tools

Stats

Asked: 2014-09-01 08:17:43 -0500

Seen: 2,144 times

Last updated: Jan 23 '18