@elkayem wrote:
I just upgraded my software to Copter V3.4-rc3 (e2a9772c). My previous version was Copter V3.4-rc1 (dfa90d29), pulled back in April. I'm running the BBBMini version (on a Beaglebone Black), and have had no issues with GPS until now.
On my flights from today and yesterday, I cannot enter Loiter mode, and there is no GPS telemetry in my log file. And yet when I bring my copter home and connect to it through Mission Planner via Mavlink, the GPS is clearly running, and if I collect a small amount of data, the GPS data is clearly there.
I have performed the above exercise twice (yesterday and today) and it is perfectly repeatable, i.e., works at home but not in the field. If I can figure out how to post the log files, I will.
It may not be related to V3.4-rc3. I also updated my Linux Kernel, and notice now that I need to put a 30 second delay at boot-up before starting ardupilot, otherwise it doesn't even recognize my spi devices. My next test will be to go back to rc1 and revert my Kernel, and see which combination works.
My theory is that Arducopter isn't immediately recognizing my GPS when it starts up (maybe Linux is taking a while before the device appears), and doesn't check again after it becomes available. If so, is there a setting I can use to get Arducopter to continue to look for the GPS?
Has anyone else encountered these issues on a Linux platform? I'll post what I discover too as I continue to troubleshoot.
Posts: 5
Participants: 2