Hi all, I was using an Iris quadcopter with 3.1.2 and was using a Raspberry Pi to use mavproxy to send autonomous commands.
Due to some issues, my team decided to upgrade to 3.2.1 and recalibrate. Now when I would run the ~May_2014 git version of pymavlink + MAVProxy, there is no information when connecting, no printout, and it just enters the "MAV>" terminal where commands don't do anything.
So I looked up when ArduCopter 3.2.1 was released (Feb 11 2015), so I downloaded ~Feb_25_2015 pymavlink/MAVproxy and I would get a "attribute error, 'x25crc' has no attribute 'accumulate_str" error. So I changed the extra crc if statemnt to false, and now I'm back to square one where it just enters a "MAV>" terminal with no firmware printout, etc.
Could someone help me out with where to go from here? I've tried many versions between May 2014 and current versions. Thanks.
Replies
If you're just getting the "MAV>" printout (and nothing else), that indicates that MAVProxy isn't able to connect with the Pixhawk's telemetry stream.
Are you sure you're using the correct port and baud rate? I believe the default baud rate was changed a month ago. See http://tridge.github.io/MAVProxy/quickstart.html for details on the startup options.
Thanks for the reply. I've currently moved away from MAVProxy and am just writing my own python script from importing mavutil.py. So far on x86 it's working well (I'm connecting and parsing messages), but on ARM (RPi) it's giving an x25crc attribute error. I'll try to figure it out once I have it functioning on x86.