I try to run a Kinect, using ROS indigo and Ubuntu. Ubuntu is running in a virtual machine (Parallels) with Mac OS as an host.
I tried to test the Kinect via rosrun openni_tracker openni_tracker
with the error:
InitFromXml failed: Can't create any node of the requested type!
Therefore I assume that the system can't access the Kinect. However, using lsusb returns:
Bus 004 Device 008: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor whenever i connect the Kinect
The following does not solve the problem:
http://answers.ros.org/question/9737/openni_tracker-initfromxml-failed-cant-create-any-node-of-the-requested-type/ (simply has no effect at all)
Kinect / Primesense (Xtion) ROS Ubuntu through Virtual Machine (VMware) (different vm and host, also it seems to be a different problem)
If anyone could help me make open_tracker see the device, that would be very helpful.
Related
I have laptop with NVIDIA Quadro T2000 GPU but this GPU is not support with the Omniverse.[see screenshot]
So I am trying with creating AWS EC2 Instance with G4dn.2xlarge instance type with windows server 2022.
Note: I want to Omniverse XR which only support Windows OS.
After creating EC2 instance in AWS, I have install NVIDIA driver from https://www.nvidia.com/Download/index.aspx .
Driver Details are as follows:
Product Type: Tesla
Product Series: T-series
Product: Tesla T4
Operating System: Windows 10
CUDA Toolkit:11.7
Driver is successfully installed I can see the status of installed, But still when I am trying to open any app in Omniverse, for ex. Omniverse create/XR, each and every app got crashed as soon as we launch.
I can see following logs in the terminal:
Image
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
I am trying to execute a codebase (detect and track by facebook) inside the docker container that requires GPU access. My docker image is linux based with CUDA toolkit installed however I cannot see any GPU devices in proc filesystem.
The host machine is windows with CUDA 9 toolkit and drivers installed.
When I try to execute the code it says:
CUDA driver version is insufficient for CUDA runtime version
On searching, I realized, I can leverage nvidia-docker plugin to map the host nvidia drivers to container OS but by the looks of it, I couldn't find any support for windows.
Is there any other way around to execute the codebase inside docker container on my windows OS?
It seems that this is not possible on any Windows OS.
https://github.com/NVIDIA/nvidia-docker/wiki/Frequently-Asked-Questions#is-microsoft-windows-supported
Is it possible to access a USB camera (e.g Logitech c270) from a Docker container?
The camera is connected to a Mac host via a USB port.
Even when running the container with --privileged, i could not find the device (e.g /dev/video0 file does not exist).
Thanks
The default docker-machine creates a virtual machine with official boot2docker.iso. And this slim distro doesn't support USB video device. When you attach the USB device to the virtual machine, the kernel can't do anything without the right driver. So, you won't see any video capturing device, such as /dev/video0.
TL;DR
I've compiled a customized boot2docker.iso which ships uvcvideo driver. Use this one to create you docker machine.
docker-machine create -d virtualbox --virtualbox-boot2docker-url https://github.com/Alexoner/boot2docker/releases/download/v17.06.0-ce-usb-rc5/boot2docker.iso default
Then install the VirtualBox extension, attach the webcam device, you are good to go!
Reference
Attach webcam: https://www.virtualbox.org/manual/ch09.html#webcam-passthrough
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/