Foreflight, Android, and the "Stratux" WiFi
1. Foreflight and Android apps worked perfectly with the "Stratux" WiFi connection.
2. We observed that both my android app and the Foreflight app did not recieve the transmitting tower repeat traffic until around 2000 feet high.
3. When it is receiving a tower the quick way to tell is that it repeats your position as a dot behind your plane with only the altitude. All ADS-B equipped planes will have both a tail number and altitude direct without the tower repeat.
4. However Marc pointed out that there must be a ADS-B plane within 30 miles of you triggering the tower response or you will not see any other non ADS-B traffic.
5. Now the big gotcha "according to Marc." Since the tower only sends the triggering airplane traffic within that triggering plane's 30 mile circle there is a situation where you could be head on to same altitude opposite direction non ADS-B traffic but you will not see it on the screen since he is more than thirty from the plane that triggered the tower response.
So until every airplane is equipped with ADS-B out, ADS-B in is a nice to have addition but not completely reliable. Even after January 2020 it will be reliable only in controlled airspace that requires ADS-B out but even then a NO RADIO plane can call ahead for clearance into B or C airspace to land and you will not see that airplane at all. ADS-B is mainly for ATC control of IFR and terminal traffic. Our being able to see traffic is secondary but much better than nothing! As they say in the airline business, "If you are in VFR conditions below 18000 feet ya gotta have your eyes out the window!"
Foreflight, Garmin 660 with the GLD-393 3D
1. Foreflight works perfectly with GDL 39 including AHRS
2. For some mysterious reason, traffic is reported 300' lower on Foreflight than on the Garmin 660.
I summarized a slack conversation and added some more info. Enjoy.