Gents,I am still using the last modded app and 2km without signal loss here. No range extender needed.
I’d like to share some considerations on the use of different modded versions (DJI Go 3.1.18-3.1.34-3.1.46) and flying at 5.8Ghz or 2.4Ghz I’ve experienced so far with my Phantom 3 SE. Specifically, I would like to share an event just happened and the decision I’ve taken due to this occurrence.
I’m flying with Android devices, a mobile (Xiaomi) with installed DJI Go 3.1.46 (and formerly 3.1.34) and Galaxy tab 8.4 pro on which I’ve installed DJI Go 3.1.18
I’m flying FCC and I'm not in the USA.
Flying with 2.4GHz gives somehow an extended range with respect to 5.8GHz if we consider that flying and shooting means ability to handle the drone with a minimum lag. I never succeeded to fly in shooting condition more than 1.8km with 2.4GHz and 1.6km with 5,8GHz
5,8 GHz at higher distance has a significant lower lag even with lower signal. 2.4GHz at 1.8km shows a strength signal between drone and transmitter but high lag, almost at the limit of usability for short distance shooting. I’m quite confident to reach over 2.5km (once I flight at that distance) or even further in 2.4GHz, but at high elevation (at least 100m high) hence just landscaping shooting.
There is no practical difference between the 3 versions of DJO Go as far as stability of signal in the various combination of 2.4GHz or 5.8Ghz with respect to “usable” shooting range. Transmission quality is the same. 3.1.34 and 3.1.46 are basically identical. In none of the three version (as of today) maps is working. So forget flight records capability in the app.
Version 3.1.34 and 3.1.46 are affected by more bugs than 3.1.18. Specifically, when RTH is activated (manually or due to signal loss) in the 3.1.34 and 3.1.46 version the software asks to confirm home location. It appears the app tries to redirect the drone to another location and it’s required to confirm to stick on previous (true) Home Point. This is most likely due to reset of the communication between transmitter and drone (evident in case the signal is lost and RTH is activated by default) and due to the fact that, at the reinstatement of the connection, the drone fix its new home point in the location where actually it is. And here the (big) issue.
Today I was shooting a coal ship unloading on a pier, 1.7km distance. 30m ASL (15m above pier).
I set the drone in 2.4Ghz mode at lift off, channel 6. Abruptly the signal was lost, most likely (I was shooting circling around the vessel) since the presence of the ship command deck between the drone and myself. I awaited signal return, that never happened (for first time since when I’m flying). I launched RTH, that failed.
I awaited more or less 5 minutes, than when I was starting to rescue the drone, it appeared above me and landed. Transmitter was “on” but still not connected. I shut off the transmitter, I reconnected the Tab, put on 2.4Ghz and voila’, the connection was re-established. Somehow the transmitter changed (when connection was lost for a certain period) from 2.4Ghz to 5,8GHz. Cannot say was commanded by the app or else.
However, If I was flying the drone with 3.1.34 or 3.1.46 I doubt the drone was able to come back due to the bug of the RTH. Although I’ve lost contact with the drone in various occasions, this is the first time the transmitter reset, most likely due to the fact that the connection was lost for a very long time.
So, based upon the outcome of this last flight, I would recommend all of you to fly 5.8GHz always (this is the natural frequency of our drone, kept by the transmitter at startup) and to stay on DJI Go 3.1.18 that has a flawless RTH.