The GPS+compass are mounted on a mast. There are 2 issues I am experiencing:
While configuring the compass, the Mag1 reading goes from id:0 0% to 100% and then back to 0%. It starts to reach 100 again. This loop continues. video-clip
What does this mean? is it configured? when do i click the Accept button?
If by chance the compass is configured, which i identify when there is NO “prearm: compass not configured error”, I am getting one or both of the following randomly:
2.1. Prearm: Error compass variance
2.2. Prearm: Check mag field : (958 max, 875, min185) (This needs recalibration as per link but i get issue #1 then)
I have experienced this same issue both on Copter and Rover. It just happened recently with Copter using one of the mRobotics SAM GPS/compass modules with the full size ground plane. I swapped out the GPS/compass module for another of the same model, and it calibrated immediately. Going back to the one that refused to complete, I changed tolerance to relaxed, but it continued to cycle through indefinitely. I sent the module back to mRobotics, and they claim it is fine when they test it. I’m running the latest stable version of copter (4.1.6 I think - latest when I was setting up the copter). The module that worked was mounted in the same copter with all the same hardware and wiring.
When we experienced this on Rover, we had a backdoor into the PixRacer through a secondary controller (Odroid), and using MavProxy we were able to initiate compass cal, and on that hardware setup it worked. I have no idea why sending compass cal commands through Mission Planner and MaxProxy would be different. Those were much older versions of FW.