Kinect device not found in device manager - visual-studio-2010

When i go to my device manager i can't see my kinect device. I
downloaded the kinect SDK 1.6.

The "Kinect for Windows Device" that is supposed to show up there is the motor in the base of the Kinect, used for tilting the device up and down. While theoretically you don't need it, its absence in the Device Manager may be a curiosity that heralds trouble.
On two occasions where I and a friend have had similar problems (I was missing the Camera, and he was missing the Audio Array), we found the power plug to be the culprit. Make sure everything is connected properly. Try moving to a different the USB port and/or restarting the computer.
That said, what appears in the Device Manager does depend on your specific configuration. My Device Manager, on Win 8 x64 with the SDK 1.6 and an X-box Kinect, shows 4 nodes: the three that you have, plus the "Kinect for Windows Device." 'Meet the Kinect' by Kean, Hall and Kerry says you would have a "Microsoft Kinect Device", a "Microsoft Kinect Camera" and a "Microsoft Kinect Audio Array Control;" no "Security Control." Webb and Ashley's 'Beginning Kinect Programming...' shows the three nodes that you have as the correct ones, plus a "Kinect USB Audio" node under "Sound, video and game controllers."
So really, if your device works, don't worry.

Your screenshot is as it should be. You have the audio array listed and the cameras, which is all the Kinect is... a microphone and a pair of cameras. All the other "magic" is done on the software end, within the SDK.
You are not missing anything and should be able to develop applications with the Kinect.

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

Questions about phantom 4 pro, connection and programming method of inspire 2

이후선
11月7日 CST14:30
Can Phantom 4 and Inspire 2 be programmed on a PC?
I wonder if I can program the drones directly through the PC and acquire the images.
Phantom 4 has a smart device attached. I wonder if I can use the other smart device (iPhone, iPad) to control the dron without using the smart device which is basically installed.
In case of Inspire 2, I use smart device and controller with USB connection. I wonder if smart device and controller can be connected wirelessly without using USB.
I am curious about the communication method of Phantom 4 and Inspire 2.
I wonder what communication frequency should be used to directly control the drone via PC.
I wonder if I can program Phantom 4, Inspire 2 using the DJI Developer-ONBOARD SDK.
thank you..
No, you would need to use the mobile SDK as a bridge (PC talks to the mobile app, mobile app controls the aircraft)
I'm not sure which smart device you mention. If you mention the Phantom 4 Pro remote controller with attached screen, you can just swap to a regular remote without and use an iOS or Android device. In case of the Crystal Sky, you can simply remove it and use another device.
Unfortunately no.
PC control see #1, frequency, 2.4 and 5.8 GHz are commonly used and configurable using DJI Go.
Unfortunately no, for OnBoardSDK supported products see at the bottom of this page.
I can not comment yet. So this is rather additional option how to get video/images from Phantom 4 to PC directly.
1.In the menu of DJI GO app you can setup video streaming, trough RTMP. So video in resolution 720p will be stream.See this tutorial https://afsyaw.wordpress.com/2017/07/06/processing-images-from-the-dji-matrice-100-and-zenmuse-x3-without-the-manifold/
2.While on your Linux machine you can setup video stream server such as NGINX.Tutorial here https://obsproject.com/forum/resources/how-to-set-up-your-own-private-rtmp-server-using-nginx.50/
3.Than you can use OpenCV usb-video lib for ROS to process video or images.
If you have Matrice 100. There is also existing HDMI port on the controller. If you will use USB-HDMI grabber such as Immilet or Magwel - both support Mac,Windows,Linux drivers.You can skip step 1, also video stream is better.

UWP Mediabox - a few questions

I have a question to you and I really hope you can provide me some information.
I wish to build a media center because I have not found any possibilities to cast my stuff straight to the big screen from my Windows mobile phone.
Off course there is the wireless display adapter from Microsoft but I wish not to cast my whole display to my tv.
After testing a few product (Amazon fire tv box, apple tv 3, display dock and the wireless dock) I came to the conclusion that I can not have an all in one solution which fits my perceptions.
From that point I thought that I have to build my own "tv application".
Ok ok... There is kodi(xbmc) and so on... But I think this is just making a detour.
Following features must be included:
running on Windows 10
Cast music, videos and pictures.
Ability to launch and download windows store apps.
Project Rome implementation to share data across devices.
Seems possible but here´s one big problem...
If we are talking about mediaboxes, we do talk about those small boxes besides your tv. Instead off building a micro ATX setup, I want to take this to the next level... using IoT (Raspberry Pi 3).
Using IoT may have some advantages but there are a few disadvantages I have to worry about.
Will Windows 10 work properly on IoT (advantages - disadvantages)
Media streaming?
ARM architecture
Bluetooth, WIFI, Ethernet connectivity
I have never ever worked on IoT before, so I am kinda noob again. I´am asking for some advices to make this possible.
[UWP] How can I stream data (e.g. video, music, images) to another application?
[UWP] Implement a remote control - just like the amazon fire tv controler ?
Advantages - Disadvantages of using Windows 10 on a Raspberry Pi ?
Using windows 10 default applications (Groove Music, Images, Videos - Application) to play incomming data?
What do you think? Is it possible to create a Mediacenter which is running on a raspberry pi using windows 10?
Thank you in advance.
The most straightforward idea would be to create an always-running app with a MediaPlayerElement with a Source property that can be set programmatically by a remote control app. A remote control app could also control the pause, play, next, previous actions.
Be aware that there is no hardware video acceleration support for Raspberry Pi on Windows IoT Core yet, and probably that also won't come soon. There are other devices that do have proper video drivers (look at the hardware support page of Windows IoT Core).
Also be aware that there is no Windows Store on Windows IoT Core, unless you are an OEM (then you can publish your properly signed apps in an official way to devices that are managed by you).
A simpler way would be to buy a Windows 10 box from aliexpress. Then you can use Miracast to stream your screen, install apps from the App Store and play films directly on it, for example using Kodi for which remote control apps exist.

Kinect for Windows - PC Incompatibility

I'm working for an University of Applied Sciences and we want to buy some Kinects together with some PCs for future research as well as student projects and we are currently in a stage where we want to define which hardware to use.
We have a Kinect for Windows sensor and we are testing it with a Dell PC (Inspiron 15r 7520; Windows7 64bit, Intel i5-3210M #2.5GHz; 6GB RAM; USB 3.0).
We installed all the drivers for the 1.6 Version of the Kinect SDK but the PC only detects the Kinect camera once in a while.
In the device manger the "Kinect for windows Audio Array Control" and the "Kinect for Windows Security Control" show up but the "Kinect for Windows" Camera only shows up once in a while. If we plug and unplug the Kinect 10 (or 20 or 30 or 5) times the Camera is not detected 9 times. Then suddenly the camera is detected once and we are able to use it.
The next time we have to plug and unplug the camera 20 or 30 (or 2 or 5 or 10) times until the Camera is detected again. Then, we can plug and unplug the Camera 5 or 6 times and it is detected every single time.
Every time the camera is not detected a Windows USB Information (yellow triangle) pops up stating that a USB device was not detected.
We are quite sure that the Kinect sensor is not the problem because it works on 5 other PC without any problems. Then we thought about an USB Controller problem but after replacing the Mainboard and the USB Controller of the PC the error persists.
Are there any known PC - Kinect incompatibilities or can anybody think of a reason for this strange behavior?
Any help is greatly appreciated.
I'm not sure whether this includes recognising the camera, but there are known issues with certain USB host controllers and version 1.6. If you haven't already, take a look at this MSDN page under the "USB host controller compatibility" subheading.
It does mention two USB 3.0 controllers which are known to have issues. If you are using either the "Etron USB 3.0 Extensible Host Controller" or the "Renesas Electronics USB 3.0 Controller" you might have your answer.

QTKit does not enumerate my USB- and virtual cams in 64Bit mode. Is there a workaround?

I have a problem with Quicktime, that means, QTKit. A long time ago I wrote an app, which is using camera devices on Mac OS X. The user could select the camera using a popup box. I populated the device list into a popup box so the user could choose his preferred camera. Now I migrated to 64Bit code. And everything works fine with iSight cam. Audio devices are listed properly, too (including virtual drivers like Soundflower). For my surprise all camera-devices are missing. And QTKit never enumerates the existing cameras. Is there a workaround or does someone know something about this issue?
I encountered the same issue. Haven't found a workaround other than keeping it 32bit. The Quicktime API mailing list has already discussed this here basically stating that the camera device (your camera device) is a Quicktime Component and Quicktime Components are only supported with Quicktime 7 not Quicktime X if I understood this correctly.
So to put it bluntly: Quicktime Components are not supported in 64bit, for whatever reason I don't understand.
Update: another discussion on the quicktime-api-lists also covers this topic here. Search for vdig in the discussion and you'll find statements on the whole 32bit vs. 64bit complications:
Apple has never updated or replaced the VDIG/ SG / QuickTime Component
API to a 64 bit architecture and your VDIG will never show up as a
selectable device under 64 Bit. So your VDIG is screwed, just like
every other Mac 3rd party QT component developer is.
Also, the term QTKitServer pops up, which seems undocumented but is used by Quicktime X in 64bit mode to play movies in 32bit by using Quicktime components.
Maybe QTKitServer is the key?

Resources