New "The device is not connected!" error

287 views
Skip to first unread message

Bit Felon

unread,
Mar 3, 2012, 3:22:58 PM3/3/12
to OpenNI
Hi all,

I've been developing an OS X application using OpenNI that was working
great a few days ago. I was interfacing with OSCeleton which uses
OpenNI, and decided to get rid of OSCeleton since it was an
unnecessary middle man to what I was working on and started playing
with OpenNI directly. Initially I was having issues so I also
attempted to get libfreenect working but no luck there so I
uninstalled it from my system (I was using homebrew so it was easy to
remove) and returned to OpenNI. The green indicator on the Kinect IS
flashing.

However, now OpenNI is not working and always returns this error:

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

Device: PrimeSense/SensorKinect/5.1.0.25: The device is not connected!
Device: PrimeSense/SensorV2/5.1.0.25: The device is not connected!
Device: PrimeSense/SensorKinect/5.1.0.25: The device is not connected!
Device: PrimeSense/SensorV2/5.1.0.25: The device is not connected!

My system is configured with the following installed:
Mac OS X 10.6.8 (Intel)
SensorKinect091-Bin-MacOSX-v5.1.0.25.tar.bz2
openni-bin-dev-macosx-v1.5.2.23.tar.bz2
nite-bin-macosx-v1.5.2.21.tar.bz2
sensor-bin-macosx-v5.1.0.41.tar.bz2

I've also tried installing older versions of some of these to match
avin's recent github posting saying "Updated codebase to the latest
OpenNI / Sensor version (1.5.2.7 / 5.1.0.25), so I also tried
installing to no avail:
nite-bin-macosx-v1.5.2.7.tar.bz2, openni-bin-dev-macosx-
v1.5.2.7.tar.bz2, sensor-bin-macosx-v5.1.0.25.tar.bz2

I've verified that the Kinect works fine by connecting it to my Xbox
and can still use it properly, see my image on the Xbox, use gestures
and the microphone.

I've used Apple's USB Prober to ensure the device is connected
properly to the USB bus, here is the output:
Full Speed device @ 11
(0xFA133200): .............................................
Composite device: "Xbox NUI Motor"
Port Information: 0x0019
Captive
External Device
Connected
Enabled
Device Descriptor
Descriptor Version Number: 0x0200
Device Class: 0 (Composite)
Device Subclass: 0
Device Protocol: 0
Device MaxPacketSize: 64
Device VendorID/ProductID: 0x045E/0x02B0 (Microsoft
Corporation)
Device Version Number: 0x0107
Number of Configurations: 1
Manufacturer String: 1 "Microsoft"
Product String: 2 "Xbox NUI Motor"
Serial Number String: 0 (none)
Configuration Descriptor
Length (and contents): 18
Raw Descriptor (hex) 0000: 09 02 12 00 01 01 00 C0 32
09 04 00 00 00 FF 00
Raw Descriptor (hex) 0010: 00 00
Number of Interfaces: 1
Configuration Value: 1
Attributes: 0xC0 (self-powered)
MaxPower: 100 ma
Interface #0 - Vendor-specific
Alternate Setting 0
Number of Endpoints 0
Interface Class: 255 (Vendor-specific)
Interface Subclass; 0 (Vendor-specific)
Interface Protocol: 0

I've power cycled the Kinect and my computer many times, tried
different USB ports, ensured the Kinect works on Xbox, tried
installing the binaries from scratch, compiled sources and tried
installing those binaries, and also tried installing Zigfu to use the
binaries included in that (which is what I used originally to get
everything working.)

I've also ensured I don't have random openni/libusb libs laying
around:
$ find /usr | egrep -i 'libusb|openni'
/usr/include/libusb-1.0
/usr/include/libusb-1.0/libusb.h
/usr/include/ni/XnOpenNI.h
/usr/lib/libOpenNI.dylib
/usr/lib/libOpenNI.jni.dylib
/usr/lib/libusb-1.0.0.dylib
/usr/lib/libusb-1.0.a
/usr/lib/libusb-1.0.dylib
/usr/lib/libusb-1.0.la
/usr/lib/libusb.a
/usr/lib/libusb.dylib
/usr/lib/libusb.la
/usr/local/Library/Formula/libusb-compat.rb
/usr/local/Library/Formula/libusb-freenect.rb
/usr/local/Library/Formula/libusb.rb
/usr/share/java/org.OpenNI.jar
$

NOTE: Everything *was* working a few days ago using the binaries
included in Zigfu. Even reinstalling from Zigfu has not fixed this
problem. Any ideas?

Thanks

Bit Felon

unread,
Mar 5, 2012, 12:14:20 AM3/5/12
to OpenNI
Hi all, still having this issue but I found something else interesting and would love to see if this correlates with other setups.

I've been reading how the Kinect was reverse engineered to see if that will help (http://www.ladyada.net/learn/diykinect/) and see that on OS X, when they run `system_profiler SPUSBDataType` it shows up three Xbox devices: "Xbox NUI Camera", "Xbox NUI Audio" and "Xbox NUI Motor".

However, when I run `system_profiler SPUSBDataType`, I only get "Xbox NUI Motor". Does anyone have any idea why this is? One thing to add is I have a Kinect with the proprietary USB-like dongle, not a true USB dongle, thus I'm using this adapter to connect it: http://www.amazon.com/dp/B004IXRXGY/

Can others on OS X please provide their `system_profiler SPUSBDataType` output for comparison?

Again, this was all working the other day with the same setup. Any ideas would be really helpful. Here is the only portion `system_profiler SPUSBDataType` output that contains the word "Xbox":

                Hub:

                  Product ID: 0x005a
                  Vendor ID: 0x0409  (NEC Corporation)
                  Version:  1.00
                  Speed: Up to 480 Mb/sec
                  Location ID: 0xfa133000 / 8
                  Current Available (mA): 500
                  Current Required (mA): 100

                    Xbox NUI Motor:

                      Product ID: 0x02b0
                      Vendor ID: 0x045e  (Microsoft Corporation)
                      Version:  1.07
                      Speed: Up to 12 Mb/sec
                      Manufacturer: Microsoft
                      Location ID: 0xfa133200 / 12
                      Current Available (mA): 500
                      Current Required (mA): 100


Thanks!

Roee Shenberg

unread,
Mar 5, 2012, 12:55:43 AM3/5/12
to openn...@googlegroups.com
seeing only motor usually means the power isn't plugged in properly...

--
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.

Bit Felon

unread,
Mar 5, 2012, 1:05:53 AM3/5/12
to openn...@googlegroups.com
Thanks! I bet that's it; it's a cheap power adapter so I'm not surprised if it's gone bad. Will get another and go from there.

Thanks again Roee!

Ron Norman

unread,
Mar 26, 2012, 11:53:32 PM3/26/12
to openn...@googlegroups.com
I have the same problem with a brand new Kinect.  Anyone get past this issue?

Igor Barros Barbosa

unread,
Mar 27, 2012, 3:47:17 AM3/27/12
to openn...@googlegroups.com
Do you have Xbox or Microsoft Version ?
What is your machine and which OS are you using ?
Which Program are you trying to run ?1
Did you followed the correct installation ?

01001001011001110110111101110010












--
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/-/4K_VWlIjLZIJ.

Ron Norman

unread,
Mar 27, 2012, 9:21:36 AM3/27/12
to openn...@googlegroups.com
Kinect for Windows
Macbook Pro running OSX 10.7.3
Trying to run the Sample-NiUserTracker
Yes, I believe so.
To unsubscribe from this group, send email to openni-dev+unsubscribe@googlegroups.com.

Igor Barros Barbosa

unread,
Mar 27, 2012, 9:23:37 AM3/27/12
to openn...@googlegroups.com
Kinect For windows is not supported for Primesenser hardrware drivers or even by AVIN2.

Do you have a Kinect for Xbox to test it ?
01001001011001110110111101110010












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

To post to this group, send email to openn...@googlegroups.com.
To unsubscribe from this group, send email to openni-dev+...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages