MP reports “BAD COMPASS HEALTH” every few times I connect. Once it reports that error, the only way I can get the compass to work again is to go into:
I usually need to do that about 3-4 times, then the test will freeze, at which time I can reconnect and everything works sweet again. The lights on the pixhawk go all multicoloured and flashy.
I’ve got an update to this issue. I changed the firmware to 3.15, and noticed the following:
Unplug the external compass and the issue continues to occur
Plug the external compass back in and I have no issues at all (so far)
When I do CLI > test > compass without the external compass, the compass readings are sometimes >1000. This is because the heli main motor is directly above the Pixhawk.
My theory is that AC3.15 doesn’t care about the internal compass until I unplug the external compass, so MP wont throw “BAD COMPASS HEALTH” until its using the internal compass. AC3.2rc3 does use both, so I get the error regardless.
I’ll report this to the devs, hopefully they can confirm.
Started having this issue today, updated to AC3.2-RC12. Bad Compass Health notice on HUD.
I’m using a APM 1.6 clone board with the internal compass trace cut and a NEO-6M GPS/compass, had calibrated compass without issue on AC3.1.5. Tried re-saving compass options, no luck so far. Compass is incrementing 1 degree/second.
Yeah my NEO-6M was toast, the internal connector had come loose from the uBlox chip, it’s an RMA job, switching to another GPS/compass combo fixed this issue.