D
Deleted member 103366
Guest
Yesterday was a nice day, sunny, warm and thankfully very little wind. I decided to take the mini for some exercise.
The first flight involved a flight up a hill/ cliff and a peek over the top, I lfted maximum altitude to allow for the cliff's height (the flight ceiling rules are AGL here ). From a previous flight, last year, with a Phantom the cliff's top is around 110m above the take off point. I didn't take notice of what ceiling I set as I had no intention of going high over the cliff top, I just slid the button well up its scale. It turns out I must have set it to in excess of 875ft.
I do not like higher than necessary RTH heights so it set to 15m, the hill and cliff had no obstacles that the drone would have to avoid during an RTH.
The first flight was event free and after a bit of buzzing about around the take off point I landed and changed the battery for an out to sea flight.
I normally have the distance limit set to around 200m but I wanted to give the mini some room so I increased it.
I was just about at the edge of visual range i.e. max intended distance, when I got a signal loss which was quite sudden, there was maybe a second of pixelation and then boom, the connection was gone. (reasonably frequent glances at the screen)
At signal loss I was not worried, the battery was in the low 70%s, the drone was set to RTH at signal loss, and as far as I was aware the RTH height was 15m. The latter that turns out to have been VERY wrong.
A little later I see the telemetry start to change i.e. I had the telemetry connection back, though the video seemed frozen, BUT its climbing, !!!!!!!!! It shouldn't be climbing, it had been above 15m to keep it in sight. I thought to myself "it's got to be a trick or something of a weak signal" but it keeps on climbing, I lost sight of it. The connection was intermittant .
200ft "uuummm" ( I had switched to imperial units ), 300ft "UUUMMMM". Past 400ft connection seems to have stabilised but its still going up and I could not make it move towards home, the edges on panic showing themselves. I remembered at least one thread here? where the poster's drone climbed to a ludicrous height during RTH and was possibly lost. 500ft .....'wtf', Into the menus ...."oh mama" RTH height set to 875ft.
The problem with that is, not only does it use a lot of energy to get up there ( the battery was down to 61 or 62% as it stopped climbing ) it also takes one heck of a lot of time to come down, plus, what where the winds up there???? (As it turned out they must have been very light as the drone had no problem making good headway once it started moving forward). I tried to reduce the RTH height setting to stop the climb but every time I released the slider it sprang back to the 875ft setting. With hindsight I was trying to set thenew RTH height fairly low, below its existing height, maybe I should have tried an RTH height slightly above its at-that-time height.
With the Mini 'at the edge' of the communication range I did not want to cancel the RTH just in case that really threw a spanner in the works so it ended climbing to it's 875ft and then, thank goodness, started to move towards home. As soon as it started moving towards home I pulled the left stick down to start its descent.
When I was satisfied it was well within communication range I cancelled the RTH, moved the right stick forward and pulled the left stick all the way back for max descent rate whilst moving forward. It was back over head at a sensible height at about 30% battery.
There is absolutely not a snowball's chance in hell that I, deliberately, set the RTH height to 875ft. The only thing I can think of is that I must have accidentally touched and dragged the RTH height button whilst changing the distance limit. If that is what happened it's one heck of a bad coincidence with the 'extreme' maximium altitude setting because the App will not let you set an RTH height that is greater then the flight's ceiling and if you reduce the flight ceiling to below the RTH height the RTH height gets dragged down with the flight ceiling.
Lessons learn't
1) If changing limits CHECK you haven't made any accidental changes to something else.
2) Do not leave unnecessarily large height and probably distance limits in place from one flight to the next.
3) Ask if I should have cancelled the RTH before it got to 875ft?
I wanted to try a loss of signal RTH ( by switching the controller of etc ). but this was a bit beyond the pale
The first flight involved a flight up a hill/ cliff and a peek over the top, I lfted maximum altitude to allow for the cliff's height (the flight ceiling rules are AGL here ). From a previous flight, last year, with a Phantom the cliff's top is around 110m above the take off point. I didn't take notice of what ceiling I set as I had no intention of going high over the cliff top, I just slid the button well up its scale. It turns out I must have set it to in excess of 875ft.
I do not like higher than necessary RTH heights so it set to 15m, the hill and cliff had no obstacles that the drone would have to avoid during an RTH.
The first flight was event free and after a bit of buzzing about around the take off point I landed and changed the battery for an out to sea flight.
I normally have the distance limit set to around 200m but I wanted to give the mini some room so I increased it.
I was just about at the edge of visual range i.e. max intended distance, when I got a signal loss which was quite sudden, there was maybe a second of pixelation and then boom, the connection was gone. (reasonably frequent glances at the screen)
At signal loss I was not worried, the battery was in the low 70%s, the drone was set to RTH at signal loss, and as far as I was aware the RTH height was 15m. The latter that turns out to have been VERY wrong.
A little later I see the telemetry start to change i.e. I had the telemetry connection back, though the video seemed frozen, BUT its climbing, !!!!!!!!! It shouldn't be climbing, it had been above 15m to keep it in sight. I thought to myself "it's got to be a trick or something of a weak signal" but it keeps on climbing, I lost sight of it. The connection was intermittant .
200ft "uuummm" ( I had switched to imperial units ), 300ft "UUUMMMM". Past 400ft connection seems to have stabilised but its still going up and I could not make it move towards home, the edges on panic showing themselves. I remembered at least one thread here? where the poster's drone climbed to a ludicrous height during RTH and was possibly lost. 500ft .....'wtf', Into the menus ...."oh mama" RTH height set to 875ft.
The problem with that is, not only does it use a lot of energy to get up there ( the battery was down to 61 or 62% as it stopped climbing ) it also takes one heck of a lot of time to come down, plus, what where the winds up there???? (As it turned out they must have been very light as the drone had no problem making good headway once it started moving forward). I tried to reduce the RTH height setting to stop the climb but every time I released the slider it sprang back to the 875ft setting. With hindsight I was trying to set thenew RTH height fairly low, below its existing height, maybe I should have tried an RTH height slightly above its at-that-time height.
With the Mini 'at the edge' of the communication range I did not want to cancel the RTH just in case that really threw a spanner in the works so it ended climbing to it's 875ft and then, thank goodness, started to move towards home. As soon as it started moving towards home I pulled the left stick down to start its descent.
When I was satisfied it was well within communication range I cancelled the RTH, moved the right stick forward and pulled the left stick all the way back for max descent rate whilst moving forward. It was back over head at a sensible height at about 30% battery.
There is absolutely not a snowball's chance in hell that I, deliberately, set the RTH height to 875ft. The only thing I can think of is that I must have accidentally touched and dragged the RTH height button whilst changing the distance limit. If that is what happened it's one heck of a bad coincidence with the 'extreme' maximium altitude setting because the App will not let you set an RTH height that is greater then the flight's ceiling and if you reduce the flight ceiling to below the RTH height the RTH height gets dragged down with the flight ceiling.
Lessons learn't
1) If changing limits CHECK you haven't made any accidental changes to something else.
2) Do not leave unnecessarily large height and probably distance limits in place from one flight to the next.
3) Ask if I should have cancelled the RTH before it got to 875ft?
I wanted to try a loss of signal RTH ( by switching the controller of etc ). but this was a bit beyond the pale
Last edited by a moderator: