Verify command is permitted based on which drone is used
There are many camera commands that are either not supported or will fail when used with particular drones.
Camera commands are among the most prolific which depend on the drone's hardware capabilities.
It would be nice to have a list of commands that won't work with which drone. Or if possible implement checks for them in the app itself.
In particular, the camera command to set the framerate is not supported for the Mavic Mini. While looking thru the SDK, there were many instances of exceptions for particular drones and checks which can be made for them.
It is very alarming to get half way thru a mission and get a mission failed because an unsupported command was attempted.
Comments
7 comments
This has already been requested and it is extremely hard to implement. Your best bet is to just create a command only mission and run it on your desktop to verify everything works. If dronelink sees that there are not motion components in a mission it won't require a gps fix or spin the props up, but you should always remove the props just in case.
Yes, I agree. That is typically what I do now. I just create the camera commands in a list and execute them in a test mission with nothing else. But it would be nice to have a list of commands that are known not to work in particular drones. With so many drones and hardware options now, it is hard to know which commands work and which don't without just trying them first.
"With so many drones and hardware options now,"
This is exactly what makes this feature hard to implement.
The most userfriendly option would be that Dronelink (knowing the user and knowing the drone) is only presenting to the user commands to choose from that are supported by his/her drone....
Unfortunately it is the most insanely hard thing to implement.
Cannot Dronelink users create public repositories based on manufacturer and model to list successfully used commands? Or as an open subject in the forum?
Others have proposed crowd-sourcing it in the past, but the project never seems to take off because it is too daunting.
Please sign in to leave a comment.