If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

yes, very possible. likely the gyro. but should also check other areas. is the electronics stack secure? have the wires moved closer to the FC? have you inspected your motors closely? have you tried a brand new set of props to rule out unbalanced props?

Thank you for the reply! I have checked the stack and it is secure. Some of the motor wires moved in the crash, flopped out of place, but I just put them back in place, no broken solder. Motors spin up nice in beta flight and I have replaced the props. The FC gyro was the only thing left I could think of.

I'm running 3.1.5 on two powercube setups (one RXCube and one Elite), one on multishot and the other on dshot600. No problems. There's an issue with 3.1.6 Colibri Race firmware, causing BetaFlight unable to recognize the FC. has something to do with soft serials enabled in that release. It's been reported so hopefully this will be fixed in the next release.

On another note.. with the Cube v1 I always suffered from yaw twitches (gyro sensitivity). I installed my Cube on a Martian II 220 frame and had it more worse as I expected. I did a softmount for the motors just to test. Never softmounted motors before and I was curious if it would help. Not much to be honest, lol. Next step was softmounting the whole Cube. That cured almost the whole yaw twitch problem (I think let's say 90% solved). I softmounted it with 2 strokes of really strong double side tape and a piece of thin foam in between. So, frame - tape - foam - 2 pieces of tape - Cube. And that on each side of the Cube.