Closed arthurbenemann closed 10 years ago
Might be worth to have a software able to parse mavlink logs (eighter before, during or after flight).
Find attached a picture of my icao log book. it's in german and french only (sorry i live in switzerland ;)
The columns (page 1):
minutes of flight time (as co-pilot)
page 2:
Yep that's exctly the logbook function I was thinking, in Europe commercial operators have to keep just such a thing and are doing it by hand right now. Would be very cool if it could be handled in electronic format.
Ok, now being objective with our devices in mind:
What we need is a table that shows info from each .tlog stored in the memmory. The following can be recovered from that:
I just wonder if parsing the logs when opening the logbook will not take too much time. Maybe we can store everything on the first couple strings at the start of the file, and just generate those when they are missing?
You don't need height basically aviation authorities need the information shown in the glider logbook example above and there might also be a consideration for airframe logging as well. With hundreds of Pixhawks about to hit the streets it might be just the ticket for proving the minimum of 1000 hours required for the DHS testing regime
Is this proposal still under active development? I would be happy do advise on implementation.
@nicksargeant I don't think anyone is active developing it at this moment, because there are a couple of high priority issues to be solved first. But it's on our queue ( we possibly will move this to a online system like Droneshare, making it work with all GCS at the same time).
@arthurbenemann I agree - this sort of thing is an ideal use for droneshare (because of support for all GCSes and easy (optional) sharability with friends). The only thing droidplanner will eventually need is the smallish client nub to upload flight data.
The FAA have an opinion now on log books for UA so best make it compliant http://www.suasnews.com/2014/03/28291/logging-of-unmanned-aircraft-systems-pilot-time/
On 9 April 2014 20:15, Kevin Hester notifications@github.com wrote:
@arthurbenemann https://github.com/arthurbenemann I agree - this sort of thing is an ideal use for droneshare (because of support for all GCSes and easy (optional) sharability with friends). The only thing droidplanner will eventually need is the smallish client nub to upload flight data.
Reply to this email directly or view it on GitHubhttps://github.com/DroidPlanner/droidplanner/issues/331#issuecomment-39997952 .
Thanks Gary,
That's a great resource. I'll put it up on the 'new' '100% javascript' megadroneshare github (which isn't yet public because it is still barely working - should be public within a week or two). For now I'll include the bug on the old-soon-to-be-deprecated droneshare: https://github.com/geeksville/droneshare/issues/3
Oo, you're ditching the Scalatra? Going Node.js or something? Can't wait to see!
Scalatra is really nice, but since MDS is going to kinda be sample code (in addition to a standalone app) - I wanted something accessible to a larger pool of devs (100% javascript/coffeescript).
So I'm using AngularJS (the backend for the api will still be akka etc... - but this new droneshare will be 'just another app' that uses the central corpus/dispatcher). No need for node.js because this particular app will really have no server specific state other than the standard public API (this app is a client of this new rest api). More info: https://docs.google.com/document/d/1ihKneLwA4hXmKS1W2pbG9lty_EAwbmy0giusUwQ8dto/edit
I used angular because I didn't want to say 'first learn jquery and backbone and flot...' ;-)
Great to see such a positive response! As I mentioned on the DP2 Google+ page, I have written (but not yet published) a comprehensive blog post regarding this issue. To avoid clogging up this thread, I have posted this document (which includes some guidelines in different jurisdictions and how we currently comply locally) here: https://docs.google.com/document/d/1S9OhAZsN12wolVLTDkoOdC8_0LLVRK_yAnCcZR4lNp8/pub
Just to clarify, is there appetite to create both a airframe logbook and a pilot's logbook? I am concerned that if it is a solely online solution, this limits the application in the field as a reliable internet connection is not guaranteed. How about a basic app that can sync with droneshare/"the cloud"? If the program/app/webpage could parse .tlogs, half of the required fields could be automatically populated.
wow nick - that's a great doc. I think we should be able to generate a fair portion of these fields automatically and provide a place in the web or device UI for the user to populate the remainder.
@nicksargeant to clarify on the online thing: The API supports both batch and live upload. I think for most GCS they can work similar to how andropilot has talked with droneshare: If a connection isn't available at the time of the flight, the tlog and assocated metadata can be squirted up the next time an internet connection is detected.
I'll close this issue since it has been moved to (mega) droneshare.
Comment by Gary Mortimer 8 hours ago