I was wondering if any programmers would be interested in building a digital logbook that integrates with the cockpit or is built into it.
feature that it would include:
all the standard logbook stuff: date, log number, company, client, pilot, crew, job, task, installation/vessel, custom notes, custom logos, custom headers, custom fonts and formatting, the ability to re-arrange items, and custom background watermarks, signature lines for supervisor, crew, and pilot.
a database of crew, projects, and sites with customizable fields that can be used to populate the report.
overlay options to send real-time notes to the video overlay
automatic power on, power off, log to the report
start dive, end dive logs by pushbutton in cockpit or in the dive log program
programmable buttons in the cockpit and the logging extension for programmable notes, i.e., have a custom text and grab a MAVLink or data lake parameter.
These are definitely ideas we’ve been mulling over, and several are already possible to some extent (albeit with a fair amount of setup required). Agreed that it would be useful to have this kind of thing available in a user-friendly way.
Thanks @EliotBR Looks like some of it has been discussed, the main Goal would be to be able to export a .pdf of the dive log that is formatted well and easy to read to be put in reports or given to clients with the video. The report would include timestamps for all dive notes so it can be easily reviewed and/or used to process the data. Also, it is fairly customizable.
The data logs of the sensors could also be possibly used to make custom charts or graphs, or for later video overlays, but you wouldn’t want the raw sensor data in the dive log, only the information important, specific to the operation.
No problem @rafael.lehmkuhl , I find it’s the best way to get the product to operate the way I would like. If anyone who’s working on this feels free to reach out for a video chat, and I’ll show you some of my workflow and reports to help with ideas on implementation.
Am I correct in thinking you meant a PDF file (e.g. for a pre-formatted report), and not a vector image flow chart (e.g. visualising the notes over time)?
We’ve been discussing something in this vein for some tools we’re working on, though I’m personally more interested in how that kind of thing can be more directly integrated with data visualisation and sharing tools, with reports as a final output once things are agreed upon instead.
Indeed. Short of screenshotting live data plots from Cockpit, that shifts into the realm of data analysis and insights, which I expect would benefit from access to all the mission data, dedicated processing (likely unrelated to the vehicle and the control station computer), and more advanced data synthesis and output capabilities like bathymetry maps, and annotated 3D models and the like
Hi @EliotBR, yes, that’s the correct .pdf. Sorry for the typo. It could also be an Excel file or something else you can edit and modify before making a .pdf, depending on the user’s requirements.
