Zbip57
Second Officer
Canada
Offline
|
Well... I take it all back. Almost all. The issue is definitely not something new. It has always been there.
However, it actually might be something that can be corrected via a firmware or app update! I just did a quick test. You should try this for yourself to see what's happening.
Power up your app, controller, and Mini, but DO NOT start the motors!! Pick up the Mini in your hand and, using the app, rotate the gimbal to its full-down 90° position. Now experiment by manually tipping the Mini to different angles watching how the gimbal behaves.
As you tip the Mini forward, the gimbal automatically remains pointing straight down because this is within the gimbal's normal operating range of motion. Tipping the Mini rearward should force the gimbal away from pointing straight down, since that is physically beyond its published 90° range of motion. However, the gimbal actually does rotate further than 90° in order to remain pointing straight down as the Mini is tipped rearward!
Huh?!? Try it, you'll see.
Okay, now try it with the motors running, holding the Mini from below to keep your fingers and face well away from the props. Hold on tight, because the Mini will fight you if you're tipping it to different angles!!! (it would be much safer to remove the props for this test, but I didn't want to disturb the loctite on the new screws.)
With the motors running, and the gimbal again pointed vertically straight down, the gimbal behaves normally as expected whenever the Mini is tipped forward. But, when the Mini is tipped rearward the gimbal will not remain pointing straight down (like it did before with the Mini powered up but motors not running). Instead, as the Mini is tipped rearward, the gimbal jumps forward and remains stablilized in that forward position.
The fact that the gimbal can stay pointed straight down (rotating beyond the published 90° limit) with the motors not running, but does not stay pointed straight down when the motors are running, does seem to imply that something in the firmware could be changed to correct this issue. Verrrrry interrrrresting...
|
|