Comment by Paul Mather on October 28, 2010 at 1:29pm

James, is this the official protocol for APM? Can you post a link to dronegcs as well?

Comment by James Goppert on October 28, 2010 at 1:49pm

Yes, this library implements the official protocol for APM. What makes it useful is that it depends on the arduino based APM_BinComm library. So as protocols are added to the micro-controller side to fully flesh out the binary protocol as described on the wiki, all we have to do is rebuild the library and the svn external link to APM_BinComm should take care of the rest. It wraps the Arduino code for host-side c++ by defining the Stream class as a Boost Asynchronous Serial port for host-side C++ programs. And boost is cross-platform so the library itself is cross-platform.

dronegcs is a work in progress by me and my lab mate. It uses qt and osgearth to produce a very visual 3d/ terrain rendering ground station. We also have kept the cpu consumption down by limiting the frame rate for the 3d graphics to around 30 fps. We are working right now on the point and click interface in 3d. Currently we can add, remove waypoints etc. We still are working on click and drap for moving them. It also uses the vehicle attitude and position information to render a 3d vehicle model that can be scaled. The idea is basically to turn the ground station into something with more of the look and feel of a real time strategy game to make multiple vehicle/ formation control an easier task.
http://oooark.git.sourceforge.net/git/gitweb.cgi?p=oooark/dronegcs;...

Comment by Paul Mather on October 28, 2010 at 3:19pm

Thanks for posting this. I'll work on implementing it shortly in my GCS as well.

Comment by Andre S on October 31, 2010 at 1:05am

Thanks, the last version seems to work for me and yagcs uses it now. Nice that it automatically pulls and patches APM_Bincomm. One minor comment though: it seems that the compiled library ends up in the subdirectory src/1 (that is the number 1) where I would have maybe expected it in lib/ or something like that. Not so important, I was just wondering whether there is a reason for this.

Comment by James Goppert on October 31, 2010 at 10:41am

There was a line in there that set the library build path. It really didn't make since so I just took it out and left it as default, which leaves it in src. If you run make install it will install the libraries to /usr/include/ardupilotmegacomm. I repackaged this change as 0.0.2 so you should just be able to install that package, or run make install after you build the source.

Comment