At first I put it down to a few corrupted entries, but after a few flights all my logs have looked something like this:
Some of those GPS points must be on another planet, they persist as far out as google earth will let me zoom!
Also, all the NTUN and CTUN entries seem to be corrupted, or not recording what they should. I can't see things like Baro_Alt and WP_Alt.
Any thoughts?
Permalink Reply by Christopher Cooper on November 11, 2012 at 7:33pm I reflashed the firmware and reset the EEPROM before I went flying yesterday. Logs were even crazier this time. The log menu in the CLI gave me this:
12 logs
Log -23659, start 1, end 1
Log -23658, start 1, end 1
The only way to download the log was to dump to the CLI. I've attached what I got, but I can't make any sense of it. The KMZ that this log creates is meaningless.
I'd really appreciate if someone could let me know what might be going wrong here.
Permalink Reply by Christopher Cooper on November 11, 2012 at 7:42pm Apologies, log now uploaded. Had to trim it to <7MB
Permalink Reply by Christopher Cooper on November 16, 2012 at 3:19pm
Permalink Reply by Bill Patterson on November 16, 2012 at 3:55pm Actually, I tried to use APM Log Visualizer, and I got thousands of bad lines.
So something is up.
[Edit] Using my own 2.8.1 logs I mean.
http://diydrones.com/forum/topics/apm-log-visualizer-source-code?co...
Permalink Reply by Christopher Cooper on November 16, 2012 at 6:29pm
Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.24 members
1297 members
79 members
183 members
690 members
© 2013 Created by Chris Anderson.
Powered by
