I had the same symptoms out of the blue also with my pixhawk, recently flashed with new firmware. I redid many times the accel calibration but that would not solve the HUD drift issue. An indeed impossible to take off, my quad flipped trying…
So the only way I solved this was to completely erase and rereflashed the Pixhawk (to be sure I erased everything I flashed an arduplane firmware then the arducopter firmware).
After the reflash, did you reload your previous parameters? From a previous file of your own? Or the standard Pixhawk parameters?
I ask because I’ve also had the same problem. It has gone away (while I had 3.1 installed) but came back with 3.1.2. I haven’t tried erasing and then reloading again, other than revision updates tehmselves, that apparantly erases existing.
The problem, in my case is sometimes worse than others. It will always “flatten out” after several minutes “warming up”, and after several ARM / DISARM cycles.
One should wait at least 3 minutes (more is better) before taking off after first 3D fix. The GPS needs to “settle in”.
@Sky, After reflashing I add indeed to redo every calibration and redo every parametrization… It is a pain indeed.
I just noticed this afternoon that my Pixhawk showed again signs of drift on the HUD… So it is a problem that comes back! I
hope 3DR reads this to find the root cause because it is unacceptable to have to reflash your board every once in a while.
I had my Pixhawk all setup and calibrated. This morning I plugged in the lipo held the safety switch button until it went solid red and tried to arm. It wouldn’t arm, so I plugged it into Mission Planner and the HUD was spinning constantly. Doing an erase and then a reset via the terminal fixed the problem.
This is pretty disconcerting! Has anyone figured out what causes it?
Finally got around to recalibrating everything. All was fine until I did the compassmot calibration. When I reconnected Mission Planner after doing the compassmot calibration the HUD is spinning again. The results of the compassmot calibration was 0%.
It appears there is a known bug related to compassmot and Pixhawk: