The downlink restored message was at 2:16.9 after a blank of 0.9 seconds
RTH initiated later on at 2:29 with no lost time before it which suggest that RTH was initiated manually by the OP.
RTH is triggered by loss of uplink signal, not the downlink. The "downlink restored" message is just an indication that the radio signal was weak at that point. The quality of downlink and uplink signals is not necessarily symmetrical. E.g. if there is interference on the craft's side, it is possible to have the uplink broken while the downlink can still be maintained.
RTH can only be triggered by three reasons : low battery, lost of uplink and the pilot's action.
Low battery can be ruled out obviously.
The OP reported that he hit the RTH button only after the craft has started ascending by itself so it is impossible that the first RTH was triggered by the pilot's action. From the chart below it can be seen that after the first RTH was triggered, full throttle down has been applied repetitively but the craft did not descend, then RTH was cancelled because the pilot pressed the RTH button. The chart matches the OP's recollection perfectly. It can therefore be concluded that the first RTH was triggered by bad uplink radio signal.
The OP cancelled RTH at 4:45.1 and 4:47.8 he pulled the left stick hard down and brought the drone all the way down manually.
He has cancelled it a number of times. The last time he cancelled it but immediately re-enabled it was at 5:20 or 320 sec. As the craft was already above the home point, autolanding was triggered instead. As can be seen in the chart below. The craft descended steadily all the way despite irratic throttle inputs by the pilot.
Last edited: