My Phantom flew away

Hmm, folks keep mentioning the rings to help with the errors, but not real clear on the details and tuning.

But thats a good call, I'll just pull the power on the video and see if that has any impact.

I'm not SURE its the wires. It could have something to do with the motors themselves. Oddly for the most part is pretty cooperative not except if the gimbal needs to look up then boom 1000's of i2c errors. The thing wigs out on all axises.

So Turning off the Video Transmitter had no effect.
I did noticed I had a couple of turns in the wires in the center, so I counter spun it.
Updated the firmware to 2.4 (FPV folks warn against this as like 2.3 ) This allow me to check on a new feature where the controller can use the poles in the motor to calculate position.

I also kicked up the power a bit on the pitch. (which seemed to be the one that was triggering the i2c errors)

So far today it seems to be back to normal. Lets hope it holds, and I can get back to working on vibrations and making sure to get the horizon stable.

Sounds like progress Jonas. Glad it's working for the moment anyway. I didn't expect the transmitter to have any effect, but anything is possible so at least you can take it and any ferrite ideas off the list. Ferrite on the motor/esc side is only to keep EMI out of the receiver. It can't effect the gimbal so I think ferrite is off the table now. Gains are the most likely place to look when things get unstable, unless something is broken. I assume that's what you were talking about when you said you "kicked up the power on the pitch". Do you have access to all three PID parameters or do you just have "P" gain? As you know, low gain tends to make things sluggish and high gains ten to cause oscillation (over correction).

...Tiger