Keep in mind that if your drone is less than 20 meters away when you press the RTH button, then it will land just where it is
Meaning no offense but that is not necessarily correct, as I recently discovered and alarmingly so.
An
M2P or Zoom (I have been playing with both) was around 18m from its home point and below the homepoint which was on the opposite side of my house.
I triggered an RTH fully expecting the drone to land where it was ( due to being within 20m of the homepoint). It didn't! instead it climbed until it was about 1m above the roof and then started to move towards the home point, instant panic because at that height and position there's a tree in the way.
I had let the RTH run during the climb as I was 'expecting' the drone to go up to the proper RTH height, 25m or so, and well above the house's roof and above of the offending tree. I cancelled the RTH as the drone was over the roof and sent it UP well away from that tree.
Going through the manual.....again..... it turns out two other things were going on. Firstly "RTH at current Altitude" was on, it causes the following behaviour
"If the aircraft is between 5 m and 20 m from the Home Point when the RTH procedure begins: i. If the RTH at Current Altitude option is enabled the aircraft flies to the Home Point at the current altitude, unless the current altitude is less than 2 m, in which case the aircraft ascends to 2 m and then flies to the Home Point at a speed of 3 m/s ".
The second thing was, I think, that the obstacle sensing was triggered by the RTH and since the house blocked the flight path the drone climbed until it had a clear path over the 'obstacle'. It is worth noting that with the slope on the roof the 'clear path' across the roof was below the roof's ridge, I find that quite impressive in a way but scarily close to the roof below the drone.
Do these things ever stop teaching us or catching us out???????