Robotics StackExchange | Archived questions

My virtual machine can not open the kinect one device

When I install the libfreenect2 lib in my virtual machine, and I run the test program. I got the error bellow:

dragon@ubuntu:~/robot/camera/kinect/libfreenect2/build$ ./bin/Protonect

Version: 0.2.0

Environment variables: LOGFILE=

Usage: ./bin/Protonect [-gpu=] [gl | cl | clkde | cuda | cudakde | cpu] [] [-noviewer] [-norgb | -nodepth] [-help] [-version] [-frames ] To pause and unpause: pkill -USR1 Protonect

[Info] [Freenect2Impl] enumerating devices...

[Info] [Freenect2Impl] 6 usb devices connected

[Info] [Freenect2Impl] found valid Kinect v2 @4:2 with serial 021766664847

[Info] [Freenect2Impl] found 1 devices

[Info] [Freenect2DeviceImpl] opening...

[Info] [Freenect2DeviceImpl] transfer pool sizes rgb: 2016384 ir: 608*33792

[Info] [Freenect2DeviceImpl] opened

[Info] [Freenect2DeviceImpl] starting...

[Error] [protocol::CommandTransaction] bulk transfer failed: LIBUSBERRORTIMEOUT Operation timed out

[Info] [Freenect2DeviceImpl] closing...

[Error] [protocol::CommandTransaction] bulk transfer failed: LIBUSBERRORTIMEOUT Operation timed out

[Error] [protocol::CommandTransaction] bulk transfer failed: LIBUSBERRORTIMEOUT Operation timed out

[Info] [Freenect2DeviceImpl] releasing usb interfaces...

[Info] [Freenect2DeviceImpl] deallocating usb transfer pools...

[Info] [Freenect2DeviceImpl] closing usb device...

[Info] [Freenect2DeviceImpl] closed

Anyone can help me ??

Asked by Dragon on 2017-04-13 21:27:56 UTC

Comments

"found valid Kinect v2" are you sure you connect a Kinect 1?

Asked by NEngelhard on 2017-04-14 10:03:22 UTC

Yes, I connect a Kinect One

Asked by Dragon on 2017-04-17 22:45:20 UTC

Usually virtual machines don't play well with USB3 devices, I never succeeded at launching such a sensor inside a virtual machine.

Asked by Martin Peris on 2017-04-17 23:25:41 UTC

Has anyone found a solution for this yet? I'm having a similar issue.

Asked by Maximus636 on 2018-12-17 15:03:02 UTC

Answers