Mapping Camera Stop Failed - For no reason???
Strong signal, 16 sats.
After the first couple of rows, every time it went to turn it got this error.
In your favor the mission did seem to restore ok (have not stitched it yet)
Mavic 2 pro, smart controller, latest version.
Comments
3 comments
The reason given was: Execution of this process has timed out
This error message comes straight from the DJI SDK and we have no control over it.
Well the map seemed to stitch ok and the images were not blurred.
When I said no reason I meant nothing in the flight conditions. White other mapping software things like wind, low signal etc. and been
I appreciate how difficult it is to deal with this SDK, and have to admire you willingness to do so.
So what you are saying is that no matter what you do you can not prevent that error and have no idea what causes it? While of course I am not aware of the particulars, are you sure that it is not how you are commanding the SDK?
Also how about and option to just continue the mission when this happens? There is certainly nothing the user can do to mitigate this.
We actually already do a lot to work-around such errors behind the scenes (like retries with exponential back-offs), but in the end we can only do so much.
We already have these options on command components (required / failure mode):
The Map component uses these behind the scenes, so we could potentially either a) expose this as an option in the Map properties or b) automatically ignore the failures, like we already do in the Facade component (when distance based triggering is enabled). The danger of either a or b is that the command is actually failing (for whatever reason) and then you end up with a ruined data capture (either too few, or too many photos). If this is something you are willing to accept, then I guess its better than the alternative. i.e. the current "you shall not pass" behavior.
Typically this happens when there is lots of RF interference.
Please sign in to leave a comment.