Features you would like to see in ArduPilot GCS

I am pleased to report that ArduPilot ground station ( LabVIEW ) team is getting up and going.

Our first objective is to clean-up the code a bit, make it more robust, and easier to add new functionality.

Over time request for ground station features have been mentioned in few threads, and I would like to consolidate them in one place.

What ground station features would you like to see or change?

For example:

1. kml logging : log lat, lon, alt

2. voice synthesis : periodically announce status (way point, alt, speed); announce status through selected flight levels

3. A choice of different graphic layouts, specially for the Horizon Indicator, something that would resemble more real aircraft instruments

4. Change colors to get more contrast on sunny days

5. Label baud rate settings for different GPSs so you don't have to remember (uBlox=38k; EM406 = 57k)

6. Distribute the executable as a .app (not just .exe) so that Mac users can try it.

7. Object tracking - once we have video support

8. Show a 3d model representation of the plane

9. online & offline maps support (google maps, OziExplorer,...)

10. Data logging - preferably user selectable parameters

- add your request

Views: 567

Comment by John C. on January 12, 2010 at 11:27am
I think we need to integrate the "Time of Week" GPS variable into the logging output, so we can build time-based representations of flights.

I think this goes with Doug's comment of log and report EVERYTHING in a human-readable / parseable format that can be converted to KML or anything else.

I personally focus on the plane in the air at this point, rather than the ground station, so full-featured post-flight analysis is more important to me than real-time reporting. I can see where this would change, but post-flight analysis is a very important thing to consider.

Comment by Morli on January 12, 2010 at 11:47am
Two point logging will be better and so pls don't discount real time reporting to GCS with logging support.
Comment by Mike Bakula on January 13, 2010 at 1:14pm
I concur on extensive (and extensible) logging. Post flight analysis is often the only way to see subtle behaviors. Also, consider "pass-through" telemetry -- for example, it'd be nice to be able to use real-time pose data orthorectify photos in real time.


You need to be a member of DIY Drones to add comments!

Join DIY Drones

© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service