- Joined
- May 26, 2017
- Messages
- 6
- Reactions
- 0
- Age
- 43
I think it is since last update I have very strange problems with my drone.
I used to fly in the fields surrounding my home in Belgium which is not so far from an airport, but it is only class D airspace according to DJI software.
In Belgium I'm allowed to fly on private property to a height of 10m without license outside of a range of 3km of an airport and when I have a permission of the owner of the property. I am all in regulation with this.
But when flying the last 2 weeks, I get a at a certain point during my flight a notification that the drone is returning home. I can cancel the return home, but immediately afterwards this starts again. Even to this extent that when the drone is trying to land, it says not safe to land, because of grass land below it, goes out of auto land mode and then puts itself in auto land mode again, while descending everytime a couple of cm. This goes on in an infinite loop for until it reaches the ground. Basically it is fighting it's own software.
There is no warning that I'm flying in a no fly zone, there is only at the beginning of the flight a warning that I'm in a class D airspace, so I have to fly with caution. I used to get a pop-up that I had to check the boxes I have permission and I understand the risk involved.
After the drone landed I can take off again and fly for a couple of minutes before it goes through this procedure again.
It's really not consistent, because sometimes, I can't even take off. The drone says taking off and then shuts down it propellers. While other times I can take off and fly till the battery dies.
i always wait for home point update, so I know that the drone should have it's gps and all databases located and updated before taking off.
I tried:
- several locations in my neighbourhood,
- changing from android to ios
- other battery
- different times of the day.
My results:
- first time, flying for 2 minutes, RTH auto-initiated
- couple minutes later not taking off.
- 30 minutes later taking off a bit further 1km and flying to the coordinates where the RTH was triggered, no problem. I could keep on flying
- couple of days later, taking off different field about 3km further, flying for 8 minutes, RTH auto-initiated.
- after landing, taking off again flying other direction, flying 2 minutes RTH auto-initiated
- going 1km further, not possible to take off.
- unlocking the authorization zone closest to my location, allowed me to take off, go up to 7 meters and the RTH auto-initiated
- not possible to take off afterwards anymore.
My location Sart-Risbart, Belgium for those that want to lookup the restrictions for drone flying in my area.
When I go through the flight logs, there is no mention anywhere about why the RTH is triggered the status changes just from normal flying to RTH. Same when not taking it, it says motors started, RTH initiated close to home point landing. (BTW it did not take off yet)
I have had this behaviour one time before, while I was on the border of a NFZ and I thought I was just outside the zone, while I wasn't and so the drone did not take off or when I moved an put myself outside of the NFZ.
So now I'm asking myself why this behaviour happens.
If this is intended by DJI, then this drone has just become a very expensive paper weight, because in Belgium you are almost always flying in a warning zone. there are very few places where there is nothing in the neighbourhood.
I used to fly in the fields surrounding my home in Belgium which is not so far from an airport, but it is only class D airspace according to DJI software.
In Belgium I'm allowed to fly on private property to a height of 10m without license outside of a range of 3km of an airport and when I have a permission of the owner of the property. I am all in regulation with this.
But when flying the last 2 weeks, I get a at a certain point during my flight a notification that the drone is returning home. I can cancel the return home, but immediately afterwards this starts again. Even to this extent that when the drone is trying to land, it says not safe to land, because of grass land below it, goes out of auto land mode and then puts itself in auto land mode again, while descending everytime a couple of cm. This goes on in an infinite loop for until it reaches the ground. Basically it is fighting it's own software.
There is no warning that I'm flying in a no fly zone, there is only at the beginning of the flight a warning that I'm in a class D airspace, so I have to fly with caution. I used to get a pop-up that I had to check the boxes I have permission and I understand the risk involved.
After the drone landed I can take off again and fly for a couple of minutes before it goes through this procedure again.
It's really not consistent, because sometimes, I can't even take off. The drone says taking off and then shuts down it propellers. While other times I can take off and fly till the battery dies.
i always wait for home point update, so I know that the drone should have it's gps and all databases located and updated before taking off.
I tried:
- several locations in my neighbourhood,
- changing from android to ios
- other battery
- different times of the day.
My results:
- first time, flying for 2 minutes, RTH auto-initiated
- couple minutes later not taking off.
- 30 minutes later taking off a bit further 1km and flying to the coordinates where the RTH was triggered, no problem. I could keep on flying
- couple of days later, taking off different field about 3km further, flying for 8 minutes, RTH auto-initiated.
- after landing, taking off again flying other direction, flying 2 minutes RTH auto-initiated
- going 1km further, not possible to take off.
- unlocking the authorization zone closest to my location, allowed me to take off, go up to 7 meters and the RTH auto-initiated
- not possible to take off afterwards anymore.
My location Sart-Risbart, Belgium for those that want to lookup the restrictions for drone flying in my area.
When I go through the flight logs, there is no mention anywhere about why the RTH is triggered the status changes just from normal flying to RTH. Same when not taking it, it says motors started, RTH initiated close to home point landing. (BTW it did not take off yet)
I have had this behaviour one time before, while I was on the border of a NFZ and I thought I was just outside the zone, while I wasn't and so the drone did not take off or when I moved an put myself outside of the NFZ.
So now I'm asking myself why this behaviour happens.
If this is intended by DJI, then this drone has just become a very expensive paper weight, because in Belgium you are almost always flying in a warning zone. there are very few places where there is nothing in the neighbourhood.
