Forum Replies Created
-
Posts
-
Fortunately, there is a core dump and more information is available in there. Assuming you start the sandbox (in a terminal window) like “./bin/SARndbox”, then please post the output from
gdb -q ./bin/SARndbox core.If you do not see message like “Core was generated by…” and “Program terminated with signal 11…”, then type
whereat the “(gdb)” prompt.Please post the gdb output that starts with “Core was generated by…”. The info should help point out something for further checking.
You’re welcome.
…RawKinectViewer opened without that.
I can see why you thought the directory was not needed. This is a quirk to the way the Sandbox software is installed.
RawKinectVieweris a system-wide install, whileCalibrateProjectoris only under the compiling user’s home directory.Welcome to the forum.
The response means that either the utility was not created in Step 5 (was there an error?) or your entered text does not match Step 11. Make sure you follow Step 11 as it is written since the directory is an important detail.
If that does not work, please post the output of
ls -lfrom the same command window. This will show all the files in your current directory with some metadata about the files.Could you give more details about how you are creating the secondary view? Are you using
SARndbox -remoteandSARndboxClientor another method?A few ideas…
I have previously made the mistake of editing the wrong BoxLayout.txt file. Make sure the file you’re editing is the same one SARndbox is reading. Try very large changes (i.e. 20-50 cm) and see if there is any change in the running sandbox. If not, it’s the wrong file.
Try cleaning the Kinect IR lens.
Your Kinect may have failing pixels “on the left side”. Physically reorient the camera so that the bad pixels view outside the box perimeter.
I cannot find a copy of that particular poster, just photos and videos in which that poster appears in the background.
But, user “Stan” (smcshinsky) on the old forum created a similar poster
that is still available at http://mastermapper.com/webmaps/Water%20shed.pdfThe Wayback Machine says the filename for the “Shaping Watersheds Augmented Reality Sandbox” publication was “Shaping-Watersheds-AR-Sandbox-Facilitation-Guide.pdf”. Searching for that filename gives a few likely results. Is this the guide you’re looking for?
Could you post the full output for
bash Build-Ubuntu.sh? There will be detailed info in there that may point to the problem source.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 hubEvery 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.
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?
@solanic Sorry, I missed this post before.
What output do you get with
sudo /usr/local/bin/KinectUtil list?A couple quick ideas:
- Disable fast boot in BIOS.
- Disable secure boot in BIOS.
- Do you have an EFI partition on the SSD? Files needed to boot will be placed in there.
- Can you boot from the USB Drive and run “Boot Repair” on the SSD?
To directly answer your question: from an API and ABI perspective, there is very little difference between Linux Mint (LM) 19 and LM 19.3. The Sandbox build and install instructions should be the same for both versions.
Generally in Linux software, major version changes may contain breaking changes. (See the recent threads on installing the Sandbox software on LM 21.) But, minor version changes should only contain fixes. Often, a binary compiled for LM 19 will run on LM 19.3 without needing to be recompiled.
On a separate note. In previous years, laptops were not recommended for running the Sandbox software due to the fast graphics required. With the speed of recent laptops this may not be a problem. But, keep in mind that if you are not happy with your Sandbox performance, you may want to change to a desktop computer.
