Hi gang; I also reported this kind of thing a month or two ago on the irc channel. In my case it was flight no. 9 on my TeleMega.
Note: IF I recall correctly: I erased the *other* flights (and kept no. 9 extent in the memory) that were on the unit. And then recorded a successful flight no 10 earlier this month. I will send along the flight file along with the telem file to Keith post haste. Best regards; Bob F. On Sun, Sep 20, 2015 at 2:22 PM, Keith Packard <[email protected]> wrote: > Steven Saner <[email protected]> writes: > > > Hi: > > > > I flew my Telemetrum v1.2 system today with the Altus Droid connected to > > the Teledongle via USB. > > > > The flight was good. Went to 6887ft and only had about 1/4 mile to walk > > for recovery. > > > > A couple issues though. > > > > The altimeter did not record the entire flight in the flash memory. Only > > the first 75 sec of the flight was recorded. The entire flight time was > > several minutes. When I go to save the flight data using the AltOS > > application on a computer the download errors out with: > > > > "Flight 8 download error invalid checksum at 0x100000 Valid log data > > saved". > > > > So, this kind of makes sense because I had the Max Flight Log Size set > > to 992 (2 flights). So, if I understand right, it would use only the 1st > > MB of the 2MB storage for the flight (no other recorded flights). And > > 0x100000 is the 1MB location where the data probably just ends. > > 1MB should be able to store about 40 minutes of flight data, so there's > something amiss here. > > Can you send whatever log file you've managed to save to me so I can > take a look at it? > > > But at this point in time I can find no way to actually delete that > > flight from the altimeter and also the Maximum Flight Log Size selection > > in the Configuration panel is greyed out and disabled. I don't remember > > for sure, but does the UI normally give the option to delete after you > > have downloaded? Since it is erroring out, I'm not getting that > > option. > > You can resize only if there aren't any flights still saved on the device. > > > What am I missing here? Do I understand the cause of the problem > > correctly, or should I be at all worried about a flash failure? > > I'd suspect some kind of firmware bug frankly. 75 seconds of flight > time, of which presumably 60 were probably descent would yield a log > file of: > > 15 seconds ascent * 100 samples per second * 8 bytes per sample > 60 seconds descent * 10 samples per second * 8 bytes per sample > > 16800 bytes of flight log. > > > The second issue is that during the recovery phase, the Altus Droid > > application as it was giving me the voice updates kept saying "Speed > > 0.0" and never anything different than that. So first question is, is > > that supposed to be vertical speed or horizontal speed? > > We only report vertical speed so that you can verify if the recovery > system has deployed as expected. > > > Lastly, I know that the Altus Droid saves the telemetry data to the > > Android file system. Is there any way to then get the droid app to load > > one of those files and replay it like you can with the AltOS computer > > app? Or at least get the flight stats? I would find it useful at times > > to be able to load one of those files on the phone and at least see what > > the basic flight stats were. > > You can take the telemetry file from the AltosDroid app and replay it on > your computer. AltosDroid isn't that fancy (yet). > > Please send along your log file and let me see if that has a story to > tell; if there's a firmware problem, I may be able to use that to > reproduce it on the ground too. > > -- > -keith > > _______________________________________________ > altusmetrum mailing list > [email protected] > http://lists.gag.com/mailman/listinfo/altusmetrum > >
_______________________________________________ altusmetrum mailing list [email protected] http://lists.gag.com/mailman/listinfo/altusmetrum
