solanic

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 26 total)
  • Author
    Posts
  • in reply to: VRUI – “Unable to locate package” #2430
    solanic
    Participant

    You were able to get your ARS working?
    Sorry for delay in reply!

    in reply to: “Interface 1 is already claimed” Ideas how to fix? #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!?

    in reply to: “Interface 1 is already claimed” Ideas how to fix? #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
    in reply to: Teaching ideas #2281
    solanic
    Participant

    We’re working to build at least 1 here at sea level.

    The junior & senior high school students will be able to take the mobile version to elementary schools to work with 4th & 5th graders if everything works out. We have bigger goals too!

    Also, do you think it’s possible to build modules:

    1. that could include trees and how they affect storm water management of certain areas even if the area is the entire sandbox.
    2. how tides affect, particularly stacking high tides, water flow in an area.

    Just to name a couple.

    in reply to: VRUI – “Unable to locate package” #2277
    solanic
    Participant

    In case this useful for others:

    https://forums.linuxmint.com/viewtopic.php?p=2231966#p2231966

    So, for anyone else who has this problem: I created a patch for Build-Ubuntu.sh, that doesn’t require a separate patch file. This will work no matter where the build script is located in your machine. Just edit Build-Ubuntu.sh:

    in reply to: “Interface 1 is already claimed” Ideas how to fix? #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!

    in reply to: “Interface 1 is already claimed” Ideas how to fix? #2274
    solanic
    Participant

    Thought you might appreciate this find.

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

    libusbx, which is obsolete

    in reply to: “Interface 1 is already claimed” Ideas how to fix? #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?

    in reply to: “Interface 1 is already claimed” Ideas how to fix? #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.

    in reply to: Test message #2262
    solanic
    Participant

    Thank you for trying Sean!

    Just tried using CODE syntax and not using CODE syntax to add our info here and it wont allow it.

    We attempted every USB port including the 4 on front plus the commands in the Archivist topic.

    Would it be appropriate for us to share the info in Github under the Kinect branch?

    We really appreciate your help & efforts Sean!!

    in reply to: Test message #2260
    solanic
    Participant

    We still have a new Topic I added that apparently has been “under review for moderation” for several days under “Kinect” tag.

    That is directly related to: http://doc-ok.org/?topic=usb-problems-with-kinect-4

    We’re very excited about the potential of the migration from old forum to this one & the new student assistant!

    in reply to: Content Migration from Defunct Forum #2257
    solanic
    Participant

    This is fantastic news!

    Thank you!

    Any way a small team like ours that is brand new to this project can help?

    Thanks to @skrobinson, as example, Linux Mint MATE 21 now works with VRUI.
    We’re currently trying to have success with Kinect and are currently stuck.

    in reply to: USB Problems with Kinect #2256
    solanic
    Participant

    Thank you!
    We’re using LM21 so its probable drivers aren’t available yet? (This is sort of over our head as of today but this is our current thinking.)

    Doing lsusbit returned:

    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 003: ID 0461:4ef3 Primax Electronics, Ltd HP 310 USB Optical Mouse
    Bus 001 Device 014: ID 045e:02c4 Microsoft Corp. Xbox NUI Sensor
    Bus 001 Device 013: ID 045e:02d9 Microsoft Corp. NuiSensor Adaptor      
    Bus 001 Device 005: ID 0bda:2852 Realtek Semiconductor Corp. Bluetooth Radio
    Bus 001 Device 002: ID 0461:4ef0 Primax Electronics, Ltd HP 310 Wired Keyboard
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    Doing lspci | grep "USB 3.0" returned no results.

    The pc is a HP Victus 15L desktop. No issues booting.

    in reply to: VRUI – “Unable to locate package” #2215
    solanic
    Participant

    SUCCESS SEAN THANK YOU!

    How would you recommend we share your fix for Linux Mint 21 in here & Github Issues I opened?

    As a rookie, I don’t want to goof how your fix is shared for everyone who’ll see it in the future.

    THANK YOU AGAIN! GO ARTICHOKES!

    in reply to: VRUI – “Unable to locate package” #2209
    solanic
    Participant

    It didn’t hit me until you said that out loud Sean.

    I try not to use Amazon for a lot of reasons.

    This is the pc I bought:
    https://www.bestbuy.com/site/hp-victus-gaming-desktop-intel-core-i3-12100f-8gb-memory-nvidia-geforce-gtx-1650-512gb-ssd-mica-silver/6504334.p?skuId=6504334

    I’ve been staring at the Victus for a couple weeks & saw the Amazon link multiple times & it never occurred to me they could be different. ( nervous grin )

    So we helped the community by showing the Victus & TPM chip has issues with 19.3 & 20.1?

    I imagine the Pavillion works I guess?

Viewing 15 posts - 1 through 15 (of 26 total)