MA2 Type Camera Command Not Working
Using Beta Build 136 on IOS - V2.0.1 - with my Mavic Air 2
Attempted to execute a simple camera List component in a Plan:
Stop Camera Capture
Set Mode to Photo
Set Type to AEB
Set AEB Count to 3
Start Camera Capture
Mission executes successfully in native app but UI does not indicate a change to AEB type and only a single photo is taken and recorded to SD card.
I routinely use this type of command List on my M2P successfully with the UI changing to indicate AEB type and 3 bracketed photos taken and recorded to SD card.
Comments
10 comments
Does it work if you remove the camera mode command?
No.
In fact it failed because the interface happened to be toggled to video and it complained about the AEB commands.
When I physically toggled the native app interface to photo the same mission without the mode set ran successfully but again ignored the AEB commands and only took a single photo.
Do you have the camera set to 12mp mode? AEB doesn't work with 48mp I believe.
No, according to DJI Fly, it is set for "single" vs 48mp.
I have a similar list for video init I use with my M2P.
Likewise it will not run successfully unless I have the UI toggle set for video. At least it seems to accept the other commands successfully, i.e. 2.7K/30fps to 4K/30fps.
To net this out after several tests, I am unable to set the camera mode or type if it is different from the current setting.
If the mode or type settings happen to match, the command list executes successfully including AEB. If either mode or type is different I get an unsupported failure message.
Great news!
Updated to IOS version 2.1.0 Build 137 and re-ran the List component plans referenced in this post that initialized the MA2 camera and all ran successfully.
I was able to set the camera "mode" from video to photo (and back) as well as manipulate the the photo "type" from single to AEB.
I received no error messages of any type as I had before with Build 136.
I feel very encouraged we are getting closer to solid MA2 support!
Think I might be doing something wrong leading to a similar error. Also these errors were for build 136. So please stop me if this was addressed in 137, but I want to be sure I am not missing a necessary input item for mapping missions.
Pretty simple - I set up a basic mapping mission for my MA2. Set all of the prompted items on the desktop - approach (little to no editing here just set altitude to 200 ft. ) then mapping elements i.e. camera type, altitude, pattern, overlap, pitch, mode (photo) and min capture interval. Draw my basic boundary.
That is it.
In the field, the mission starts up and executes approach. Drone rotates and set itself on the mapping path, adjust gimbal to pitch and then fails with the following error - Camera Mode | Photo | Unsupported Interface.
So not doing anything fancy. Can honestly say I am not positive if the drone was set to photo or video but I can see that little toggle on my iphone in my mind's eye. Which if this is why it was failing...ugh.
I want to be sure that my set up is right.
Do I need to create a list to set all camera parameters before the mapping can begin? Was hoping for a plug and play mapping functionality.
That was the same issue I was having with Build 136.
I installed Build 137 and the problem has gone away.
I put all of my common camera commands in reusable Lists for the various photo and video settings I use. I then include them as needed during the mission prior to intended capture. For example, they can easily be included for "immediate" execution in a Destination Approach for a Path or another Destination.
One way to test this is run a simple plan at home where the only component is the List that just includes the camera commands from your plan with no motion components. I still typically remove my props just to be sure!
Excellent. Wild weather here in SoCal as of late and I need to take extra time to get to place to fly within all the restrictions so the idea about a no motion plan is a good idea. Thanks.
Looking forward to trying the mapping again tho.
The primary reason I am looking to use Dronelink as opposed to my current automation software is camera control. Dronelink exposes all of the camera commands available from the SDK with is great. The trick, however, is to only use the ones that are supported by your drone. Otherwise, you will get errors. The "no motion" plan solves that problem and eliminates surprises later.
Please sign in to leave a comment.