True AGL support is on the roadmap.
Yes, from the mission previewer. We have a whole video dedicated to this.
I assume you mean the Free plan for individuals? Yes, there is no functional difference between Free and Pro right now.
effective-gis.blogspot.com
KML import is also still on the roadmap. Having said that, even if we do add it, the import will probably result in creating a path component, not a map component, which means you will then have to do all the camera commands yourself.
The reason Dronelink is different is because most other apps use DJI's onboard flight controller. This is also why you see it take a while at the start of the mission, and why you see it say joystick and not waypoint:
support.dronelink.com
support.dronelink.com
The app will show a dialog with the error message when the mission disengages. If you forget to read it you can see it from the web app by hovering over the mission status in your mission list:
Every time you open a mission plan the web app marks it as "touched" and the native app sorts the list of mission plans by most recently touched.
The autofocus control is provided by DJI as part of their built-in UI library in the DJI SDK. They are working on an overhauled version of the UI library which I am hopeful will fix a lot of their bugs.
The reason Dronelink is different is because most other apps use DJI's onboard flight controller. This is also why you see it take a while at the start of the mission, and why you see it say joystick and not waypoint:
What happens if the drone loses connection?
DJI drones have a connection fail-safe setting that allows you to configure the behavior of the drone in the event that you lose connection. The options are hover in place, return to home, and auto...
Why do I see "Device Running Too Slow" during missions?
Dronelink uses a custom flight controller that performs all the calculations on your mobile device (learn more). This can be processor intensive depending on the complexity and duration of your mis...
Not sure which part of the documentation you are referring to, but this article states that the only advantage is that the mission continues after you lose connection:
support.dronelink.com
The screenshot is of the web app. The only thing the native app does is mission execution.
IIRC none of those apps use DJI's UI library. DJI includes the UI library to give developers a jumpstart when creating new apps. In the end most developers end up switching to their own custom UI components for the flight dashboard to either get around bugs or provide industry-specific user experiences. We haven't had the time or the resources to prioritize this type of feature develop considering the long list of other features that people are demanding that make Dronelink unique.
Not sure which part of the documentation you are referring to, but this article states that the only advantage is that the mission continues after you lose connection:
What happens if the drone loses connection?
DJI drones have a connection fail-safe setting that allows you to configure the behavior of the drone in the event that you lose connection. The options are hover in place, return to home, and auto...
When I implemented support for LCMC (lost connection mission continuation) in Autopilot years ago, about 1% of all missions were flown using it. People basically didn't want to use it once they saw the features they would lose by selecting it. The reason I implemented it was because the community was adamant about how important it was and how much they would use it once it was there. Unfortunately it look a ton of development effort and then the numbers didn't back it up. The reality is we will probably skip that style of LCMC all together in Dronelink and just go straight onboard (M series) or even run the flight controller in the cloud and sent commands over the cellular network (this is the future, it's going to be exciting).
2-3 years is an eternity when exponential curves are at play (Moore's law). These types of devices might be able to handle basic missions with a path and an orbit but once you start getting into larger more complex missions (as happens with mapping), you are pushing the limits. We are doing out best to push the limits of the tech but in the end you run up against physics. If you do need to use Android and/or a late model device, I would consider switching to a tablet, at least for the advantage of a larger battery and better heat dissipation (not to mention the larger screen to see the live video feed = safer).
versus.com
I guess it depends on who you want to believe. This article claims a 45% performance increase over the 845, so assume even more over the 835. In the end specs don't really matter. All that matters is the real-world experience with actual workflows.
Happy to test it our on our S7 test device if you share a link to the mission plan. Will post the results compared to loading times on latest hardware.Fair enough, can't argue against metrics. Last thing, my point on the "old device" comment was that your app, while complex, should not take 1-2 minutes to process on a Note 8. While its a 2 year old device the newest Note 10's CPU (Snapdragon 855) only beats the Note 8 by a measly 8 pts. That's Samsung's flagship phone, not a device issue is my point.
it's possible there's a bug in the appQualcomm Snapdragon 835 vs Qualcomm Snapdragon 855: What is the difference?
What is the difference between Qualcomm Snapdragon 855 and Qualcomm Snapdragon 835? Find out which is better and their overall performance in the mobile chipset ranking.
