I'm writing to report a very likely bug affecting at least firmwares 3.1 rc8 to 3.1.2 (), at least for hex X frames. The bug manifests when RTL is the last step of an AUTO mission and RTL return altitude is different from the current altitud
I had what looks like an autopilot-gone-wild where at some point (from stabilize) logging stopped and one motor maxed out (and the hexcopter flipped). I suspect a bug in the newest release of the code (3.1 rc7), but I may be missing something.
Is there a known good way to set the PID controllers on a hexcopter? I moved from an underpowered quad to an overpowered hex and it's (at least by comparison) very "squirrely". Very sensitive to manual inputs, and when I tried to fly it with the defa
Oh, well, yesterday we were doing some routine checks of the auto mode and the quadcopter just went unstable, flipped over and crashed. This happened in calm weather, at the right altitude, apparently (from the logs) right after reaching the first w
It seems that once a landing failsafe sets in, the autopilot should not enter other modes, especially after landing! The following scenario unfolded about a week ago:
Takeoff manually in stabilize, go in loiter mode, battery failsafe incorrectly trigg
I'm having a hell of a time figuring out how the battery voltage and current is supposed to work. Sure, the installation is straight forward and I get numbers that change. The problem is that they are not the right numbers:
Today I tried out "auto" mode after making sure that everything else works well (alt hold, position hold, loiter, land, RTL). Auto works wonderful with a couple of small issues:
- First, if the quadcopter is at rest on the ground (armed, but propel
Today I tried out "auto" mode after making sure that everything else works well (alt hold, position hold, loiter, land, RTL). Auto works wonderful with a couple of small issues:
- First, if the quadcopter is at rest on the ground (armed, but propel