Thanks for the great tool, Obelix! Just tried it myself to diagnose my drone after a minor motor issue.
A few thoughts:
* It's not at all clear to me how to pan and zoom in the graph. Left-clicking and dragging a box seems to zoom in, but I can't for the life of me figure out how to zoom back out. Panning with the right mouse button seems to work some of the time, but sometimes the scale along the bottom just says the same time over and over, and panning doesn't seem to work. I also got popups (something about "no data point" or similar regularly while trying to use the mouse buttons to pan or zoom.
* There is a LOT of data available that you're capturing, but except to an expert, it's difficult to tell what most of the variables are. Perhaps you could group a handful of key variables useful to beginners for diagnosing common problems on a single tab (say: altitude, heading, roll / pitch / yaw, engine RPM, engine temp if that's monitored [I'm not sure]), and give them friendly names? Maybe make that the default tab?
* There are a *lot* of tabs to choose from, and it takes quite a while scrolling between them with the arrow buttons. Perhaps a drop-down list of tabs would be quicker?
* The keyboard controls don't seem to function if the flight button pane doesn't have the focus. (Eg. I accidentally bumped the graph pane while my drone was flying, and then couldn't control flight while using the keyboard, until I first clicked on the flight button pane). Might be nice if they worked regardless of which pane had focus.
* I hit a problem whereby the altitude controls didn't seem to work, which caused me to hit my ceiling and crack the indoor hull in the process. (Not the end of the world, I have EPP tape and it was easily repaired). I was using the keyboard controls and the correct pane had focus; the Up control worked and my drone rose, but when I pressed the down button instead of descending, it rose more and hit the ceiling before I could react and press Shift to land. I was flying over an almost perfectly level surface (carpeted floor) and the only thing on the floor was the drone box to give a good target for the camera, so the altitude sensor shouldn't have caused the sudden climb. Likewise I wasn't close enough to the ceiling to cause a problem when I pressed descend -- it was still a good 4-5 feet above the drone at that point. It definitely happened at the moment I pressed the key to descend, and I definitely had the right key, so I can only assume that under some circumstances the wrong command can be sent to the drone.
Just a little feedback for you -- I'd love to see you develop this further, as it would be very useful to have a good diagnostic / telemetry tool for troubleshooting drone problems.
Oh, and one last thing, I haven't tried but was curious. Do you know if your program can read log files captured by Meavydev's ARDrone Flight on Android? (http://meavydev.co.uk/ARDrone.html
) My desktop PC doesn't have wifi, and my laptop's screen is near-invisible outdoors, so it'd be great if I could capture logs of outdoor flight with my Android tablet, then view them in your app...