On The Fly Missions not save and accessible.
I flew three OTF missions today. After returning home and opening DL on PC and tablet none of the Named missions are showing up.
I flew three OTF missions today. After returning home and opening DL on PC and tablet none of the Named missions are showing up.
<%= block.description %>
<% } %>
Comments
6 comments
Are you clicking this tab?
Jim,
That was what I was missing. Without written documentation to refer back to I loose track of some of the ways to navigate around all of the features of both the Native app and Web app. Getting too old to remember all the ins and outs of the many apps one uses to fly these days!
Thanks,
Greg
Why do you need any other apps haha j/k. Documentation is a goal, but in the end we are just leaning toward spending our item slamming out innovative new features and using video tutorials, and Eric hasn't released the tutorial for the functions yet. My dev pace is currently out-pacing his tutorial production pace :)
Hi Jim,
for me it is the otherway round:
I see all OTF missions in the webapp, but I do not see any failed or succeeded OTF mission in the native app. I see only one mission which was incomplete. Is that as designed? Would be great to see all those OTF missions also in the native app. Am I doing wrong something?
By the way: I tried several time to do OTF mission with the PATH component (a feature that I love, great job by you guys!!!), but those missions failoed right at the start of the generated mission with the error "Camera not accessible" (or so). That couldn't get overcome until I landed and restarted the drone.
KR, Oliver
Just found the exact error message in the OTF mission in WebApp: "Mission Failed: Camera Stop Capture | Camera Unavailable"
Link to that OTF mission: https://app.dronelink.com/oliver-paulus/mission/YHM1JoOalMSiegWA6H7g
KR, Oliver
The native app only shows active missions. If you want to see the past missions you have to go to the missions tab (pictured above) in the web app.
As for that error message, that is straight from the DJI SDK, and generally indicates that either your hardware is malfunctioning (may need to send in for repair), or you are issuing camera commands faster than the hardware can handle, and you may need to put a wait command before you execute the next camera command.
Please sign in to leave a comment.