Camera Photo Type Command Failure on iOS update 2.1.0
With the new update this error occurs when a picture command is being sent. Drones it has occured on are the Mavic 2 Pro and Mavic 2 Zoom. The error code is 1013. It seems that the HDR setting is never set even though the command is present.
Here is the link to an example mission file where the error occurs. https://app.dronelink.com/jaydon-bixenman/testing/plan/Cl1nfURRADZB8lEA72wr/sQZa8LDYARXLw9NwH0UE
Comments
3 comments
All previous versions of Dronelink used to ignore this error code from DJI. We added a new setting that gives you more control over when to fail missions (vs just disengage) when commands fail, so we changed the behavior of the kernel to no longer ignore this error. This is the new setting:
Disengage means just that: disengage the mission, which allows you to retry. This is good for situations where there error is recoverable, such as Start Capture but the camera is not quite ready.
Propagate means that the command should fail the parent component, or the entire mission if it is already at the top level (not inside any lists or other components). This was the previous behavior all the time before the setting.
Having said all of that, if you end up determining that your particular camera command will never succeed, you should either mark it as not required (if you intend to run the plan on multiple drones, where some support it and others don't), or remove it from your plan.
HDR is supported on our Mavic 2 Pro, however an error occurs when trying to use that setting as a command from dronelink. I found a similar bug here which returns the same code (1013) when setting mode to HDR - https://forum.dji.com/thread-222547-1-1.html
It details the difference between using DJIFlatCameraMode rather than ShootPhotoMode to update the setting on the Mavic 2 Pro.
Did you try eHDR like the post said?
Please sign in to leave a comment.