New Software Installation Mechanism

Home Forums AR Sandbox Forum New Software Installation Mechanism

Viewing 13 posts - 16 through 28 (of 28 total)
  • Author
    Posts
  • #2776
    jdelaat
    Participant

    Good day, unfortunately I am also experiencing the same Protocol error as described above. I have tried a couple of things but now I am out of ideas.

    I have tried a couple of Kinects we have lying around. They are all ‘Kinect V1 for Xbox 360 1414’ models as returned by KinectUtils list. Note: KinectUtils setLED works as desired. The protocol error is returned when I attempt KinectUtils getCalib 0.

    I initially got this error after setting up and installing on Ubuntu 24.04 LTS, after which I decided to reinstall an older OS (Linux Mint 20) but this has the same outcome.

    Also, I would like to report that BuildVrui-current.sh contains a mistake for both Ubuntu and Mint where it tries to install libcd1394-dev where the package name should be libdc1394-dev. This fixes a lot of the build errors that @gcsciencemill was experiencing because all optional packages would get skipped due to apt erroring out. Perhaps PullPackage SteamVR is also required before pulling Vrui to fix the compile errors regarding ‘headsetDeviceName’. Hopefully someone finds this useful in the future.

    But unfortunately, I am currently unable to continue setting up the Kinect. Hopefully this issue will get picked up soon.

    Cheers,
    Jasper

    #2777
    gcsciencemill
    Participant

    So the packages didn’t work on my new MINT install…. so I needed to make from the tar. Now I am getting some openal errors… mostly in the SoundContext.cpp and .h files. Make is complaining about how it can’t find a field named aLDevice or aLContext. Not sure what to do…. has anyone gotten this to work on a recent build either from package or compile? I am happy to change what I do to get the code to work.

    #2778
    okreylos
    Keymaster

    I am seeing the issue reports. A core problem seems to be that PullPackage Vrui does not install some optional libraries (libtiff, libpng, …), and that later code assumes that those libraries are there. That’s a bug.

    I am working on the root problem. In the meantime, I updated the PullPackage Vrui command to hopefully pull those packages successfully. Re-run that command and see if it works.

    #2779
    jdelaat
    Participant

    Can confirm that the new Vrui version installs packages correctly, so I no longer need to apply my corrections to compile Vrui.

    Unfortunately my error still remains:

    enversed@zandbak:~$ KinectUtil getCalib 0
    Downloading factory calibration data for Kinect A00361802428039A...
    terminate called after throwing an instance of 'std::runtime_error'
      what():  Kinect::Camera::getCalibrationParameters: Protocol error while requesting parameter subset
    Aborted (core dumped)

    I noticed that with the new Vrui update, my PC was missing udev-related packages. However after updating I still get the above error. Could this be related?

    #2780
    oconnorc
    Participant

    The intrinsic parameters file still is not being created. Is it possible that the problem is with my Kinect?

    #2781
    DigitalBlack
    Participant

    I’m getting the same error as jdelaat just wanted to see if anyone found a solution…

    #2782
    jdelaat
    Participant

    I happen to have found a workaround that I can confirm resolved the issue for me today. The kind people of System76 have packaged an older version of the software that doesn’t have this error. You’ll have to use Pop_OS as distribution, though.

    See these instructions: https://support.system76.com/articles/ar-sandbox/

    • This reply was modified 1 month, 2 weeks ago by jdelaat.
    #2786
    robbo
    Participant

    I wrote a post how I think I may have fixed the KinectUtil getCalib 0 function not writing the intrinsic parameters file. I rewrote part of the Camera.cpp file and recompiled it and it seems to be working now. You can read more on my thread here

    #2800
    okreylos
    Keymaster

    I fixed the underlying issue that caused KinectUtil getCalib to fail. I pushed the changes to the PullPackage repository, meaning to apply the fix, simply re-run

    
    PullPackage Kinect
    

    and continue the installation procedure as usual.

    #2806
    robbo
    Participant

    Thank you @okreylos !

    I’ll delete my forum thread about it so it doesn’t cause any confusion in the future.

    #2814
    sanginnwoo
    Participant

    I have tried this on Linux Mint 22 Mate Edition (installed freshly) in Surface Pro 9 (Dual Boot System).
    I didn’t install the NVIDIA driver as the computer doesn’t have an external graphic card.
    Following the instructions from @okreylos, I haven’t encounter any errors during the software installation.
    Because I haven’t construct physical system, I don’t know the sandbox actually work; however, in terms of software, it runs with no error.

    #2815
    johnhart
    Participant

    Hi, I have zero experience with Ubuntu, I’m a teacher, I don’t know what I’m doing and I’m trying to get this to work to use with kids at school. Hopefully someone out there can help us out, we’d very much appreciate it.

    I followed the instructions in this thread and everything seemed to install OK, I got the messages ‘Package Vrui, version 12.2, successfully installed’, ‘Package Kinect, version 4.2, successfully installed’ and ‘Package SARndbox, version 3.2, successfully installed’ in the terminal and I have icons on the desktop.

    I have the original Kinect for the Xbox360 (model 1414) and the light on it blinks green when I plug it in to the PC (it’s running Ubuntu 24.04.1 LTS). When I try to run RawKinectViewer it tells me I have fewer than one 3D cameras connected to the host. I noticed it says, ‘Support for Microsoft Kinect v2 (Kinect-for-Xbox-One) enabled’ in what was returned in the terminal, so I imagine that might be why my Kinect isn’t recognised? If anybody has any ideas about what I need to do to get the Kinect recognised (and any other tips) I’d very much like to hear about it.
    Thanks

    #2816
    okreylos
    Keymaster

    This is usually a connection problem. First, check all the connections between the Kinect and PC. The power adapter cable is sometimes temperamental. Then, try plugging your Kinect into different USB ports on the PC. If none of that helps, try if you can find another power adapter cable.

    The above steps typically fix the problem.

Viewing 13 posts - 16 through 28 (of 28 total)
  • You must be logged in to reply to this topic.