Image capture problems with DJI M300 RTK with H20T
I was excited to see that Dronelink supports missions designed for specific sensors on the H20T. Today I discovered that there is still much development to get this working.
I started by connecting my iPad to the M300 smart controller. The controller instantly recognized that there was an external device. I opened the Dronelink app and selected my mission. The mission simply would not load. I tried many things like disconnecting my tablet from the smart controller, opening the mission and reconnecting. This would get me into the mission but the flight plan would not load and the telemetry readings never populated.
So, I loaded the Dronelink app onto the M300 smart controller and connected to my WI-fi hotspot on the iPad. Installing Dronelink on the smart controller was simple (I followed the instructions on this site). My flight plan loaded and I was able to begin the mapping mission in RTK flight.
The sound of the image triggering only happened at the waypoints and the image capacity did not change which lead me to believe images were not being captured. There were other problems as well, like image exposure settings not populating and "jerky" flight. When I got back to the office I discovered that some images were captured but at seemingly random locations. It also appears that the settings are off because I selected "H20 Zoom (min)" and it looks like there is no overlap on the few images that were captured in appropriate succession.
I'm happy to answer any questions and help developers solve problems so that Dronelink can work correctly with the DJI M300 RTK system. I'm guessing Dronelink was never tested with an actual M300 RTK and smart controller but I am happy to help.
Comments
4 comments
Dronelink uses the DJI SDK, which supports all the drones listed on the system requirements page, but we have not extensively tested all the drones on that page. When you start to get to the higher-end, enterprise drones, there are many unique and exclusive features that may require additional code to unlock. This is definitely the case with the M300. As far as prioritization, we are not likely to spend resources on it in the near term unless you have an enterprise use case that has the potential for putting significant volume through an enterprise account. I assume you are just using a hobbyist account to test? If you want to discuss the enterprise stuff, feel free to reach out to sales@dronelink.com.
Thanks Jim! I do have an enterprise use case that will do exactly what you mention. I'm going to have a hard sell with my team, however, if I cannot demonstrate that Dronelink does what is advertises being able to do.
There are options to choose specific sensors with the H20T and M300 on my "Elite" plan. This directly suggests that it works. There is no mention that "one must spend more money to get what we currently say works".
If I can use the service, as advertised, with my "Elite" mapping membership, then I will gladly contact sales to spend more money.
We do not filter the sensor specification drop-down by account type because there are actually people using M series drones for non-business use cases. As far as adding them in the first place: this was fairly easy as each sensor specification is just one line of code in the kernel. The hard part is actually implementing the native code paths that need to call the various APIs in the DJI SDK that are required to use the unique features on that particular drone. We are actively involved in development projects that do just that with other enterprise customers for drones such as the M210 RTK, and we are happy to discuss starting such a development project with your company if the existing code base does not work for your requirements yet. The Elite plan is for hobbyist use only, but we do allow using it for testing, which in this case has shown you that there is still quite a bit of work left to do.
Great feedback. Thanks for being attentive to my concerns! I'll send an email to sales this afternoon and begin conversations about an enterprise solution. In the meantime, I'll continue to test and isolate issues. Looking forward to working with Dronelink.
Please sign in to leave a comment.