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
22 comments
Have you tried using Time instead of Distance for the capture priority?
I haven't given that a whirl yet, but it's on my to-do list for tomorrow. Is there a particular rabbit hole I should be diving into, or is it more of a "let's see if the universe aligns" kind of test?
Time is the more reliable capture priority on Mavic Pro — Distance often under-fires when speed drops or the camera interval can’t keep up. Switch the Map component to Time, use an interval the camera can sustain (often ≥2s depending on format/JPEG vs RAW), and see if capture continues past the first few shots. If it still stops around ~4, share the mission plan link.
It did exactly the same thing during the timing interval. The timing interval was set to 4 sec. and jpg photos. https://app.dronelink.com/john-keller/dronedeploy-migration/plan/XD6gH9TCgwM19k2rqVUw/Fgn9vgoZg9lcv9fF4Tji
Everything looks fine to me. Can you send a screen recording? The missions in your account don't show the error message you are seeing for their disengagement reason.
It doesn't throw an error, it just stops taking photos.
I assume if you start the camera in interval photo mode just sitting on your desk in Dronelink it keeps capturing?
I cant even try that because i cant fly it indoors
This test doesn't even require props on, just open the flight dashboard and start the camera.
I just took it up for another test flight and this time it failed right away after 1 photo
The desk test still matters — no flight, props off is fine. Power up on the desk, connect in Dronelink, open the flight dashboard, start interval photo, and see if it keeps firing. A screen recording of a run that stops after one photo would also help (camera settings visible when capture stops).
I looked at your plan and you have the interval time set to 4 secs. The original Mavic Pro drone along with I believe all DJI drones aren’t capable if 4 second intervals because the firmware does not allow it which is what your plan has it set to. Either use 3 or 5 sec interval and try again. I think that is your problem. Only what the DJI Firmware allows for your drone can be used with the Dronelink app. If it won’t work in the DJI app then it won’t work with Dronelink.
Majority of DJI drones firmware allows timed intervals at 2, 3, 5, 7, 10, 15, 20, 30, and 60 seconds. Check the specs for your drone to confirm but those are the most common intervals for most of them. Enjoy.
I set it to 5 sec intervals and it hasn't taken over 2 photos before it stops taking photos all together. How do I test it without taking off? Where is an option to turn off the props?
No takeoff needed — leave the props off (there isn’t a props-off toggle). Power the aircraft on the desk, connect in Dronelink, open the flight dashboard, start interval photo, and see if it keeps firing past the first couple of shots. A screen recording of that desk run with camera settings visible when capture stops would help.
I tried that and video'd it. it seems to work on the desk but i took it out and tried it again in flight and it takes about 2 photos and then doesnt take anymore.
Sounds like a hardware error, but you might have better luck converting to onboard waypoints: https://support.dronelink.com/hc/en-us/articles/41225655534867-Onboard-DJI-Waypoints-Legacy-Drones-Converting-and-Running-Missions
Curious it you set the interval in the plan to 5 seconds in the mapping component or in the DJI app first. Maybe try that just to see if it’s the interval time will stick. Since it’s working with just the photo component and no motion components on a desk maybe the setting in the mapping component is not sticking. Just a thought
Just noticed you have the focus mode set to continuous AF. I’m not sure that will work or not. Maybe change it back to the default - - and see if it runs. Sometime those ficus modes won’t work properly.
I tried it at 5s and 7s with the same RESULTS. I will try it again without AF on and report back.
Since it starts and runs the mission I don’t think it’s an issue but in the future I would not change the arrival time to 0.0 seconds. Either 1 sec or leave it at the 4 sec default. The 4 second default value will not change how the mission runs. There are a lot of settings in the web app and if some are changed it could keep the mission from running correctly. This applies to all the deceleration and acceleration rates for horizontal, vertical and rotation values. Motion tolerance as well as altitude range. It’s always best to leave all the settings to the default values which have been tested and used for years. I’ve been using DL for almost 6 years and the only settings I change from the default values are the Altitude, Speed and Pathing corner radius. Everything else is left alone. Just some info which may help in the future.
Also since the photo timed shots work on a desk without any component it must be the map component which has been discussed or as Jim stated a hardware issue with the drone. I know 4 seconds won’t work so use 2, 3, 5 or 7 seconds set in the DJI app first as well as the same value in the map component. Change the arrival time back 4 seconds and the focus mode to the default - - . If it doesn’t work then there is more than likely another issue.
Please sign in to leave a comment.