I have an Xbox One with Kinect 2. I want to know if I can connect it to my PC, and if so, how to do it ?
Microsoft Finally came up with a sane solution to Xbox Kinect One problem
Check this out
http://www.microsoftstore.com/store/msca/en_CA/pdp/Kinect-Adapter-for-Windows/productID.308878000
You can un-officially connect the XBone Kinect to a PC.
Although you'll invalidate your warranty on the Kinect you should still be able to use it with the XBone afterwards.
Not sure if its a great idea for your project though - you'll still need a Windows 8 PC with the right USB 3.0 controller for it to work and you are at risk of non-windows Kinect SKUs being blocked/nerfed in future.
But basically:
Disconnect the USB lead from the Kinect
Take the Kinect apart
Solder a 12v power supply to the USB 3.0 powered-B side pins where the connector joins the PCB (these are extra pins in addition to the standard USB 3.0 spec for "special" device power input/output)
Connect the Kinect to the PC with a standard USB 3.0 B cable
A picture of where to solder the 0v/12v wires is here.
I connected them to a barrel connector to fit a spare laptop PSU.
This works for me with Windows 8.1 and the MS KinectSDK public preview 1407.
To connect Kinect 2 (Xbox One) to your PC, you need a 12 V power supply and this cable:
(source: diskdoctors.com)
Using information from this picture:
Kinect 2 cables:
Change standard Kinect cable with a new cable USB 3.0 A, other cables (grey and brown is 12 V power).
Sorry, but there is no official way to connect the XBOX One Kinect with a PC. A hack might be available one day, but I would not recommend going that way.
Buy a "Kinect for Windows V2 Sensor" - that includes the license and SDK to develop your own applications with the Kinect V2.
I connected the 12 V DC , as it must be in some photos;I used a Renesas USB 3.0 PCI-EXPRESS card and a 3m cable;and Kinect XBOX ONE was not detected by windows;I cut and re -made the long USB3 cable to 1m cable; and again nothing detected by PC.
It looks that a POWER ENABLE signal STRAP(CONNECTION) must be made somehow(in the kinect 2)
The "distinct" hackers forgot to explain that signal (how to).
I didn't have the time to analyze the good images of the original USB3 HUB with the industrial USB3 B male connectors uploaded on web(by the way some photos disappeared meanwhile) This industrial USB3 cable of Microsoft has USB3 standard-5 pins, USB2 standard-4 pins + another additional 4 pins (of course one is ground and one is 12 V, and at least one not documented.
Fortunately I have about 4 projects to work till connecting the sensor and Microsoft did
something interesting. It manufactured and sells the adapter for the sensor separately.
A bit expensive, at 50$ but however we speak about one power adapter, a USB3.0 HUB and a USB 3.0 cable. ( the price had to be better at 30$) , even so it is not killing price.
http://www.microsoft.com/en-us/kinectforwindows/purchase/default.aspx#tab=2
and it looks already available for purchase.
Make sure hardware matches standards if you are using a PCIe USB 3 adapter - your motherboard will probably have to support PCIe 2.0 (PCI Express).
Related
Can I use kinect sensor for testing my algorithms related to depth measurement? Have someone already tried this?
I have researched a bit, and have thus few questions -
is there a linux driver to work with kinect?
Which kinect is advisable? Kinect v1 or v2?
is there a way that I can get the data on my computer using a USB cable? As far as I have seen, the kinect needs to be modified ( i.e add a 12 V power supply ). Does anyone know the specifications of this power supply? How many ampere should the power supply support?
lastly why is there is such a massive price difference between the usb adaptor for Kinect V1 ( for xBox 360 - 4 pounds ) and Kinect V2 ( for Xbox one - 50 pounds), although both of them simply divert power and data cable as far as I understand.
I'm not sure whether the Kinect sensor is appropriate for testing your algorithms given that I don't know the specifics, but to answer your other questions:
Yes, there are drivers such as OpenKinect's libfreenect for Kinectv1 or libfreenect2 for Kinectv2 for Linux.
Note that I only have experience with the official Kinect SDK. If you care about skeletal tracking quality, you should probably use the official Kinect SDK on Windows. If you don't care about the skeleton tracking, that gives you a lot more options.
Kinect v2 - it has better specs. Certain requirements might call for using Kinect v1, but generally, Kinect v2 is the default choice.
No, you need the adapter/power supply to connect it to a PC. The official power supply is 2.67A at 12V. There are many tutorials online for DIY, such as this YouTube video: How to Hack Xbox One Kinect to Work on Windows 10 PC
Supply and demand. The adapters are no longer being manufactured and there is more demand for the Kinect v2 adapters.
I'm looking for a device who has the capability to be a GPSR tracker and have the same features like ELM327 OBD II has. The features I'm talking about are:
Engine RPM
Calculated Load Value
Coolant Temperature
Fuel System Status
Vehicle Speed
Short Term Fuel Trim
Long Term Fuel Trim
Intake Manifold Pressure
Timing Advance
Intake Air Temperature
Air Flow Rate
Absolute Throttle Position
Oxygen sensor voltages/associated short term fuel trims
Fuel System status
Fuel Pressure
...over 4,000 - 15,000 additional values.
I've found some devices but none of them has this features...
Since you did not mentioned any platforms, I write 3 opportunities you have and you can spread it further!
1) You can use Arduino Uno or Raspberry Pi with Arduino kits.
For instance, combining Raspberry Pi and Arduino geolocation tracker (GPRS + GPS) kit and a CAN Bus Module, you can get what you want. There are many good examples and libraries for C++ and Python. For a rough idea look at Cooking Hacks website, Realtime GPS+GPRS Tracking example and CAN Bus Module Tutorial for Arduino and Raspberry Pi.
2) Alternative is using a mobile device (cellphone) using a Bluetooth or WiFi CAN Bus (eg. ELM327) and write an app to save the GPS data through the Built-in GPS module and OBD data via ELM327. Then you can send your data using mobile data.
3) I've seen devices such as TK228 OBD-II GPS Tracker But I don't have any idea how useful they are and how they work!
I have tested 1 & 2. There are some bottlenecks using Raspberry Pi but Android + a CAN Bus module worked for me perfectly.
Cheers!
i have found this device which has elm327 and gsm both functions
https://www.alibaba.com/product-detail/obd-gps-tracker-elm327-obd2-scanner_62198702445.html?spm=a2700.7724857.normalList.95.15d42a92zLl08q
May be it will work for you it will drop the data into the system itself by IMEI number of the obd device
I used Kinect 2.0 connected to motherboard Gigabyte through ST-Lab U710 USB3.0 PCI-E-1 controller (claim SuperSpeed) inserted in PCI-E-16 of course. All SDK samples works fine but there are no Super Speed in driver hub usb3.0 so I get only 7 fps not 30.
I bought Foxconn H67S/H61SP motherboard, because it's claim Super Speed in PCI-E-16. I use ST-Lab U710 USB3.0 PCI-E-1 controller in PCI-E-16 again. But speed is 7 fps only and no SuperSpeed words in driver hub. Also I need make Disable\Enable HD Video Graphics for start Kinect demo now. (Disable\Enable KInect or controller USB not help.)
When I connect Kinect to more expensive MBs with USB3.0 integrated all works fine and speed is 30 fps.
My question: How to get words "Super Speed" in driver of ST-Lab U710 controller (chip Renesas\NEC mPD720202 - claim SuperSpeed)?
Also Why Host Controller Utility say: "There is not any controller USB3.0" though it works? May be controller don't turn on Super Speed?
I use Win8.1 64 bit and drivers from 2015 Drivers Pack Solution.
If the Kinect v2 works (even if only at low FPS), it is most likely not an USB problem. If the Kinect v2 can't connect as a superspeed device, it won't work at all.
It's more likely that your CPU and/or graphics card is too slow. The System Requirements claim you need the following:
4 GB Memory (or more)
I7 3.1 GHz (or higher)
DX11 capable graphics adapter
But that's pretty vague and the resulting FPS can vary widely, depending on your specific setup.
Does anyone here use USB 3.0, and can tell me why when I plugin my Xbox One Kinect 2.0 USB 3.0 cable into the computer, why it keeps sporadically disconnecting and reconnecting even though I downloaded all the windows updates, all the graphics card updates, all the firmware updates, etc...? And YES, I tried several different Ports. It's not broke. I got it new for Christmas.
After fighting with this for weeks, I finally found the root of my frequent disconnects. At some point, I had disabled the Xbox NUI Sensor Microphone Array to eliminate a feedback loop:
Control Panel > Hardware and Sound > Sound > Recording
After re-enabling the Kinect microphone, the Kinect stopped disconnecting.
To eliminate the feedback loop, I reduced the Kinect microphone's level setting to 0. You can get to the level setting from the Recording tab in the Sound dialog. Select the Xbox NUI Sensor Microphone Array and click the Properties button. From there, select the Levels tab.
I had a similar issue and I kept trying every thing for days, and finally the issue turned to be from the kinect AC adaptor... I tried it with the official windows sdk and developer toolkit, when I attempted one of the example codes the issue persists to appear but with a clear message asking to plug the power cord in, though the adaptor is brand new!!
I searched for some information a bout the AC adaptor and it seems that there is a problem with the adaptor, and most importantly the Kinect manual states that any unoriginal adaptors may cause the device to fail - also the manual says that original AC adaptor power output is 12V-1.1A while the one I have is rated 12V-1.08A (no big deal but who knows)
Kinect for Xbox 360 freezes and disconnects from USB after running Processing SimpleOpenNi depth image example
I had this problem,too. My system using pci-e usb 3 gen 2 and in windows 10 v1903 and kinect sdk 2 ... and all thing OK.. worked correctly .then after a date .reapetdly disconnect and restart.
at last ..I found this problem on my system...
I disabled sound using in windows setting.
I enabled this item in setting and all things became OK.
Read this, if you use an USB3.0 expansion card in a PCIe slot.
In my case I had connected the adaptor to an USB3.0 card (Transcent PDU3). After some hours research I discovered that the mainboard (MSI K9a2 Platinum) had Gen2 PCIe for the PCI-E x16 slots, but not for the PCI-E x1 I had plugged the USB card into. After switching to a PCI-E x16 slot, the constant disconnecting was over.
Don't confuse PCIe version and USB version here. For a Kinect 2.0 you need USB 3.0 and for USB 3.0 to run at super speed, you need PCIe 2.0 (or Gen2).
Testing PCIe version
You can use GPU-Z to determine which PCIe-Version the slot has where you got your graphics card plugged in -- let the mouse pointer hover over the bus interface field and wait for the tooltip and it will reveal the PCI-e version of your graphics card as well as the one of your mainboard. If you confirm it is Gen2 (or PCI 2.0) try to use that slot to put a confirmed-as-working-with-the-Kinect-2-USB3.0-card in it. (Having onboard graphics or a second PCI-Ex16 slot will definitely come in handy here).
Hope this helps.
I think it has to do with the USB 3.0 version, older machines won't run it. You need USB "3.1" and controllers usually manufactured after 2013 have it. It's often mislabelled as USB 3.0 in marketing material. USB 3.1 is also known as "SuperSpeed" or "SS10" which goes up to 10 Gbit/s. USB 3.0 "only" transports at 5 Gbit/s.
I have two five years old big rigs (Z68X-UD3H-B3, i7-3770K, and a 970a-D3, FX-8350) and it constantly disconnects. Both have 2011 board technology.
I also have two laptops, a VAIO and a Lenovo, which were built after 2013 (when they changed to USB 3.1) and it runs fine on both of those machines.
I too suspected the power supply at one point, nope, I thought I had a broken Kinect (bought a second, nope, now I own two.)
Other things to check:
- You might be able to use a USB 3.1 PCI card as long your MotherB will carry it.
- Remember to load the Kinect SDK 2.0 and also update the driver to the 2016 driver (SDK 2.0 comes with the 2014 driver).
- Remember USB 3.x is the "Blue" USB plug not the black.
This is not a case of requirements increasing beyond the capabilities of USB3.0!
Its also not a problem with Win10 1809 or KinectSDK 1409.
It will disconnect if your apps have no access to either microphone or camera.
You can check or reset your settings the easiest with a free program called OOSU10.
Runs fine on my 2012 laptop.
If your problem is that the Kinect Configuration Verifier does not start at all, then this is caused by having disabled the printer spooler service.
I have a device that came with an AC power adapter where the connector is a mini USB plug. The device however doesn't seem to power itself from a computer's USB port (using a standard USB-mini USB cable) unless a specific driver is installed. The driver is only available for Windows. I would like to charge the device from USB plugs on different platforms.
My question is: why isn't power getting to the device without the driver? Is a driver always required for a USB port to start giving power? Or is it this device that's specifically made not to take a charge unless some software routine triggers it to do so?
I guess my question can be summarized as: Is power not present on the USB cable or is it present but the device ignoring it. If the answer is the former, I'll be trying to figure out how to write software that will enable the voltage to always be present.
Thanks
Why isn't power getting to the device without the driver?
USB ports are always powered when the computer is on and the USB control software hasn't detected current overdraw.
Is a driver always required for a USB port to start giving power?
No, the USB port is always required to start off providing power to the device, otherwise the device could never initiate a connection.
Or is it this device that's specifically made not to take a charge unless some software routine triggers it to do so?
This can be complex. To meet the USB spec a device cannot pull more than a few mA until it's registered with the computer.
However, nearly every computer allows the USB port to pull the full 500mA (and more) before it'll shut the power off.
The device you're charging is being nice by not pulling any significant power until the computer gives permission.
Writing software won't help, the device has to register with the USB bus, which will best be done with the driver.
However, the plug in charger doesn't do that. It likely has shorted the two data lines of the USB plug together, which signals the USB device that it's not connected to a computer and can pull the full 500mA without waiting.
Take a USB extension cable, cut off the jacket, and short the data lines (green and yellow, sometimes) together on the end going to the USB device, and leave them cut without touching anything on the end going to the PC, and leave the read and black power wires connected through.
It might work. If not, take the wall charger apart and find out what it's doing with each of the four USB wires, and see if you can duplicate that.
This might be helpful if you are targeting a linux system.
This seems to be platform-specific. In Linux, USB ports are always energized, while on Windows they don't. Thumbdrives with LEDs turn off when unmounted in windows, but in Linux they stay lit. My cellphone's manual says that it can't be charged by a PC, but I regularly do on my linux machine, I guess that's because they don't have a driver and windows won't power up without one.
Have you tried plugging it into a 'dumb' USB port - like the one on a car charger? Those ports are pure power and don't create a USB network. I think.
Unless you have the hardware specs from the manufacturer, I think you are out of luck. You could try reverse engineering the driver to see what it does, but I'd expect it would be cheaper and easier just to buy one with cross platform drivers or charges without the driver.