Hi guys,
I uploaded the current version of my QT-based GCS to google code. The sources are available via the SVN repository at https://code.google.com/p/yagcs/ .
Current features:
- Real-time map display (native interface, does not rely on google earth plugin, allows offline access)
- Real-time data plot for distance, altitude, etc.
- Simple presentation of roll and pitch via opengl
- Easily extendible (at least that was the goal) via QT ports/slots
- Should be relatively platform independent due to QT
Also, it now functions as a generator of mission header files which can be loaded via the APM waypoint writer. The GUI, however, is still a bit rough on the edges, meaning it's still lacking quite a few features.
The code only relies one two libraries in addition to QT (one for the data plotting, one for the serial port access), which are itself based on QT. That means you do not need google earth plugins, labview, etc., and all is based on open source. For installation instructions see INSTALL.txt and for more information README.txt.
Would be great to get feedback of course. Also, if somebody from the windows users would try to compile it and tell me if this works, that would be very interesting. Also thanks to the person who pointed me to qextserialport, don't quite remember who initially suggested that.
Cheers,
Andre
Comments
Basically this way one needs to re-implement some functionality that is in GE already but one gains some flexibility (you could do all sorts of overlays of tiles with other things, etc.) Also one could use other map-tile sources. This is really nothing new, as far as I know some other people have done similar things.
what do you mean with this: Real-time map display (native interface, does not rely on google earth plugin, allows offline access)
Can you explain what technique are you using ? its interesting.
Thanks
I wrote the code in the APM_BinComm library. It should be pretty portable; take a look at the test harness code for an example. Feel free to bug me if you have issues there.
You will need awk (standard on Mac OS or Linux, probably part of Cygwin for Windows users) to make changes to the protocol definitions.
We need more work on the APM side to respond to uplink packets, etc. Please file issues - this is something I can probably turn around pretty quickly.
You re right, the best tools is the one you are comfortable with.
bye
Regardless, use the tool(s) that let you build what you need to build.
bye
So I tried the qextserialport from the google code repository but I get errors because of missing header files. Which seems to work is the (older?) version from sourceforge (the not-single-class version). Check out with
"cvs -z3 -d:pserver:anonymous@qextserialport.cvs.sourceforge.net:/cvsroot/qextserialport co -P qextserialport"