That explains what I'm seeing. I got a little confused by the documentation. As long as it keeps appending to the log buffer, multiple paths/flights will all be there. I'll do a couple of checks this afternoon.
Knowing this, my approach would be just to export to csv or kml and then edit out the actual flights for now until there's something more elegant. On Sat, Jul 16, 2016 at 12:03 PM, Keith Packard <[email protected]> wrote: > Tim Robinson <[email protected]> writes: > > > I just received a TeleGPS unit and am starting to do some tests before > > flying it. Most everything has worked great except I seem to be unable to > > change the maximum log size. It shows as configured for 1984 kB (1 > > flight). > > I changed the TeleGPS firmware so that it just keeps appending data to a > single log buffer instead of the separate flight buffers present in our > flight computers. There is 2MB of storage on the board, of which 64kB is > used to store configuration parameters, leaving 1984kB of space for the > log. > > I did this because several fliers noticed that simply power cycling the > board a couple of times while testing things would "fill up" all > available log space on the device, leaving it unable to log data for the > actual flight. > > > It records flights (simulated by putting in my pocket while going on a > run > > around the neighborhood. I can download the flight and mark it for > > deletion. Once I've done this, further attempts to download are met with > a > > dialog "No flights available on serial_num". > > Right, there should be only a single "flight" on the device at any time. > > > At this point I still can't change the maximum log size. I'm using the > > TeleGPS app 1.6.5 and I've updated firmware to telegps-v1.0-1.6.5. > > Given the above description, do you think the firmware is doing > something wrong? > > I'm thinking of how I might change the ground software to take the > single log and split it into sensible "flights"; with GPS date > information, I should be able to identify sections of the log that are > close together in time. > > -- > -keith >
_______________________________________________ altusmetrum mailing list [email protected] http://lists.gag.com/mailman/listinfo/altusmetrum
