Issues with Gimble movement order in a mission
Flightplan in question https://app.dronelink.com/duncan-lovett/testing/plan/wD8qPY6osw7ajgifvWiZ/mksKlE3jakzpPZDfUamw
Hello All,
I am having some problems with a simple plan. The idea is that I position the drone looking at the bottom LHS of an imaginary 9x9 grid of an object I want to photograph. The drone then take 3 AEB and moves the gimble up 25 degrees. Repeat the 3 AEB and then rotate gimble up 25 degrees, repeat and 3 lots of 3AEB images are captured. Rotate the gimble down 50 degree and rotate right 25 degrees and repeat the procedure until all 27 images are captured.
For some reason the gimble movements are being done at the start of the mission rather than in between the photographs.
Can anybody help me to fix this.
Also is there any way to make this an on the fly mission that can just be accessed at anytime in the app without me having to manually drag the mission to my current location using the web app?
Many Thanks
d
Comments
3 comments
Update: I have added a rotation command in between each camera command set to rotate the drone horizontally rather than use a gimble command and the rotations are also being done at the beginning of the mission.
I do something similar in taking 2x2 or 2x3 panoramas within a mission. However, I use the Heading component. I would think the Rotation component would work as well but have not used.
With either you should be taking advantage of the "Immediate" and the "Achieved" capabilities offered within each component. With "Immediate" you can have a command list that changes camera settings and/or pitch while the drone is in motion and then with "Achieved" do the actual capture.
Your "on the fly" question gets into Functions which I have not tackled yet but there are a number of videos about them as well as many discussions in this forum.
There is an advanced setting on components that we turned off in the UI called "Exclusive Execution". Right now, the system attempts to execute any components in a list simultaneously by default (non-exclusive execution), but in this case you need to be able to toggle it on. We may consider adding it back to the UI, but until then, David is correct, your only option is to put your camera commands in the achieved section of heading components.
Please sign in to leave a comment.