When the phone is not connected to the controller my Go4 app says "Disconnected". When the phone is connected to the controller but the controller is not connected to the drone the Go4 app says "Aircraft Disconnected"
Likewise and respectively the fly app says "RC not connected to m...." & "Aircraft not connected t'.."
Could that be Wayne4chun's reasoning?
I understand the premise of the errors and realize the implications, and if the issue was uniform, providing similar results in all flight locations I might concur. However, I have been to the valley 4 times over 2 days and not yet been able to fly due to constant disconnects.
Between flights, as I travel back and forth between the valley and the office my
M2P flew without incident at the office. We are moving out of the office and hauling everything to the valley for storage
It just seems strange to conclude its a cable when the cable and phone remained connected between locations, worked at one place and not at another.
Ok, here's a few of examples. The bird was hovering and I switched from video to still camera and the controller disconnected from the phone. Possibly a coincidence but this has happened to me before. OK, more coincidences.
Up in the mountains I had disconnects and reconnects. One after another on the same flight. Temporary loss of connection and then the link would come back until it didnt! Other times in the same location I'd have no issue all day.
Another time at the "Mysterious Valley", I lost the app and then the controller, freeing my
M2P to do whatever a freebird does. At this point I entered "Spirit mode" and began to pray. Actually, I did just as I always do; restart the controller and everything usually comes alive again (usually). This occasion was scary though. Normally, when disconnected from the controller, the drone should stop, hover and then enter RTH. Not so this time. It slowly rotated (like beginning RTH) and started to fly away, in the wrong direction! I had no control and my investment was turning to a speck in the distance. I shut off the controller and the drone kept going! Eventually it stopped, hovered, then turned towards me and came home. Before landing I was able to reconnect but it took a while. What "appears" to have happened is that during the disconnect and me moving the sticks around, there was a momentary link that triggered the fly away. Just a guess... I'm glad it had a change of heart and came back.
I thought perhaps I was flying near a tribal burial ground in the valley and the the spirits of fallen Indian warriors were screwing with me. I of course jest, but it makes as much sense as a controller disconnecting from the drone because the cable between the controller and phone has a problem and the issue being generally localized and reproducable.
Here's something interesting, I notice that sometimes my phone, an Android S10+, shows the battery level big and bold on screen at the time of a disconnect of the app.
A thought... is there something built into the programming on the
M2P that would stop a flight or prevent a flight in the absence of WiFi (data) feed. You know, "Big Brother" stuff. When at the Valley and in the mountains there is little or no cell service. Only thing makes me doubt this is that it should "prevent" take off and warn you, not disconnect in mid flight.
