Hi,
Playing around in the Malvern Hills today with the FPV, encountered a strange/unexpected behaviour.
Had a standard thrash about at treetop height (all in 'M' mode) down to 50% battery, then did a full power climb up to about 400 metres above take-off point, which obviously put the battery into a state of high discharge rate during the climb. This triggered a 'return to home immediately' prompt, shortly followed by it entering forced landing mode with the battery still at ~ 40%! Obviously it's still controllable and I brought it back safely, but I wasn't very impressed.
In 'M' mode, you can nose down and 'glide' back from that height using about 3-5% battery which was the intention.
Instead, it put it into 'N' mode and descended at the usual 5 m/s, which ironically used a LOT more battery than had I done it in 'M'.
Is this normal behaviour? When I saw the prompt to land, I did react by initiating the idle power/glide procedure, which would have resulted in a very low discharge rate, but it didn't seem to react to this and pushed on with the forced landing regardless.
I understand the reasons behind the forced landing in 'N' and 'S' mode where the trajectories are very predictable to the onboard computer, but it doesn't seem very compatible with 'M' mode, and it seems to base this on the 'average' power use over the last 'x' amount of time rather than using the true power output right now.
Flight was entirely legal and no, I haven't read the manual cover to cover!
Any ideas?
Playing around in the Malvern Hills today with the FPV, encountered a strange/unexpected behaviour.
Had a standard thrash about at treetop height (all in 'M' mode) down to 50% battery, then did a full power climb up to about 400 metres above take-off point, which obviously put the battery into a state of high discharge rate during the climb. This triggered a 'return to home immediately' prompt, shortly followed by it entering forced landing mode with the battery still at ~ 40%! Obviously it's still controllable and I brought it back safely, but I wasn't very impressed.
In 'M' mode, you can nose down and 'glide' back from that height using about 3-5% battery which was the intention.
Instead, it put it into 'N' mode and descended at the usual 5 m/s, which ironically used a LOT more battery than had I done it in 'M'.
Is this normal behaviour? When I saw the prompt to land, I did react by initiating the idle power/glide procedure, which would have resulted in a very low discharge rate, but it didn't seem to react to this and pushed on with the forced landing regardless.
I understand the reasons behind the forced landing in 'N' and 'S' mode where the trajectories are very predictable to the onboard computer, but it doesn't seem very compatible with 'M' mode, and it seems to base this on the 'average' power use over the last 'x' amount of time rather than using the true power output right now.
Flight was entirely legal and no, I haven't read the manual cover to cover!
Any ideas?