Big9erfan
lvl.1
Flight distance : 10951 ft
United States
Offline
|
m80116 Posted at 6-19 10:17
Welcome to the forum there... be aware that flying from a building is one of the known reasons to be a candidate for fly-aways (drone loss). Be sure the power the Mini outside any magnetic interference in your building, if you're unsure do not fly. You can verify the magnetic field and orientation with a mobile phone but you need to know what you're doing.
Wi-Fi interference still happens but the 5.8 GHz used for FCC is usually outside the reach of typical home and office routers. I ignore the sources of other 5.8 GHz emissions but in my country I tend to rely on the 5.8 GHz range despite the shorter throw because it proved to be less influenced by home Wi-Fi usage and in a clearer frequency spectrum.
m80116,
Thanks for the welcome.
I wasn't flying from a building, I was at my work, went outside (away from the building) and went flying. I was a good 50-100' from the building itself. I ensured there was no compass interference, I kept the drone "low" 30 feet or so and less than 50 feet away and did some pre-flight checks to ensure everything was responding properly, that the map showed the proper orientation and location, that the controller inputs were the direction and speed I expected, etc.
I understand about wifi & magnetic interference between the controller to the drone. That makes 100% sense to me. What I didn't expect was the app to say that it had lost communication with the controller. The app view screen went black, the rest of the UI was there, but not really responsive. Killing & restarting the app did not help, though it's possible I didn't give it long enough to re-estabilish communication with the drone. I have to admit, I was fairly uneasy flying "blind" and as such took great care to fly directly back and land so that I could try to determine where things went wrong. Unplugging my phone and plugging it back in and then restarting the app seems to have been the solution, I was just curious if this suggests that there's a possible problem with the controller, the cable or just an oddity that happens with the app sometimes. |
|