I believe this is a major bug. But maybe I did something wrong.
I flew in an area with a restriction of 60m altitude. Did a hyperlapse. Quad was about 300m away. Was shooting a pier - so quad over the sea.
With 4 shots of a 250 shot video to go, I got a battery low warning and offer to RTH. I canceled to allow completion. I’d fly back in the next 10 seconds and there was enough battery for that easily.
It then quickly showed a forced RTH message. Battery seemed to stop quickly as it completed. Guessing processor usage when it renders the video onboard? So I let it auto RTH
It rose to 65m, turned towards me and - nothing. Just sat there warning me of the battery. I took over. Cancelled automatic RTH and stick forward to get home. I was over the sea.
Quad didn’t move. No matter which direction I went in. Then I got critical battery warning. But quad would not move. Hovering over sea. Maybe 100m from shore.
I noticed the altitude was red. It said 65. I realised I can descend. So went down to 60m and altitude went white again. Then I could move. Loads of beeping and warnings. Quad started descending by it’s self but I could fly toward. Maybe I cancelled the forced landing. Not sure. I was in panic mode. Made it to beach and landed on sand. Safe.
The issue is: why did it rise to above the maximum set altitude (set by the quad when it started up and warned that I was in a restricted zone)?? Because when it went into that area (above the max altitude set, and into a restricted area) - it would not RTH, and when I took over, it would not move. Except down. Which I realise later. Surely the RTH should be the set RTH value, or the max altitude for the area - which ever is lower. A useless RTH of 65 in a 60 is dangerous and neatly cost me my drone.
I opened settings after calming down and the RTH value was indeed 65 and the max altitude had been auto set to 60 based on my location.
Very scary when you quad is about to die - 100m out to sea over the waves! I’d hope DJI can update the logic on RTH altitude and max altitude. Seems very unsafe.
I flew in an area with a restriction of 60m altitude. Did a hyperlapse. Quad was about 300m away. Was shooting a pier - so quad over the sea.
With 4 shots of a 250 shot video to go, I got a battery low warning and offer to RTH. I canceled to allow completion. I’d fly back in the next 10 seconds and there was enough battery for that easily.
It then quickly showed a forced RTH message. Battery seemed to stop quickly as it completed. Guessing processor usage when it renders the video onboard? So I let it auto RTH
It rose to 65m, turned towards me and - nothing. Just sat there warning me of the battery. I took over. Cancelled automatic RTH and stick forward to get home. I was over the sea.
Quad didn’t move. No matter which direction I went in. Then I got critical battery warning. But quad would not move. Hovering over sea. Maybe 100m from shore.
I noticed the altitude was red. It said 65. I realised I can descend. So went down to 60m and altitude went white again. Then I could move. Loads of beeping and warnings. Quad started descending by it’s self but I could fly toward. Maybe I cancelled the forced landing. Not sure. I was in panic mode. Made it to beach and landed on sand. Safe.
The issue is: why did it rise to above the maximum set altitude (set by the quad when it started up and warned that I was in a restricted zone)?? Because when it went into that area (above the max altitude set, and into a restricted area) - it would not RTH, and when I took over, it would not move. Except down. Which I realise later. Surely the RTH should be the set RTH value, or the max altitude for the area - which ever is lower. A useless RTH of 65 in a 60 is dangerous and neatly cost me my drone.
I opened settings after calming down and the RTH value was indeed 65 and the max altitude had been auto set to 60 based on my location.
Very scary when you quad is about to die - 100m out to sea over the waves! I’d hope DJI can update the logic on RTH altitude and max altitude. Seems very unsafe.