These are chat archives for dronekit/dronekit-android
COMMAND_DENIED). The interesting bit is that when it gets stuck, I can fly around in Loiter and the camera always tries to point at the last location. So I stop following over my front yard, the gimbal is stuck, and everywhere I fly, I'm pointing at that exact location (as long as I'm panned so it can point at it). So it looks like the last ROI is being saved somewhere. I thought of calling
ControlApi.goTo(null)to perhaps set the last ROI to null. But looking at the DK-Android code, that would just cause a
NullPointerException. So, still on the hunt.
shotManager.py:enterShot()). While in there processing
APP_SHOT_NONE, it calls
del currController, kicking it out of scope so it's garbage-collected. I'm no Dr. Python, but that seems to imply that Follow is suddenly killed in that case, after sending the last
SET_POSITION_TARGET_GLOBAL_INTcommand. So that seems like it would be leaving the last ROI in place, doesn't it? I know from experience that the only way to make it _stop staring at the last ROI is to either enter a different shot, or power-cycle the Solo. Seems like there should be some kind of
shotManagercould before killing the current shot, giving it a chance to clean up after itself. Just a thought.