I’m running APM Planner 2.08 (7342ec34-2.0.8) on a MacBook Pro Retina Late 2013 on OSX 10.9.2.
Recently got a PixHawk and used APM-Planner to flash the latest ArduCopter to the PixHawk.
While configuring and testing the system I’ve noticed that APM-Planner connects fine via MavLink at 115200 (appears as usbmodem1).
But while on the Terminal tab, trying to connect to get logs from the PixHawk (via the same USB) with a fresh power cycle of the PixHawk, it’s impossible to connect at 115200 on the same connection. Reduced the connection speed for the usbmodem1 to 57600 and it works sometimes…When it works and I try to pull logs from the PixHawk, I notice that it is extremely slow and APM Planner seems to give up pulling the log files. Also the byte counter goes to values much higher than the real size of the log file.
I’ve resorted to get the microSD card out of the PixHawk and copying the files to the computer. If I may suggest as an improvement, just “pull” the files straight from the PixHawk, and do any post-processing after the files are on the computer.
In my case using Win-Mission Planner is not an option because even running inside a Parallels VM, my laptop has a retina display and Mission Planner is completely unusable because of the way that the graphics elements display.
Any suggestions on this issue of speed of the connection for terminal, and the problem with the logs ? At this phase I have all the logs turned on so, my logs are “somewhat” big…
Although nobody replied I kept trying to see what was going:
Flashed 3.1.3 to the PixHawk and the problem persists
Much larger log file than the original, unable to connect the terminal at 115200, only at 57600 and unreliably - note - Mavlink connects fine at 115200, and very very long download times. On this screenshot which I’ve managed to download one log file after several attempts where APM planner gave up - ie stopped at various byte counts. It took almost 15 minutes to get the log file. And no, it’s not the Mac disk, it’s a 1TB SSD…