Drone-specific features (Mavic Mini).

Vadim Temkin

I should probably post it in the "Feature request" section, but I'll ask here first.

I understand that the Dronelink plan allows for all and any commands available in DJI SDK. Obviously, each of the drones has its own subset of the available commands.  For professional use, when the user/organization has multiple drones, it is great that one can create a plan which will work for different drones.

Now, with all the Mavic Mini users (myself included) started to use Dronelink, it would be great if the user can set up the target drone in the settings, and all the commands (and settings) that are not available to this particular drone would not show in the interface (of course, this option should be switchable).  In addition, the Mission checker should be able to flag commands and settings which will not work for the particular drone (in case you are trying to reuse plan which was targeted for different drone).

I understand, that would be quite a rewrite, which could take significant effort. In meantime, just a simple spreadsheet with a list of commands and settings available to each specific drone (or just one for Mavic Mini, users of the other drones know their machines much better) would be extremely useful. So I can go to New Component / Camera Command and don't try to add Camera Mechanical Shutter.

For the same purpose, it would be great to have something like tags in the repositories of plans and functions which would mark them as designed (or safe) for Mavic Mini (or other drones).

 

1

Comments

10 comments

  • Comment author
    Jim McAndrew Dronelink Staff

    Even creating the spreadsheet would be very difficult on this request. I think the best we could probably do would be to crowd-source it from actual usage data. When users try to use commands that fail, we could save that back to the server and then display a probability of command failure based on the actual data.

    In the meantime, you can just set the commands to not required and it will skip over them if they fail, instead of failing the whole mission.

    0
  • Comment author
    Vadim Temkin

    Is there any way for the user (or you) to see a log where one can see the results of not required commands? I created a public test plan with all (or most of) the camera commands: https://app.dronelink.com/vadim-temkin/testing-mavic-mini-features-availability/plan/zwuMFo3hth7MJAOUfRUT Supposedly it can be executed without leaving one's room. Any ideas?

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    Yes, you can run a command-only mission while the drone is on your desk.

    At the moment there is no UI that displays the results of individual components, but you could export the mission and use this library to decompress it and see the results (in JSON).

    0
  • Comment author
    Vadim Temkin

    Jim, how to bypass "Drone Takeoff Location Unavailable"? And how do I "export the mission"? Thanks!

     

     

     

     

     

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    Turn off this:

     

    Mission history can be found on this tab:

    Open a mission and click this:

    0
  • Comment author
    Vadim Temkin

    Thanks, got it! And got the first bug report:

    "Unable to Execute Mission

    java.lang.NullPointerException: Attempt to invoke virtual method 'com.dronelink.core.mission.core.enums.Camera Exposure Compensation com .dronelink.core.mission.core.enums.Camera Exposure Compensation.offset(int) on a null object reference"

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    Interesting. Will take a look at it.

    0
  • Comment author
    Vadim Temkin

    While I try to build an interface for lzutf8 you can take a look at the result lz file: https://drive.google.com/file/d/1c3nokNqnwm77DsJhFtHazDkfro2y8xnf/view?usp=sharing

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    If you hammer the camera with this many commands in rapid succession it will probably have a hardware error / disconnect. You should try putting some wait statements between the commands.

    0
  • Comment author
    Barry Houldsworth Dronelink Expert Dronelink Expert

    I think this video might help https://youtu.be/18ivyaVGNes

    0

Please sign in to leave a comment.