Open Island

I have had series of problem when installing pymavlink and mavproxy onto BBB... There is a link for communication Raspberry pi via MAVLink: http://ardupilot.org/dev/docs/raspberry-pi-via-mavlink.html it was talking about connecting Pi through tele2, and set up a mavproxy on pi for further development. Lot of installion of mavproxy on arm or CC refer to this page, So I take my BBB and following the installation with pip, it always comes to a gcc failed..... But, I tried a Pi2 with Raspbian Jessie, did the apt-get update, and apt-get install dependencies, then you need to first run pip install future...  if you don't, pip install pymavlink will stop with error: no module named future. even you saw it down load a version of future.... after this then you start:  pip install pymavlink pip install mavproxy or eventually pip install dronekit, all can be done. sudo apt - get update #Update the list of packages in the software center sudo apt - get install scr

I use a 8G uSD with debian image of 4G, when I run mavproxy, it shows not enough space, since the whole system is at 3.3G some thing.... I checked the beaglebone web site about expanding sd card, this is not correct... http://elinux.org/Beagleboard:Expanding_File_System_Partition_On_A_microSD Another link does the job: http://dev.iachieved.it/iachievedit/expanding-your-beaglebone-microsd-filesystem/ There are a number of tutorials out there that show you how to expand a BeagleBone Black microSD-based filesystem. Most of them were written, however, when the delivered image from  BeagleBoard.org  contained two partitions: one a FAT partition, the other your standard Linux partition. The aim of this post is to show you that indeed, you have nothing to fear expanding your BeagleBone Black partition even though there is only one (if you’re like us you get a little nervous when someone asks you to delete the partition you booted in). Let’s get started. We’re using the  Debian

Before Going on to beaglebone, I wish to test the following: 1. connect a pixhawk telemetry 2 through a FTDI uart to usb to my windows PC. 2. run a MAVproxy on wondows 3. connect mission planner(on local PC) to pixhawk through MAVproxy 4. same as 3, but from another PC in the same network. I have done this with dronekit-sitl on PC, according to the dronekit-sitl paper, connect 2 link to it can cause unstable. For multiple connections, it recommands MAVproxy. When I first started, I have install MAVproxy through windows installer, as well as pip through command line.(I also use python on PC) double installation cause the program to run very strangely, so I uninstall MAVproxy from windows uninstaller, and pip uninstall mavproxy through command line. Then run again the windows installer again from this page: http://ardupilot.github.io/MAVProxy/html/getting_started/index.html MAVproxy starts to show correct information....but I still can't get local or remote GCS connecte

Drone Kit is python library to communicate with APM, pixhawk through MAVlink. As I understand this is the tool that they used on solo, which has a iMX6 on board as companion computer and talk to a special version of pixhawk. Here I want to install droneKit, and MAVproxy on beaglebone, for doing something stupid on it... Solo is latest "last?" version of 3DR, but the company lost market to DJI, cause a large layoff in 2016, so infact the design was for 2016. it can't compete with DJI's later model, such as Marvic which also have a companion computer but have more cameras for optical flow control, make it a super good product. Saying that, solo is still a good choice for my project, for following reasons: 1. it's still a open source, which means lot of examples and possible to modify.. 2. it has already integrated a companion comoputer, and a controller, so you can skip all the wireing and keep your drone net. 3. Document of development is by far, the most c

I still have few beaglebone on hands, including the white beaglebone A6A, and later beaglebone black, 2~3 beaglebone green. The most common firmware was angustrom in the A6A, but later version(beaglebone black and green) it becomes debian, which is more similar to ubuntu. The good thing of beaglebone is that it's designed with TI industrial application targeted arm, so it has lot of UARTs, where I can attached uart interface. There are a lot of boards comes and goes these years, Pi becomes a fast changing version, which also progess the most. Beaglebone is not popular as Pi, and it's not the most powerful one, but it's still supported and updated....Old dog with new trick. checked the web: https://beagleboard.org/latest-images The latest one debian is 8.7, and one version for all colors of beaglebone, white, black, green, blue....even industrial... and to flash your finish system to eMMC, only need to modify the uEvn.txt, no more need to start from another image. T