Occasional error thrown by newStopIntervalPhotoAction()

Completed

Comments

4 comments

  • DJI Developer Support
    The 'The execution cannot be executed' was thrown by the camera firmware. If this error occurs randomly, i think the very frequent shooting action may block the firmware. I suggest you set the interval to ast least 2-3 seconds to reduce this error. By the way, our latest SDK is 4.16.2.
    0
    Comment actions Permalink
  • Sean McEntee

    You are on the right track. To clarify, I have the interval fixed at 3sec for exactly that reason. And the error never occurs on the ShootPhoto action. It only occurs for the newStopIntervalPhotoAction().

    My guess is that if the Stop action arrives at the moment when a photo is being taken, the error is thrown.

    (So with approximation figures, if the time to take and process a photo is 0.3sec, my interval is 3sec, a random clash will occur about 1 in 10 times I issue the STOP command- which is what I am observing)

    0
    Comment actions Permalink
  • Sean McEntee

    Some further information as I am still testing...

    The STOP command still works even when it throws the error i.e. no more photos are taken

    Secondly, it MAY only be happening when the newStopIntervalPhotoAction is the last item in the Timeline. On one occasion when I was in debug, I noticed the additional information of "The mission has already completed".

     I will try to verify this with a further dummy action where there are no further actions.

    0
    Comment actions Permalink
  • DJI Developer Support
    To be honest, there is no much things the SDK can do because the camera firmware hasn't handle our SDK camera actions correctly.
    0
    Comment actions Permalink

Please sign in to leave a comment.