- This topic has 22 replies, 11 voices, and was last updated 4 days, 10 hours ago by
.
-
Posts
-
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 setLEDworks as desired. The protocol error is returned when I attemptKinectUtils 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-devwhere the package name should belibdc1394-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. PerhapsPullPackage SteamVRis 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,
JasperSo 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.
I am seeing the issue reports. A core problem seems to be that
PullPackage Vruidoes 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 Vruicommand to hopefully pull those packages successfully. Re-run that command and see if it works.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?The intrinsic parameters file still is not being created. Is it possible that the problem is with my Kinect?
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/
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
- You must be logged in to reply to this topic.