Topic: “Interface 1 is already claimed” Ideas how to fix?

Tagged: Kinect

This topic has 10 replies, 2 voices, and was last updated 1 year, 7 months ago by solanic.

Viewing 11 posts - 1 through 11 (of 11 total)

Author

Posts
September 8, 2022 at 12:34 pm #2230
solanic
Participant
Found previous forum in wayback machine for this Topic

http://web.archive.org/web/20210728133702/https://arsandbox.ucdavis.edu/forums/topic/interface-1-is-already-claimed/

Step 6: Connect and Configure the 3D Camera

I tried the instructions in several directories including this:
```
~/src/Kinect-3.10$ sudo /usr/local/bin/KinectUtil getCalib 0
Downloading factory calibration data for Kinect v2 V2-365303133947...
terminate called after throwing an instance of 'std::runtime_error'
  what():  USB::Device::claimInterface: Interface 1 is already claimed
Aborted
```
September 12, 2022 at 10:01 am #2270

Sean Robinson
Participant

@solanic Sorry, I missed this post before.

What output do you get with sudo /usr/local/bin/KinectUtil list?

September 12, 2022 at 10:21 am #2271

solanic
Participant

Results:

Kinect 0: Kinect V2 for Windows/Xbox One, USB address 001:028, device serial number V2-365303133947

Not sure if this matters: the “device serial number” does not match what appears might be the serial number printed on device.

September 12, 2022 at 10:42 am #2272
Sean Robinson
Participant
My strong suspicion is that your Kinect is malfunctioning.
- Reports as a V2.
- Will not connect as a USB 3 device.
- Serial numbers do not match.
The serial numbers (external and reported by KinectUtil) on my Kinect V2 match.

Can you borrow another Kinect to try out?
September 12, 2022 at 11:21 am #2273
solanic
Participant
I have multiple Kinects.

I was able to get a crisper view of K-1 serial number and it matched in both Step 6 instruction and Util list.

You might notice it’s extremely difficult to view the numbers because of how close the moving platform base is to manufacturer sticker. (I tried viewing with multiple magnifiers. Yes, I wear bifocals.)

K-2 also matched.

So I tried Step 6 and it returned the same Aborted result:
```
$ sudo /usr/local/bin/KinectUtil getCalib 0
Downloading factory calibration data for Kinect v2 V2-271548135047...
terminate called after throwing an instance of 'std::runtime_error'
  what():  USB::Device::claimInterface: Interface 1 is already claimed
Aborted
```
Is it possible because of using LM21 the Kinect toolkit has some kind of conflict or missing library?
September 13, 2022 at 5:35 am #2274

solanic
Participant

Thought you might appreciate this find.

https://forums.linuxmint.com/viewtopic.php?p=2231669#p2231669

libusbx, which is obsolete

September 13, 2022 at 8:37 am #2275
Sean Robinson
Participant
libusbx is not used. The README mentions it for historical context. libusbx was merged into libusb.

Is it possible because of using LM21 the Kinect toolkit has some kind of conflict or missing library?

Yes, but such a conflict or missing dependency is most likely to show up during compilation.

IMHO, the heart of the problem you are seeing is that the Kinect is appearing on the wrong USB bus.

When I pass my Kinect V2 USB connection into a LM 21 container and run lsusb, I get the following output.
```
Bus 003 Device 002: ID 045e:02c4 Microsoft Corp. Xbox NUI Sensor
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
```
Every lsusb output you have posted shows the Kinect on the same Bus as the “2.0 root hub”. I think you could have success on the LM forums by asking for help about this specific issue: why is the Kinect V2 on USB 2 and not USB 3?

I suspect the final answer to this will be to replace the Kinect power supply/USB adapter with a different model.
September 13, 2022 at 10:43 am #2276

solanic
Participant

You dashed our hopes for an ez fix with merged into ha.

I will ask that question in LM Forum.

Possible the Adaptor is only USB 2.0 I guess?

And I imagine it’s impossible to find a “3.0” Adaptor??

Thank yoU btw!

September 20, 2022 at 9:37 am #2283
solanic
Participant
Woo hoo!

This: https://www.hyperkin.com/kinect-converter-adapter-for-xbox-one-s-xbox-one-x-windows-10-pcs-hyperkin-officially-licensed-by-xbox.html

Returned:
```
sudo /usr/local/bin/KinectUtil getCalib 0
[sudo] password for ars:         
Downloading factory calibration data for Kinect v2 V2-271548135047...

Depth camera intrinsic parameters: 367.143, 251.583, 367.143, 205.421
Depth distortion correction coefficients: 0.0817633, -0.268767, 0.105677, 0, 0
Depth unprojection matrix:
      0.00027237  0.00000000  0.00000000 -0.06852459
      0.00000000  0.00027237  0.00000000 -0.05595128
      0.00000000  0.00000000  0.00000000 -0.10000000
      0.00000000  0.00000000 -0.00000088  0.00200000
Smallest eigenvalue of color system = 0.000588743
Optimal homography from depth space to color image space:
     -2.92319768  0.02045509 -0.04977884 1835.67404906
      0.02339482  2.93977514 -0.00006789 -110.78348893
      0.00000000  0.00000000  1.00000000  0.00000000
      0.00001379  0.00000264 -0.00000013  1.00000000
Writing full intrinsic camera parameters to /usr/local/etc/Vrui-8.0/Kinect-3.10/IntrinsicParameters-V2-271548135047.dat
```
September 20, 2022 at 2:27 pm #2284

Sean Robinson
Participant

Excellent! Is this power supply/USB adapter a replacement for the first one?

September 20, 2022 at 3:26 pm #2285

solanic
Participant

Yes!

And yes. First adapter & converter was original, used & resold from GameStop. USB 2.0 I guess?

The Hyperkin one is a brand new manufactured one.
How great is that!?
Author

Posts