Mavic Mini madness - New 2021 problem

Mario Vallerini

Hi, I have a serious problem with my Mavic Mini 1.
I installed Dronelink and DJI Fly on the Pixel 1 and it worked great for a month.
The phone is dedicated to these applications and does not surf the internet in any way other than to download your flight plan.
The phone is rooted and I have a firewall installed.

On December 31st I prepared a 5 minute mission above the garden where at midnight we will have done fireworks. Keeping some distance, taking photos and movies.

I have tried the flight plan a few times, making small adjustments, until the final version I have further tried to the end and successfully.

When, hours later, it was time to launch the mission, the drone lifted off the ground for the usual meter, and then veered left to hit a wall. It hasn't reached the point of "Approach".

I tried again the next day and, after having raised the usual meter, he took another direction and finished against a plant. Also in this case it did not reach the mission start quota.

With DJI Fly 1.2.1 software the drone still flies perfectly.

The batteries were all charged. The area where I live is in the countryside with little radio interference. (I'm a radio Ham).

I would like to know what you think or if someone else has had a similar problem.
I use Dronelink 1.7.3 because version 2.0.0 does not work on my system.
With 1.7.3 I did other missions that worked perfectly.

Thank you for any advice.

Mario

0

Comments

14 comments

  • Comment author
    Jim McAndrew Dronelink Staff

    Which mission in your mission history had the issue? Click this tab for your history:

    Can you please provide more details on what you mean by 2.0.0 does not work?

    1
  • Comment author
    Mario Vallerini

    Thank's for your answer.

    I'm not sure I understand.

    On the PC (via web) the mission is called: "Capodanno - Jan 1, 2021 11.33 PM" and was the last fly into a plant. Auto aborted after 3 seconds, due the crash.

    Into Android device the mission is called: "Capodanno - Dec 31, 2020 3.08 PM".

    I remember that, on Dec 31, after having done all the flight tests, I downloaded the plan on the phone to use it offline and so I tried it. And it worked well. I had everything ready for the mission when the time came.

    ------------------------

    As for version 2.0, I can still say little. I installed it two days ago and tried it yesterday (Dec 31). It said it was connected, but I didn't see the drone video. I was running out of time, so I reinstalled version 1.7.3 which I knew worked fine.

    I will be happy to continue my tests. Now I also have a Mavic Mini 2, but unfortunately it doesn't work with dronelink.

    ---------------------

    I hope I can figure out what went wrong with the last flight plan. I have had some damage to the drone, but I am especially sorry that I can no longer use your software.

    Regards, Mario

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    I don't have enough information to know exactly what happened, but the mission history in your account shows that the mission was aborted after 3 seconds. Assuming you started from the ground, the first several seconds of the mission would have been executing DJI's precision take-off command, during which Dronelink has no RC stick authority. It would help to see the flight logs.

    As far as there being a difference between 2.0.0 and 1.7.3 in terms of the drone connection process, none of that code has changed so I think your issue must have been circumstantial. We are about to deprecate 1.7.3 and force all users to upgrade to 2.0.0, so if you continue to see the issue you may need to run through these steps.

    0
  • Comment author
    Mario Vallerini

    Ciao Jim,

    "during which Dronelink has no RC stick authority" I tried to dodge the plant the second time and, in fact, it wasn't responding to commands.

    If you want to see fly logs of Dec 31 and Jan 1 (the last fly), you can download from here:

    https://mega.nz/file/z4kBEKxY#HSoszNBsngJ3VcJTvkoOinvcGpfYKq-Zb04C8RF3jqI

     

    Thank's for your time!

    Mario.

     

     

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    Can you upload in another format (zip?)

    0
  • Comment author
    Mario Vallerini

    https://mega.nz/file/XsUmSB7Y#nqvsxxteuOXe5QsEM3WoEjsit-Rela3KRL2qtp8zt40

    Zip format

    0
  • Comment author
    Mario Vallerini

    "during which Dronelink has no RC stick authority". May be I've understood now (better late than never): there is the possibility the problem is in thr DJI's firmware take off procedure? This is a possibility, but, after the last crash, I've done a little fly in my house with DJI's fly 1.2.1 without problems...

     

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    Thanks for sending the logs Mario. After careful examination, I believe we have found an explanation for the incident. Some of this is conjecture as we don't have complete information, but I believe the root cause is correct:

    It appears that you attempted to start the mission on Dec 31, but the mission immediately disengaged after takeoff, probably because the drone was not in P mode (v2.0.0 actually has new code to automatically switch the Mini to P mode at the start of a mission to avoid this).

    After this first attempt, it appears that you tried to resume the mission (while the drone was still in the air?) and it immediately disengaged again because the flight mode was still not P.

    You then gave up for the day and came out the next day (Jan 1) and attempted to resume the mission. This attempt was from the ground, and most importantly, it was after the drone has been restarted from the previous day. Of course, when the drone restarts, it acquires a new GPS lock, which on consumer drones such as the Mini, can be +/- 4 meters due to the low quality sensors that are incorporated in the hardware. We assume that you either took off from a different spot from the previous attempt, or the GPS lock was different by an amount up to the error margin previously listed. In either case, once the drone took off and Dronelink took control of the sticks, it attempted to fly the drone back to the previous location that the mission was disengaged (as is the standard resume logic) and this resulted in lateral motion before going for altitude as the previous location was probably somewhere within 4m laterally at an altitude of 1m.

    In the end, you probably should have aborted the previous mission and started fresh, but the app does give users to the option to resume previous missions. The normal case is resuming to a point midway through the mission when the drone is already at altitude (for battery swapping), or resuming immediately after an unintended disengagement during the same battery session (meaning the drone would have the same GPS lock, as was the first resume attempt listed in our analysis above).

    We are considering adding additional safety measures to prevent situations like this in the future, and we are willing to take responsibility for any damages that may have been caused by the incident. Please email support@dronelink.com if you need renumeration.

    We apologize for any inconvenience this may have caused and thank you for the report!

    0
  • Comment author
    Mario Vallerini

    It appears that you attempted to start the mission on Dec 31, but the mission immediately disengaged after takeoff, probably because the drone was not in P mode (v2.0.0 actually has new code to automatically switch the Mini to P mode at the start of a mission to avoid this).

    I actually don't know in what mode it was.

    After this first attempt, it appears that you tried to resume the mission (while the drone was still in the air?)

    No, the drone fell after 3 seconds. But I had forgotten that two minutes after I tried another take off. Always from the same starting point, every time always from the same point.

    We assume that you either took off from a different spot from the previous attempt, or the GPS lock was different by an amount up to the error margin previously listed.


    No, it was the same take-off point, but the GPS error you are talking about has already happened to me.

    ----------------------------------

    Thanks for helping me understand what happened. Luckily I just had to change a few props. I would like to know how I can (in the future) completely reset the mission in order to repeat it without problems. Obviously I will pay close attention to the "P" mode. I don't know why version 2 of the app doesn't work on my smartphone. Today I reset the phone and try it again.

    Thanks again for your answers and congratulations on the support service.

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    If you are on 2.0.0 you won't really have to care what mode it is in because it forces it to P for you now. If you want to make sure you are not resuming a mission, just make sure to abort the previous one (will show as red). Tap the ... then Abort:

     

    0
  • Comment author
    Mario Vallerini

    Ciao Jim, I have good news!

    I don't not why, but today version 2.0.0 run ok on my phone. 

    I've done the last mission (after aborted like you said) and Mavic Mini flew well, completing the mission from start to finish.

    Grazie dei tuoi consigli. Mario

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    Glad to hear it!

    0
  • Comment author
    Norman Rodriguez

    Buen día;

    Hoy 19-07-2022 perdi mi drone " DJI Mini 2 3NZSHBQ004020C | 01.05.0000" usando Dronelink, realice un plan de vuelo y ejecute la mision, despues de algunos minutos perdi la señal de mi drone e intente retornarlo a casa con RTH, pero de igual manera el drone seguia sin señal. 

    Acudo a ustedes para ver como me pueden ayudar con esta situacion, gracias.

     

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    You can access the flight logs to see the last known location.

    0

Please sign in to leave a comment.