Open MatzElectronics opened 7 years ago
Completed, in ActiveDevelopment branch
Is there an automated build of the ActiveDev branch? I'd like to use/test this functionality.
There isn't, no. I disabled the auto-build we had because it kept failing.
On Sunday, October 16, 2016, John Leeman notifications@github.com wrote:
Is there an automated build of the ActiveDev branch? I'd like to use/test this functionality.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/parallaxinc/Flight-Controller/issues/31#issuecomment-254044607, or mute the thread https://github.com/notifications/unsubscribe-auth/ANak_iOAiWo8pDusKqH3d06WpLbEGylqks5q0hrsgaJpZM4J_i7c .
I did play with this before I borked my setup. Any way to make this a checkbox instead of a menu option. i.e. you could "enable logging" and stream to a file during the entire flight?
Kind of, but I don't actually know in GroundStation when it's "flying". I could stream to disk when the motors are spinning, but if you disarm / rearm and fly again, do I append, overwrite, or increment to a new file? What would your preference be?
J
On Tuesday, October 18, 2016, John Leeman notifications@github.com wrote:
I did play with this before I borked my setup. Any way to make this a checkbox instead of a menu option. i.e. you could "enable logging" and stream to a file during the entire flight?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/parallaxinc/Flight-Controller/issues/31#issuecomment-254690759, or mute the thread https://github.com/notifications/unsubscribe-auth/ANak_tFVji_rGc1MKg1_AfNiN0qfE92hks5q1XsZgaJpZM4J_i7c .
I'd be okay if it logged the entire time the box is checked - flying or not. Maybe that's just me.
What about naming the files with a timestamp like DDMMYY-HHMMSS.csv or something similar?
I like the idea of a datestamp filename if it's not too much trouble - I would recommend YYYY-MM-DD_HH-MM-SS.csv. Longer, but then when you sort the files alphabetically, it also sorts them in date order.
That could work. What about adopting the naming convention used on seismograms and other geophysical data? YYYY-MM-DDTHH:MM:SS (i.e. 2016-09-03T12:02:22)
Functionality is tested and verified. Will leave open for two pieces: Some reference to time (cycle, phase, anything that time can be inferred from), and default file naming if possible. If it's not possible or easy to do, we can skip that part because the user has the ability to name the file themselves.
Preferably as a .csv format file with the first line being the column headers.