Unable to detect kinect

[Harshad1]

Hi everyone,

I have been trying to read data from the kinect but I haven't been able to.

I am running x64 Fedora 16 and I have compiled and installed both OpenNi and avin2 according to the instructions.

(Do I have to install NITE even if I do not intend to do any skeleton-tracking etc work? I only want raw point cloud data)

Whenever I run, for example, the NiViewer example, I get:

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

My device (a kinect for windows) *is* however connected as seen by lsusb:

 

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 001 Device 003: ID 0c45:63e7 Microdia 

Bus 001 Device 014: ID 045e:02c2 Microsoft Corp. 

Bus 001 Device 016: ID 045e:02be Microsoft Corp. 

Bus 001 Device 017: ID 045e:02bf Microsoft Corp.

I have also confirmed that the hardware works by trying it with the kinect sdk samples on a windows machine.

Please help!

[Harshad1]

I've tried installing NITE (installed the ubuntu -x64 edition) and the running the demos in NITE.

Same result.

[Igor Barros Barbosa]

First step is to make sure you actually installed the libraries corrected.
I never tried for fedora, and I also don't know if it is officially supported by Openni. But you can see an example installation for Ubuntu and MInt here:

http://igorbarbosa.com/articles/how-to-install-kin-in-linux-mint-12-ubuntu/

If you actually compiled everything by yourself instead of using the binaries, you need to make sure to use the appropriated usb rules, and the appropriated version of avin2.

If you actually have all those things right, (I actually assume you have the correct installation) the problem might be:

You are using a USB 3.0

I haven't tried with the new OpenNI and its support for the WINDOWS KINECT. So that as far as I can orient you.





01001001011001110110111101110010
http://igorbarbosa.com

[Harshad1]

On Saturday, 19 May 2012 20:30:47 UTC-4, igorbb wrote:

I haven't tried with the new OpenNI and its support for the WINDOWS KINECT. So that as far as I can orient you.

01001001011001110110111101110010
http://igorbarbosa.com

I think that this might be the problem:

I finally tried looking at the usb rules and I found that the usb rules for avin2 and I found this:

#--avin mod--

# Kinect

SUBSYSTEM=="usb", ATTR{idProduct}=="02ae", ATTR{idVendor}=="045e", MODE:="0666", OWNER:="root", GROUP:="video"

SUBSYSTEM=="usb", ATTR{idProduct}=="02ad", ATTR{idVendor}=="045e", MODE:="0666", OWNER:="root", GROUP:="audio"

SUBSYSTEM=="usb", ATTR{idProduct}=="02b0", ATTR{idVendor}=="045e", MODE:="0666", OWNER:="root", GROUP:="video"

Note that the product ids are different from the product ids of my device (from lsusb):

Bus 001 Device 008: ID 045e:02c2 Microsoft Corp. 

Bus 001 Device 010: ID 045e:02be Microsoft Corp. 

Bus 001 Device 011: ID 045e:02bf Microsoft Corp. 

I tried changing the device id in the udev rule but that didn't work. Might this be a cause?

 

[Roee Shenberg]

Kinect for Windows != Kinect for Xbox - I modified SensorKinect to work with K4W at  https://github.com/shenberg/SensorKinect (older version, won't work with current OpenNI, only 1.5.2.23 or lower). Feel free to try that or wait a bit till the changes get integrated into mainline SensorKinect.

Roee

 

--
You received this message because you are subscribed to the Google Groups "OpenNI" group.

To view this discussion on the web visit https://groups.google.com/d/msg/openni-dev/-/veomh8T0mdsJ.

To post to this group, send email to openn...@googlegroups.com.
To unsubscribe from this group, send email to openni-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/openni-dev?hl=en.

[Harshad1]

Awesome! At least I know what's wrong now.

Could you possibly give us an eta on the integration / update?

I'm only asking in order to pick the best path for my project...

[avin]

Hi Harshad, I will add Kinect-4-Windows by the end of this week.

(I should have a K4W device in 2 days...)

avin.

[Harshad1]

Thank you! 

Let me know if there is any information or testing I can do to help.

[CyberQat]

Hi Avin,

I'm awaiting thids wityh baoted breath too as I have a K4W and OSX,
for whichapparently the only version of OpenNI is the latest.

I'll be happy to give you reports on how it works.

[avin]

Hi, I just wanted to update that I finally got a Kinect4Windows
sensor!

It's already working well (I only had to change about 5 lines in the
code to add support for it) and I will probably release a new
SensorKinect in a day or two.

avin.


On May 20, 6:21 am, Harshad1 <harshadsriniva...@gmail.com> wrote:

[Jeffrey Kesselman]

Cool.  Thanks so much!

JK

--
You received this message because you are subscribed to the Google Groups "OpenNI" group.

To post to this group, send email to openn...@googlegroups.com.
To unsubscribe from this group, send email to openni-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/openni-dev?hl=en.

--
It's always darkest just before you are eaten by a grue.

[Harshad1]

Awesome! I'm looking forward to trying your code.

Out of curiosity, did this involve changing more than the device id and perhaps a few registers?

[Roee Shenberg]

To the best of my understanding, one packet had its size change a bit and it uses iso mode and not bulk.

--

You received this message because you are subscribed to the Google Groups "OpenNI" group.

To view this discussion on the web visit https://groups.google.com/d/msg/openni-dev/-/XuEyKU1S0iYJ.

[Harshad1]

Hi Avin.

How's the updated sensorkinect coming along?

Is there anything I can do to help test it?

Harshad