I’m on Ubuntu 15.10, using the most recent APM Planner 2.0 for the latest Ubuntu stable release.
I am added to dialout and tty groups, and both serial ports in general and the serial port on my Pixhawk work fine in i.e. picocom. Dmseg does not give anything untoward that I can see.
The thing works fine in Windows.
However, when I start APM Planner 2 and click Connect, it shows the connect icon as connected, but nothing happens and no data gets exchanged. No error messages appear on screen or in the terminal. It detects the serial port just fine, it just doesn’t succeed in communicating.
Similarly, it cannot determine the Pixhawk appropriate firmware, even though it can detect the pixhawk, and that it is a pixhawk, on the firmware flash screen.
I believe I am having the same issue as OP. I’m on Archlinux if that makes a difference.
[li]Plugging in device shows up as /dev/ttyACM0[/li]
[li]APM Planner v2.0.18 was not able to detect my firmware version, not able to update[/li]
[li]APM on Mac, was able to update firmware successfully, that ruled out hardware issues[/li]
[li] Found this post and compiled from GitHub, APM Planner v2.0.19 is able to update firmware successfully on Linux - making progress[/li]
[li] Able to access APM via APM Planner terminal and minicom on /dev/ttyACM0 at baud 115200 [attachment=2]serial.png[/attachment][/li]
[li] Still not getting any APM data such as GPS fix or orientation [attachment=1]no_data.png[/attachment][/li][/ul]
I have attached apm.log as the stdout from APM Planner if that helps. The only thing info I can see is the mode of APM. Not for sure if that is just a default for connected to serial. I’m not seeing any other data or messages coming in.
It looks like my issue is not the same as OP. My Pixhawk doesn’t work on OSX, only the firmware update. My issue is related to solid red LED meaning the Pixhawk hasn’t properly booted, throwing some CRC failure. I’ve posted a new thread on this specific issue.