I've been trying everything I can to get the logs off my APM2. I erased the logs with the Logs > Erase command in the CLI. Flew for 3 minutes or so, connect again and then when I go to the terminal tab of Mission Planner 1.1.40, I click Log Download I get this screen:
It shows no logs to download which clearly there are (see last image). It then starts showing the text as above by itself and the amount "Done" increases incrementally for ever if I let it. it got to 27000+ yesterday after about 45 minutes!!
The terminal screen shows this:
If I Type "logs" in the CLI I get this:
it dumps the logs but to where, how can I view them or save them?
Can someone please tell me WTH is going on?
Replies
I´m running Mission Planner 1.1.73 and got exactly the same issue. Could you please advise me how I can get the logs to show up?
Now it works fine for me with the new Mission Planner.
Thanks
Sorry!! Log download problem is still there, it worked fine on a small log (2 minutes flying) but after having flown 6 minutes I get this accompanied by odd beeps from the PC's internal speaker.
EDIT: An APM reboot and reconnect seems to have solved it, log available again, (I'll shut up now)
Logs now visible and downloadable with v1.1.41
Thank you Michael, Chris, yovio and any others involved!
D:\WORK\C_SHRP\del_at_will\ArduinoCPP\ArduinoCPP.csproj: The project file could not be loaded. Could not find file 'D:\WORK\C_SHRP\del_at_will\ArduinoCPP\ArduinoCPP.csproj'.
Thanks
I manage to get it working with custom Mission Planner. Problem lies with the waiting time needed by mission planner before sending 3 new line command. Mission Planner 1.1.40 wait for 2 seconds before sending 3 new line command. I guess 2 seconds is not enough for APM2 to boot up and ready to accept command.
I increase the waiting time become 4 seconds and it works.
do you have a gps attached? i dont see that in the log window
Issue posted > See here, please add confirmation comment if you have the same problem
I am facing exactly the same problem. Cannot download logs. CLI otherwise is working fine. Guys let me know once you know what the issue is.
Thanks
Exactly the same on different PC with different cable (Also Win XP)