Success! make install finishes and reports success, but it seems to have stripped all the path info out, reporting:
There were more before that, but they scrolled beyond the terminal's limit.... Is there a better way of fixing this than replacing each one manually? |
Administrator
|
This post was updated on .
Hi,
I confirm that it is working here too. I committed the fix. The tuning guide is for ROS, thus I created a config file with the same parameters for the standalone app. You can download this file rpi3.ini and load it in Preferences dialog of RTAB-Map. I tested with OpenNi2 driver and a Xtion Live Pro. You can close the Odometry panel if the gui is lagging too much. For the runtime path modified, it is normal. Make sure to do "sudo ldconfig" so that rtabmap can find its libraries when starting. I updated the guide. cheers, Mathieu |
I appreciate the heck outta all of your help! I'll drop one more post in later as a wrap up after I have it all working as expected. TY again!
|
Rtabmap runs and seems to be functional, however it doesn't see the Kinect (1414 or 'for XBOX 360'), despite lsusb returning:
I know the Kinect works, as I can use it with Rtabmap on my windows 10 pc. |
Administrator
|
Try freenect driver. I tested on my kinect 360 (model 1414) and it works.
|
No luck :/
|
Administrator
|
I reproduced the error after a couple of restarts. Maybe it is an usb issue. Try restarting multiple times to see if it can open it. I have only mouse, keyboard and kinect connected to RPI.
|
This post was updated on .
I'll give it a shot. I'm only running the Kinect. The Pi is headless. Meanwhile, I'm not getting any title-bar on the GUI. I have to alt-tab around. Not a deal breaker, but if it's fixable....
No luck so far. Tried rebooting dozens of times. Tried the Kinect in every USB port. Nothing. |
Administrator
|
To see if you can actually use the kinect on your RPI, you may try building freenect library to get their small testing app:
http://blog.bitcollectors.com/adam/2016/01/kinect-support-for-raspberry-pi-using-libfreenect/ If their simple viewer is working, rtabmap should be able to work when built with that version. For the titlebar, maybe it is an option somewhere on RPI to hide/show them by default: https://forum.dexterindustries.com/t/solved-no-title-bar-for-each-window-opened-in-raspbian/3707/6 cheers, Mathieu |
This post was updated on .
freenect-camtest gives me
until I ctrl-C freenect-glpclview and freenect-glview gives me I should probably have said this earlier, but I'm the outlier with regards to statistical probability of 'getting things to work,' in that I rarely do... Sorry to drag you into this void of tech support :/ |
Administrator
|
This post was updated on .
Some related posts:
(low voltage problem) https://github.com/OpenKinect/libfreenect/issues/524 (timing problem) https://raspberrypi.stackexchange.com/questions/74655/erratic-errors-in-libfreenect-on-raspberry-pi-3 Probably it's ok, but just make sure that the kinect's power is plugged into wall. cheers, Mathieu |
This post was updated on .
looks like the timing solution is already applied. I'm scrounging around for another power supply. I'm running the Pi on 2a cell phone wall wort. I'll see if there's a better one around.
Ok, it was the power, at least for the freenect tools. I got video data with freenect-glview! It still doesn't work with rtabmap. I'm assuming I need to compile rtab with that version of freenect, somehow? |
Administrator
|
For reference, my RPI uses a 5V 2.5A power supply. To use freenect built from source, uninstall the binaries:
$ sudo apt-get remove libfreenect* If the other libfreenect is installed in /usr/local, rtabmap should be able to find it with cmake. Before compilation, verify that WITH_FREENECT is TRUE when doing cmake in rtabmap/build. cheers, Mathieu |
This post was updated on .
I found a 2.5a supply, which seemed to help. I'm going to try recompiling with this new freenect.
|
As far as I could get. I believe the latest freenect is installed, but I can't compile rtab now.
I do have libfreenect.h
|
Administrator
|
It should be the one in "/usr/local/include/libfreenect". Not sure why that directory is somewhat not added to include directories. I did try on my mac with latest freenect version and freenect still install headers in "/usr/local/include/libfreenect". RTAB-Map should be used "/usr/local/include/libfreenect" directory. When doing cmake in rtabmap, you should see in the list of found dependencies something like this:
-- Found Freenect: /usr/local/include/libfreenect Another reason is that build cache of rtabmap didn't update properly. Remove everything in rtabmap/build and do a clean cmake so that the correct path (as above) is added for freenect. cheers, Mathieu |
This post was updated on .
I tried 'make clean' but I'm guessing that's not clean enough! :P I'll give it a shot here in a bit!
.. It's definitely seeing it. I'm guessing it was just the already built stuff interfering. Building now. |
Administrator
|
It is a problem with cmake when changing a dependency's location. Cmake keeps in cache some variables (like paths) and won't update them on next cmake. "make clean" only removes compiled files. We could only delete the CMakeCache.txt to force cmake to re-update the cache, though I generally prefer to remove everything in build to make sure everything is re-initialized.
cheers, Mathieu |
Yeah, I can see that now! It's past the half way point, and proceeding fine, so far. I'll keep you posted.
|
It works! In the end, it looks like it was libfreenect 0.5.7 which did it, and I think that building it from source is the only step that still needs to go in the guide! Thanks again for all the help!
Incidentally, the 'no title bar' issue is also resolved. |
Free forum by Nabble | Edit this page |