so ive been fighting this for like two weeks now and im at the point where i just want to throw the whole thing out the window. running a basecam-based 3-axis gimbal on a custom hex, camera is a sony a6500 with a sigma 16mm on it, total payload is sitting around 800g which should be fine for this gimbal according to the specs.

the problem is on the roll axis mostly. after about 3-4 minutes of flight it starts drifting clockwise, like maybe 2-3 degrees, doesnt sound like much but its enough to ruin a shot. ive rebalanced probably five times now, tried adjusting the PID on the roll motor, bumped up the power a bit. it gets better for a flight or two and then starts doing it again. temperature maybe? its been pretty warm here lately.

anyone dealt with this kind of slow drift on a brushless gimbal? wondering if its the IMU placement or if the motor is just getting too warm and losing torque. open to any ideas at this point honestly.

had almost the exact same issue on a movi clone i was running a couple years back. turned out the IMU was picking up motor vibration and it was slowly confusing the horizon reference over time. i ended up wrapping the IMU in some foam tape and moving it about 15mm further from the tilt motor and it basically fixed it. worth checking where yours is mounted and whether theres any direct contact with the frame.

also the temperature thing is real ? brushless gimbal motors do lose holding torque as they heat up, especially if theyre already near their rated load. 800g is probably fine in theory but if your balance isnt perfect the motor is working harder than it should be the whole time and by minute 4 its just tired. try balancing it so the camera rests dead neutral with zero power applied, like properly neutral not close enough.

might be a dumb question but have you checked the encoder calibration recently? i had drift issues that drove me crazy and it turned out i just needed to redo the motor calibration sequence in basecam after i changed lenses. apparently the weight distribution shift was enough to throw it off. probably not your issue but took me way too long to figure that out so figured id mention it