DJI Waypoint mission shows NO photo or video counts in Mission Estimate
Here is what the Mission Estimate Shows (count is zero):
Here is the Toggle Capture Markers view showing many pictures (count not zero):
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
25 comments
Daniel Snyder, can you possibly share the mission
Hi Martin, Sure. Try here: https://app.dronelink.com/daniel-snyder-rctunesv0hub0224z9yz/troubleshooting/plan/X1r7Oy6lgObY1EmbaIBC/EsqjO3v2HQXPw2bQXYqJ
What says the simulation timeline ?
I'm guessing something has gone wrong with the conversion to a DJI (onboard Mission), the preview timeline shows some photos & video for the last 2 components, but nothing for the first
I noticed there is no capture on map, just Path and Orbit. Still see no photo or video in estimate but maybe it’s due to it being a waypoint mission conversion as Martin stated.
Here is the Original un-Converted Waypoints Mission preview - Lots of pictures on both Waypoints and Mapping component.
Here is the Converted Waypoints Mission preview - Just pictures on the Waypoints:
And as you have seen - no Pictures or Videos on the Mission Estimate.
Maybe the DJI conversion engine is not converting all the Picture events (like fr the Mapping component)? Maybe it is supposed to convert the Waypoint pictures only??
OK, I have confirmed it from scratch. I can replicate the problem. I have a Mission with 3 components - Mapping, Waypoints and Orbit.
All 3 Components have Pictures and / or video. The run properly in Native Dronelink app and all 3 components produce their required pictures / video. This aligns with the mission estimator.
Post conversion to Onboard Waypoints - all 3 components are converted to DJI waypoints - bit the picture and video settings are missing from the Mapping and Video components. Only the Waypoint component retains their picture settings.
And the Mission estimator shows no pictures and no video items at all.
It is a 3 way discrepancy - The Conversion is only partially performed and the Mission Estimator does not work properly on converted DJI waypoints.
Do you think that dji waypoints are commonly/regularly used ?
So what happens if you actually fly it, what results do you get
It looks like there might be a regression in the converter as I know it used to use the photo time interval setting on waypoints to capture during maps after converting. Going to file this bug under the converter rather than the estimate or preview.
Thanks Jim. I hope the Mission Estimator will true up with the Timeline Camera events too. Martin - I am reluctant to fly a mission with these possible conversion liabilities. I'll test once Jim gets it working again.
Hi Stephane, If there is no cell service you wont be able to fly using Dronelink - unless the Waypoints are loaded onboard in the DJI drone. Useful in wilderness areas.
It should work if you download the mission before losing any cell service. No ?
Daniel. Understand about onboard for certain needs but you can download plan as Stéphane indicated. Just In case you weren’t aware. I download all my plans even though I now have an iPad with cell service. It Became a habit using my other WI-FI Only iPad for 2-1/2 years. Enjoy….
https://support.dronelink.com/hc/en-us/articles/4406012655763
Hey Daniel, thanks for providing the link to the converted onboard mission. Could you also provide the link to the original un-Converted Waypoints Mission as well?
Sure Nicolas - here is the originating source mission:
https://app.dronelink.com/daniel-snyder-rctunesv0hub0224z9yz/troubleshooting/plan/JlpNDyrKSAPEI3JQYgzg/UXohM1t62yz33q58SHAK
Good Luck.
Hey Daniel. Just a couple things I noticed unrelated to the conversion problem/ mission estimates. On this Original plan there are a couple things which you may want to changed or it may cause issues when actually running the mission. The Photo type is set to Single however you have an interval time command selected. Should select Photo type “Interval”, not single. Also the drone will only shoot intervals at what the drone is capable shooting. So 6 secs may cause it to either fail or it will run however, it will shoot at the interval which was set in the app when you last used intervals. The A2S can only shoot at 2/3/5/7/10/15/20/30/60s intervals. Unrelated to the question but something to look at.
You can test any camera commands without actually flying a mission. Just create a camera command list and run the mission. As long as there are no motion components like a path, orbit, map etc. it will not start the motors or try to fly. Good way to test any camera function to see which ones work and which don’t. So you could just copy that Original plan and then delete the map, path and orbit and leave just the photo camera commands. Just make sure there is just the purple reference pin, nothing else and remove the props at least for the first time for safety until your sure. Good luck…
Thanks Mike, This is great information I was not aware of. I will apply these constraints going forwards. Cheers, Daniel
There are several issues to note here:
1. The last Waypoint is Charlie Uniform - which is the 73rd waypoint - so that's not applicable here. (I nevertheless would hope if more than 99 waypoints are converted the program would shout out a warning to this effect - please confirm).
2. This point needs more clarification. For example - Does it mean that all camera commands are ignored in a converted mission? What commands are ignored / not ignored? Are the camera commands at each converted DJI waypoint executed or not? Very confusing.
3. Item 1 is not applicable in the explanation. Item 2 still does not explain how the Photo and Video counts in the Mission Estimator DISAGREES with the Mission Preview Photo and Video counts. (see screenshots previously attached) They can't report conflicting counts! They have to be made consistent.
Let me know if you have any questions. I'd be eager to retest when you have something updated.
CU is the 99th waypoint. (A-Z=26, AA-AZ=26, BA-BZ=26, CA-CU=21, 26+26+26+21 = 99). It also shows 99 Waypoints (Max) as the description under the component in the component list.
It does not currently show any warning, but happy to add it as a feature request. It will probably not be prioritized very soon as only a small fraction of 1% of all Dronelink mission are flown using onboard waypoints. This is one of those features that many people were very vocal about wanting us to implement, but when they see the disadvantages and limitations imposed by the underlying lack of features in the DJI waypoint implementation, they just prefer to accept the limitations of virtual stick missions instead. Obviously this isn’t true in all cases if your primary requirement is continuation of the mission after loss of signal, but that isn’t the reason most people want this feature, at least in the Dronelink user base.
It means all commands (camera, gimbal, drone, remote controller). The key benefits and limitations of converting missions are listed here.
This is what happens when you try to map a more feature rich mission format (Dronelink virtual stick) onto a less capable format (DJI onboard waypoints). It’s like trying to map 3d objects into 2d space - you lose things when you drop a dimension.
When the map falls back to the 99+ waypoint conversion code, it doesn’t insert the distance based photo capture settings at the waypoints, so the resulting mission doesn’t take photos, either in the preview or the estimator.
You placed a series of camera commands after the map, which included setting the camera to single capture mode, and then start capture, which results in 1 additional photo in the original preview timeline. This does not come through on the resulting converted mission.
Agree, at least about the video on the orbit that shows up in the timeline of the converted mission but not in the estimator. This is what is already being looked into.
Thanks Jim.... My mis-counting after conversion of base 26 to base 10 !
The orbit video should be counted now if you refresh.
Thanks Jim - it checks out. Both non-zero number of Photos and Videos are showing up. The count is not the same for Photos but at least it's not zero. (#Photos should be around 230). Good fix for now.
Right, this fix was not focused on improving the over 99 waypoints case. Having said that, I did take a closer look at your original mission plan, and it turns at the reason it is falling back to the default, over 99 waypoint conversion, is because you have terrain follow enabled on the map. In this case, it assumes that adding more waypoints along the map segments is more important to you so as to follow the terrain more closely during each segment. If you turn that off, it uses the optimized code which produces a much more accurate photo count estimate.
Please sign in to leave a comment.