I've been getting inconsistent results with the on board logger. My last flight was recorded just fine with the ground station, but APM never recorded the flight. The weird thing is that I had cleared the logs prior to the flight and when I tried to download the log, I got 2 completely worthless logs and a 3rd one which was just waypoints from an older flight.
Any suggestions on a procedure to make sure each flight get's logged properly?
I ran into the same issue again today.
I had a great flight this morning with the onboard logger working just fine. Landed, downloaded the log, cleared the log. I then turned everything off for a few hours.
I went out again this evening for a quick flight. Loaded a new mission with 2 waypoints. Landed and there were no log to be downloaded again!?! Furthermore the plane could not hold an RTL circle and did not come back from it's intended waypoints. I had to fly it back manually. I'm not sure if those are related issues or not.
Attached is the ground control station log of that flight.
I'm having similar issues with on board logging. I have yet to successfully download log files from APM via USB.
I flew today and when I tried to download from the tool it says there are no logs but from the command line i get the following.
ArduPlane V2.70] logs
ATTITUDE_MED GPS PM MODE CMD
Log 1, start 1, end 382
Log 2, start 383, end 528
Log 3, start 529, end 779
Log 4, start 780, end 1013
Log 5, start 1014, end 2091
Log 6, start 2092, end 2119
Log 7, start 2120, end 2124
Log 8, start 2125, end 6313
Log 9, start 6314, end 6316
If I use dump it seems to write the log to the CLI but it takes a very long time and I'm not sure it contains all data?
I too could really use some help on this from some of you that are more knowledgeable in this area. Please!
Are you running Mission-Planner on Windows or on some other OS? (Or in a VM?) I found that Mission Planner drops a bunch of characters when run inside of my VM or under Mono.
My 'fix' was either:
a) Use tlogs captured 'live' - they have more data anyways
b) Use a terminal program to capture logs to a file then edit the text file so it would be acceptable