Using Kinect v2.0 (USB 3.0) with Raspberry Pi3 (USB 2.0) - raspberry-pi3

I just bought the USB Kinect adapter and realised it just works with USB 3.0. When connecting it to the USB 3.0 port of the PC everything works fine, but when I tried to connect to my Raspberry Pi3 it just won't work. I've already installed all the drivers (Openni,Sensorkinect) but when I execute the "Sample-NiSimpleRead" of OpenNI I get the following message:
One or more of the following nodes could not be enumerated:
Device: PrimeSense/SensorKinect/5.1.2.1: The device is not connected!
Besides, when I try sudo lsusb -v|grep -i nui I get:
iProduct 2 NuiSensor Adaptor
Still, there's no way to make it work. I've seen some projects in Youtube which use Raspberry3 and Kinect, so there should be one way to solve this. Do you have any idea?

Kinect v2 is solely USB3, while RPi is USB2 (as you stated). Maybe you've seen the videos of Kinect v1, which uses USB2?

Kincect V2 needs USB-3, so if you need to plugin into a embedded device then Nvidia Jetson TK1/TX1/TX2 boards are the best bet. Here is a link that shows a demo of Kinect-V2 with Jetson TK1. I have tried the same steps for TX2 and it works fine after the successful installation of "libfreenect2".

Related

How can I use Kinect 360 with Windows?

I am trying to connect Kinect 360 with Windows.
What I try:
I try to connect it with Windows 10 (64-bit) and Windows 8.1 (64-bit) (both ware host OS).
I downloaded and Installed the Software Development Kit (SDK).
I downloaded and installed the Kinect for Windows SDK v1.8.
I downloaded and installed the Kinect for Windows Developer Toolkit v1.8.
Then, I plug the Kinect 360 in the electric power and connect it with my Lap Top using the USB 3. I am using a power supply adapter cable for Xbox 360 Kinect Sensor (see the picture below).
As a result, no new hardware ware listed in the Device Manager like no new microphone, no new camera, no new unknown devices.
BTW I am not sure if the Kinect hardware is working at all. I don't know how to check it - there aren't any lighting lights on it. I did some research, but I didn't see any lights on working Kinect 360 on youtube videos. So I don't know how to test whether the Kinect is working (without connecting it with XBOX).
I want to connect the Kinect sensor with the PC machine because I need to do some tests. If there are other solutions with another OS (like Linux-based or MAC OS), I can try it too.
there was the same problem, it shows up as a microphone, I thought the problem was in the kinect itself (I thought it was broken) so it lay on the shelf for 2 years. I updated my PC 4 months ago and it turned out that there is usb 3.0 on my old motherboard, but it is not supported (perhaps 3.2 is needed for it). Now kinect works fine and is being determined

Does the FTDI D2XX driver work on Ras Pi 3 b+ running Windows 10 IoT v.10.0.17661?

I'm trying to get data back from a magstripe reader and an rfid reader that are plugged into the raspberry pi and communicate via serial. I can connect to the readers but when I try to read from them I don't get anything.
Was wondering if the driver even works on the newer iot OS versions.
So I used the code located from this link! in conjunction with the driver install steps from the tutorial Rita shared and I was able to get the Serial Device's, open them and and start reading data.

Does Android things Stable release 1.0.0 officially supports Internet using usb stick via GSM/3g/4g for Raspberry Pi 3?

I want to provide IOT solutions using android things in remote areas where ethernet or wifi is not available , hence, does android things stable release 1.0 supports internet via usb dongle using sim like 3g/4g in raspberry pi 3 model B
According to the Unsupported Features list android.hardware.telephony is not supported. But you can connect 3G/4G modules via UART and use Internet data exchange via it's AT-commands (e.g. like described in this manual for SIMCom modules).

Kinect USB 3.0 keeps reconnecting frequently

I'm working on a Kinect app, using a Kinect 2.0 for Xbox One on a Windows 10 PC. Now I have a problem using a new computer. Testing the Kinect with KinectStudio or any of the example programms, the Kinect keeps reconnecting frequently, as if you would pull out the usb cable and plug it in again.
If the Kinect is running I get the full 30 fps but mostly only for about 10 seconds before the connection is interrupted.
There is no other device plugged in at the usb 3 ports and I tried all of the ports. The computer has an Intel 8 Series/C220 Series USB Chipset and I updated and reinstalled all the drivers. The Kinect Configuration Verifier showes a problem with the usb Controller: "Supported USB 3.0 port detected with unknown bandwidth. Kinect may or may not be compatible with your hardware."
Did anyone experienced something similarly or do you have any idea how to fix it?
Your Kinect has to be attached to a 3.0 port that has its own pcie channel.
If the usb isn't built into the motherboard and you don't have a 3.0 without anything else on the channel, then you'll need to get a pcie to usb 3.0 addition for your motherboard.

Run official Kinect SDK on iMac

I would like to create my Kinect development environment and am contemplating using iMac as the box with Windows 7 installed as dual boot and/or parallels.
Has anyone tried this configuration earlier and does it work?
Running Bootcamp(dual boot) works with windows 7/8 Parallels does not.
I have a macpro 1,1 and a mac air both work with bootcamp(dual boot).
The only thing that could cause it not to work is the USB configuration. Kinect requires that it be connected to a USB host controller and not a hub. I believe all of the iMac's USB ports are host ports so I don't believe this to be an issue. If you use the Kinect Sensor Chooser control built into the WPFViewers sample app it will tell you if that particular problem arises (insufficient bandwidth).
Parallels will not work with the SDK at the time of this writing due to driver. Kinect is not an official USB device and the driver requires direct communication with the Kinect. I hoped that this would be resolved with the official Kinect for Windows hardware but alas it was not.
You might want to look at native OSX Kinect development using OpenKinect
http://openkinect.org/wiki/Getting_Started
If you don't want to have to write all the image processing code yourself, and are working in C#, you could start with the Accord library:
http://accord-net.origo.ethz.ch/

Resources