PVFlyer said:
Can you indicate where (URL please) "tx power and distance were well documented far before you had" for Vision+? Hope you are not referring to generic home/business Wifi router/repeater stuff.
This features are not in any way specific to phantom, they're specific for atheros/madwifi (and maybe others) drivers and usermode linux tools to talk with these drivers (iwconfig/iw depending on linux distribution).
So I see nothing wrong in linking to OpenWRT (that runs on the phantom unmodified) documentation as I did a few posts ago.
LuCI (also not specific to phantom in any way) contains even better explanation on this parameters, I can attach a picture for you this evening if you want.
These features works the very same way on any Linux+WiFi device with this PHY, be it phantom, or access point or laptop as they're built on the same hardware and work with the same standarts and limitations. Technically this part of the phantom is a flying access point (plus ser2net process for telemetry and lighttpd for gallery), running on the access point Atheros SoC.
Algorithm on finding the correct values is also the same for all such a devices -- set the desired distance (if driver supports it) and increase tx-power until your antennas or matching circuit start limiting you. Most common way to measure throughput and link reliability in numbers is iperf util.
PVFlyer said:
If you insist "setting these two values" (or whatever other values) performing the same or even better, why you are so reluctant to prove it right by flying your Vision+. Don't tell me you are not a Vision+ owner. I thought it's pretty straight forward to prove by start screen recording on your iOS/Android device and fly until "Phantom Connection Broken", then post/share your video with us.
Assertions I don't even have a phantom is humorous, I've posted strace of your program running on it.
Also I've posted all the logic and automation here, so anyone can check it, even you. It shouldn't perform better, it should perform just the same.
Maybe I'll take a video next time I'll be flying outside the city, but this definitely won't happen in the next few days. This will also require me to buy your app again with some other account (as google only allows one refund per app per account).
After all, I believe you'll find excuses for (or just ignore) the video proof, like that happened with strace showing you lied about set distance command.