Fail on mission start with beta version + DJI Mini 3 PRO
Hello I bought Premium hobbist Dronelink in order to I could test it together with my new Mini 3 pro with RC N1. I use Samsung S21. I tried also Huawei P20 Pro.
I have success with creating little missions with endpoints in "on the fly" mode. Missions was completed ok.
But I wanted to create planed mission from my computer, so I created this little mission.
When I arrived to the place I takeoff with my drone I tried to start mission. I had many unsucessfull starts with error something like "Unable to take controll". After then I figured out, that it not works in Cinema mode, which I have enabled on RCN1, I switched to the Normal.
I tried to start mission again, I check some option something like "Mission is running. Restart and reload mission"
After that, was mission started, drone tried to fly into the first waypoint, but instead of this, drone was falling into the high grass. I tried to stop mission and take control, but drone ignored me :)
After this, I first time tried function "Find my drone" in DJI app, because of high grass :)
I also have one similar fail before 2 weeks. I only connected to the drone with Dronelink, but drone start immediately falling after takeoff similar way as in this case. I done nothing, only takeoff, no mission was started I only connected and start drone with Dronelink.
I tried also Follow mode, but drone was unstable in the air and was doing some unusual moving, but not followed me, so I stopped this rather. Drone was not falling in this case.
What was reason for drone Fail in my mission? Maybe low altitude 3m at start? Or little bit different takeoff location as on map?
Comments
7 comments
Hi Svato, can't see why that mission failed, it all looked good, yes you need to be in normal mode to execute missions, the only thing i can think of is you launched the mission before you had enough satellites locked for the home point to have set properly
Hello Martin, thank you very much for response, maybe I had no enough salelites.
I am newbe in Dronelink. It looked that drone flyed for first waypoint (it was not captured video on sd card) but altitude instead of growing up was growing down and it was followed by unintended landing in high grass.
I explain this for me so: I taked off on another place as is on map and takeoff point was grabbed there.
Altitudes are relative to the takeoff point I think. So it maybe calculated, that he should decline instead of rising. (But it's strange because 3m is enough) Or previous experiments with Cinema mode enabled generated some mess in Dronelink commands?
I will try it again, but I will enable capturing video manually before start and I enable N mode to avoid mission start errors.
I looked at your plan as well. First of all I would not fly at or descend to a very low altitude of 3M. These drones only have an accuracy of about + or - 4M. So about 13’ which means it could hit something when flying that low altitude. The altitude is based on the drones take-off location but if the elevation is not completely level/ flat from where it started it may cause an issue as well. I believe the elevation change was enough where it was too close to the ground when it got to the end of path and as you said in high grass. I looked at the plan in both DL and Google Earth and in 3D view and I can see the difference in elevation in that area. Overall it looks like the 3M altitude at the start of missions is too low and is flying the approach going up in elevation to the first point. It may have looked like it was descending but I believe it was due to the increase in elevation and flying at the set 3M uphill, even if just a bit. My suggestion would be to start and end any mission at a higher altitude.
Also there are several ways to take control of the drone at any time easily. I’m attaching a link to DL’s help articles which there are a ton of. Should be able to find a lot of info there. Good luck.
https://support.dronelink.com/hc/en-us/articles/360036830214-How-do-I-take-over-control-during-a-mission-
https://support.dronelink.com/hc/en-us/categories/360001874574-General
Hello Mike,
you are absolutely right,
I tested this mission through weekend.
At Saturday morning I increased first waypoint to 10 meters.
Mission started, but I noticed near the drone some birds and I stopped mission manually.
At evening was place clear, no birds so I started mission again on the same place. Spiral was going ok but where was drone at the first turn,
app Dronelink in my Samsung Galaxy S21 disappeared(Crashed without warning).
So I tried it again with the same result. RC N1 stayed connected so I navigated drone manually to me.
You are true with GPS inaccuracy, I noticed that start altitude is always different, one time I had to stopped drone again because it started immersing into the grass again :) but another try was about 10 meters above ground. It also dependent on takeoff location because terrain is not flat, takeoff is from lower altitude as first waypoint.
This mission near the forest with no flat terrain at takeoff is probably risky.
Next day I tried it at morning and at evening and today morning too. Dronelink was exited self. I think the place where app crashed is random. I have setted up in firmware max Altitude 140m and max distance 1000m. So this shouldn't be reason.
This morning I noticed notification that new beta version 4.6.0 exists, so I will install it and test it again. Maybe problem will be disappeared.
4.6.0 has been out for awhile and has had many build number since implementation. Always a good idea to keep version up to date especially with the newer Mini 3 while testing. Also you may encounters some issue using that S21 device. If it is working then thats good but just be aware. Check help section.
https://support.dronelink.com/hc/en-us/articles/15304402363411-Mini-3-Mini-3-Pro-Support-Overview
Hello, with version 4.6.0 mission works even in APAS mode with Obstacle Avoidance enabled in Dji Fly App. Also Follow mode works near good.
I noticed my Dronelink app had enabled max altitude only 40m, maybe this was reason for app crash before with older version of Beta at particular point of mission.
We made a change to allow engaging (putting the drone in virtual stick mode), even while the flight mode is set to APAS. This does not mean that the obstacle avoidance is actually working in virtual stick mode, just that DL now allows you to go from APAS to Virtual Stick flight mode.
We didn't make any changes to follow mode.
Not very likely. The crashing cause is discussed here:
https://support.dronelink.com/hc/en-us/community/posts/16409496589331/comments/16410305783571
Please sign in to leave a comment.