I just managed to get APM Planner RC2 running on my Raspberry Pi. I have not tested connecting to an APM yet but clicking around in the interface is much more responsive than i ever thought it would be.
Here are a brief instruction:
- Raspberry Pi with 32 GB SD card loaded with Raspian
- Added a 4 GB swap per the instructions here: http://jermsmit.com/my-raspberry-pi-needs-a-swap/ (the compilation will run out of memory otherwise)
Install the required packages:
sudo apt-get install phonon libqt4-dev \ libphonon-dev libphonon4 phonon-backend-gstreamer \ qtcreator libsdl1.2-dev libflite1 flite1-dev build-essential \ libopenscenegraph-dev libssl-dev
Clone the repository in your workspace:
cd ~/workspace git clone https://github.com/diydrones/apm_planner
Build APM Planner:
cd ~/workspace/apm_planner qmake-qt4 qgroundcontrol.pro
make
Run APM Planner:
./release/apmplanner2
Comments
@Joe: If you setup a cross-compile for RPi and document it I can setup an automated build and make it part of the AP2 releases. That would save me some time investigating (maybe, if interest I could even look at a BBB version ;) )
@Bill Bonney
Oh, thanks, Bill. The thought just occurred to me last night, after a day of build wrangling on the pi!
Willing to bet it builds in ~1/2 hour on a properly configured PC running the cross toolchain.
I only really bumped up my swapfile size for the final link stage, so it might've been quicker if I'd bumped it earlier. :-D
I'm wondering how to ensure that the build env on the PC and the pi are absolutely synched. My Pi 2 (x2) arrives Friday, so unless it's markedly faster building there, I might try this!
I do think with just a touch more speed, and a way of displaying the MP screens properly (possibly some sort of X windows Oculus overlay mechanism and suitable pointing device) that it'd be possible to have a portable, low power, wearable GC setup. Combine that with easily selectable FPV mode thru the Oculus, or perhaps a pi/fpv transparency function, and we'd really have something useful for the flying field!
@Joe et al. Great work on the RPi build. Has anyone attempted cross-compiling on the desktop first then downloading. e.g http://hertaville.com/2012/09/28/development-environment-raspberry-...
Success!
Got it to build on a Pi 1! It does require some mucking around to increase swapfile size, to get the build to complete, and also to get it to boot up quickly, and also a fast, big, SD card is helpful. I actually got it to connect to the UAV, and put in some waypoints on the map. Not nearly as crisp as on the PC, but it's barely usable. I'm hoping it's quite ok on the Pi 2.
Oh, woops, I should have noticed. Droidplanner for Android. Different thing.
Although, I still think it's worth a try to compile it for the RPi2.
Thanks RC Tech!
From the TV stick specs, looks like if it works passably there it might just work passably on a Raspberry Pi 2 (Quad core Arm A7).
Any luck getting it to build on the TV-stick?
It was not a viable solution to run this on a Pi. It was painfully slow. I am fiddling with Android TV sticks now, trying to get Droidplanner for Android to work. http://www.ebay.com/bhp/android-tv-stick
This project can no longer be built. I tried with the latest version of Mission Planner, and also grabbed the archived 2.0.0-rc2.
It would be great to be able to try this out. Perhaps the RC Tech.se or Magnus might want to re-compile the thing from current library installs? I'm not familiar enough with the current QT (last work I did with it was in 2009) to figure out what the problem is.
Should be 57600....?
Hi - thanks for this - used the instructions to install it on my server running lubuntu 12.04 - worked a treat.
Will have a go on the BeagleBone later on.
-
1
-
2
-
3
of 3 Next