Popular Resources
-
<% blocks.forEach(function(block, index) { %>
-
<% if (imageHeight) { %>
<% } %>
<% if (block.name) { %><% if (block.html_url) { %> <%= block.name %> <% } else { %> <%= block.name %> <% } %>
<% } %> <% if (block.description) { %><%= block.description %>
<% } %>
<% }) %>
Comments
4 comments
Does it work for other, smaller test missions?
This mission works ok, RC lost about 1k, from takeoff point.
https://app.dronelink.com/mark-pinnuck/mavic-home/plan/rjSL5XpZegWuUehj3Y8v/cvhgZpzI5k15Ocksm6Wp
The only difference with this mission I created the entire mission as a normal mission, converted and deleted many of the generated waypoints. With the “Quarry” mission I created a 3 point mission and converted it, I then added the rest of the waypoints in the onboard mission.
Suggestion: It would be good if the flight dashboard had a mission elapsed time since start that kept ticking when RC lost.
Also when you touch the path display height, distance from start and elapsed time for that point. This helps you know when RC is due to reconnect. Ie touch the point Rc expected to return, if elapsed time exceeds that time by a significant margin you know the drone has run into trouble. The touch path feature not as important as elapsed time, saves me startling a stop watch when the starting a mission.
Flew mission again after just moving a couple of weigh points. Dashboard reported “RC lost mission stopped” ( not a good response when configured to continue mission) the mission continued autonomously and returned to the final waypoint. After reviewing the video of the mission, about 2/3 of the way the drone started rotating clockwise about a revolution every 15 seconds. It did not follow the mission view points.
Please sign in to leave a comment.