AntDX316
Second Officer
Flight distance : 3394731 ft
United States
Offline
|
Furthest out was like 700m in Suburban (POI orbit) but was getting Remote Strong Interference alerts so didn't go out further at 2.4GHz. When I get strong Interference on Auto and I assume at 5.8GHz it just greys out (even super close). At least with 2.4GHz, I get some sort of warning. I got the M2Z at 1.2km on Auto but that was years ago. M2Z still gives me a better signal range than both M2Ps. I really don't want to go out far but some shots require it. If I can't go out further I just take 3 shots with no less than 75% overlap then photo-merge the pano (crop if needed)
I haven't tried w/o the Yagis on the new firmware (though, for some reason it says it Has .670 already installed even though I've never turned it on at July 7th and later, I think the latest was June 30th? firmware refreshed twice to ensure a good update). I was in a situation with the previous firmware, no yagi that at 350m in the same area I was getting a signal cut out. At least with 2.4GHz, new update, Yagi I was getting a clean signal with a few occasional hiccups but nothing too crazy. At least it works.
I got to 1.8KM+ along the beach at night w/o issue. Before, was having plenty of issues close-up but this was w/ the previous M2P. I don't really run scientific controlled testing. Someone showed 3 dbi gain with Yagis so it must work. If you can just get enough penetration to have feed and control, imo it's a win. When it greys out but you still have telemetry it can be nerve-racking. I had the Smart Controller crash on me (grey screen then app crash after a few minutes) and I wasn't even too far when it greyed out. RTH worked beautifully. I ran to the location where it was signal lost then went back and saw it was there where it took off.
I assume they've allowed more signal performance because of the strong interference caused by Everybody going powerful wifi will cause more problems than keeping it at a lower wattage? |
|